A weekly collection of articles on software architecture, development, AI, and leadership, featuring insights on legacy systems, HTTP, and team skills.
Explores managing the tension between adaptation (exploration) and optimization (exploitation) in tech teams, advocating for a balanced, context-driven approach.
An engineer argues that software development is a learning process, not an assembly line, and explains how to use LLMs as brainstorming partners.
Analyzes why team retrospectives often fail to drive improvement and offers practical solutions inspired by Toyota's kaizen principles.
Explains how high-performing teams can effectively use Team OKRs to bridge strategy and execution, avoiding common top-down pitfalls.
How a small team organized a 250-person tech conference in just two months, focusing on community and embracing serendipity.
A developer critiques the blind adoption of Scrum, arguing it's often misapplied and becomes a rigid, unproductive ritual rather than a useful framework.
A guide to creating and sharing personal and team weekly digests to track work progress, increase visibility, and improve transparency in a tech workplace.
Explores how storytelling makes software principles like Agile and SOLID more memorable and understandable than dry rules alone.
Analyzes Shopify's controversial meeting purge, critiques its execution, and shares best practices for running effective, productive meetings in tech.
Discusses the importance of managing a project backlog by closing out old, unrealistic issues to improve focus and efficiency.
A software engineer's perspective on the value and pitfalls of time estimations in software development projects.
The article critiques the misapplication of DevOps and Platform Engineering, arguing they are about organizational culture, not just tools or rebranding.
A satirical guide on how to misuse and distort the Scrum framework, leading to failure, to highlight common Agile anti-patterns.
Argues that Kanban is more adaptable and effective than Scrum for software teams, explaining how Kanban principles enhance responsiveness and decision-making.
Argues that deadlines harm software quality and morale, proposing 'preemption points' and queueing disciplines as better alternatives.
Argues that velocity is a poor engineering metric and introduces better metrics for measuring team performance and productivity.
Analyzes why daily stand-ups often fail in software teams and provides actionable advice to fix them by refocusing on core Agile principles.
A satirical critique of over-engineered Agile frameworks, proposing the simple 'Talk To Your Customers' (TTYC) methodology as a disruptive alternative.
A guide to essential developer team workflows covering Git branching strategies, Agile methodologies, and CI/CD practices for effective collaboration.
