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.
A guide on giving effective feedback in tech teams, emphasizing the importance of balancing critique with specific, meaningful praise.
Strategies for managing and documenting team knowledge to improve collaboration, decision-making, and onboarding of new members.
Explores why complex ideas and systems are often favored over simpler ones in tech and academia, and argues for the advantages of simplicity.
A guide to effective Angular interview questions for senior developers, focusing on open-ended questions to assess problem-solving over API memorization.
How to use an Azure DevOps Pull Request template to enforce a team's Definition of Done and improve code review quality.
Learn how to implement and use the Python logging module to monitor events and analyze application performance.
A guide to manually tackling tedious software development tasks like linting and dependency upgrades, and when brute force is the right approach.
Analyzes why daily stand-ups often fail in software teams and provides actionable advice to fix them by refocusing on core Agile principles.
A guide on defining your target audience for technical documentation and books to create focused and effective writing.
Explores how embracing uncertainty in software product development can lead to greater profitability, using betting analogies to explain economic principles.
A software development analogy comparing building a house to building websites, emphasizing the need for upfront planning for accessibility and performance.
