A proposal for organizing active developer sprints within the Django community, inspired by experiences at DjangoCon US.
A template for creating structured technical design documents to record decisions, scope, and solutions for software projects.
A conversation about transitioning to full-time open source work, the challenges of funding, and the personal motivations behind it.
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.
Explores the evolution of operations into platform engineering, where teams focus on enabling developers through self-service platforms and managed services.
Discusses the importance of human factors like team onboarding, reversibility, and support when choosing software architectures and technologies.
The article critiques common self-deprecating phrases in tech communities, arguing they reinforce harmful perceptions about intelligence and belonging.
Explains the multifaceted role of an Engineering Manager (EM) in hiring, facilitating work, team alignment, process improvement, and coaching.
A programmer shares how using documentation tools like Dash helps overcome information overload and memory limitations in modern software development.
Argues that deadlines harm software quality and morale, proposing 'preemption points' and queueing disciplines as better alternatives.
A developer reflects on six months of full-time open source work, discussing projects, financial challenges, and lessons learned.
A programmer's reflection on the philosophical and practical differences between truly fixing a bug versus just patching it, emphasizing testing and documentation.
A developer reviews their 10-month tenure at Remix, highlighting community growth and achievements before leaving to focus on a new venture, EpicWeb.dev.
Argues that velocity is a poor engineering metric and introduces better metrics for measuring team performance and productivity.
Analyzes the 'Time Till Open Source Alternative' (TTOSA) metric, showing how quickly open-source alternatives emerge to challenge proprietary software.
Explains the 'Minimum Viable Nothing' concept for validating product ideas without building them, focusing on testing willingness to pay.
A personal reflection on work intensity, exploitation, and finding meaning in tech careers, challenging the stigma around long hours.
The article argues that true mass collaboration on the internet is a myth, using examples from open source, gaming, and teamwork dynamics.
Explores how intentional rituals can build belonging, engagement, and culture within engineering teams, with examples from past workplaces.
