How to tame evil dependencies

Dependencies are often ignored or simplified

Author

Jakub Chodounsky
September 09, 2024

How to tame evil dependencies
9 minutes by Dirk Lässig

Dependencies between software development teams in large organizations are an almighty problem making it important to look at dependencies holistically. A good solution is a three-phase approach: minimizing dependencies by realigning teams and refactoring systems, mitigating their impact through common standards and practices, and coordinating remaining dependencies through effective planning and collaboration.

Develop custom internal tools with fewer resources and greater efficiency using ToolJet, an open-source, low-code platform. Create complex apps and dashboards effortlessly with our intuitive drag-and-drop interface, and JavaScript and Python code support. Unify all your data by integrating with over 50 data sources and automate tedious manual tasks with workflow capabilities.

Words can encourage or discourage divergent thinking. Use language that accurately reflects your level of certainty, so you don't make overly-bold statements you can't stand behind.

Suresh highlights five key areas where he had to let go of old habits to succeed in the new role. These include shifting from being a creator to an enabler, adapting to constant interruptions, accepting slower feedback loops, addressing conflicts head-on, and focusing on long-term strategic planning.

This article by Claire, CEO of Canopy, addresses the challenge of giving feedback on subjective matters like tone or personality. She offers a framework for delivering such feedback effectively, emphasizing the importance of connecting it to work outcomes rather than personal attributes. Key points include rejecting the notion of purely objective feedback, acknowledging the conditions that enable certain behaviors, and providing specific examples of desired changes.

Technical Coherence
10 minutes by Jack Danger

Software development slows down over time. To battle this we identify the necessary user experience domains for our products. Then we identify the shared product domains that underpin multiple user experience domains. And lastly, we organize engineering into three layers, the top two correspond to the above domains and the third provides infrastructure.

how did you like this issue?

Login or Subscribe to participate in polls.

newsletters

Would you like to become a sponsor and advertise in one of the issues? Check out our media kit and get in touch.