A personal reflection on the author's 2020, discussing burnout, creative output, and the impact of the pandemic on work and life.
Explores the benefits and common questions about mob programming, a collaborative coding practice where teams work together on features and problems.
A developer's guide to convincing business stakeholders to approve technical investments like framework migrations and tech debt.
Best practices for developers to prepare and submit code for review, ensuring productive feedback and positive team dynamics.
A software developer shares insights from giving 125+ tech talks, focusing on planning, topic selection, and setting clear presentation goals.
A software engineer critiques story-point-driven estimation in agile development, arguing it's often misleading and doesn't solve core estimation problems.
Practical advice for developers to improve their GitHub portfolio, focusing on quality projects, learning in public, and effective documentation.
The author announces their new book 'TypeScript in 50 Lessons', a 450-page guide focused on the TypeScript type system.
A developer's chart on career priorities goes viral, sparking discussion on the evolution from making code work to valuing readability and avoiding over-abstraction.
Compares Feature Teams and Product Teams in software development, explaining their structures, goals, and which type the author prefers.
A senior engineer describes how the Feature Lead role at Nested provided the growth and business impact he was missing as a senior developer.
An argument that technology cannot solve systemic human problems like racism, and that real change requires human action, not just code.
A detailed guide on the author's process for creating concise, high-value educational videos, focusing on preparation and content structure.
A guide for developers on when to prioritize writing tests versus fixing bugs, based on cost-benefit analysis of different scenarios.
Tips for improving communication and reducing conflict in open-source software development, addressing maintainer anxiety and contributor fatigue.
Advice on pacing your programming self-study to avoid burnout, recommending 4 hours daily for full-time learners and 1-2 hours for those with jobs.
A developer shares insights and lessons learned from speaking at tech conferences, including idea generation and personal experiences.
Analyzes how developers without CS degrees got their first jobs, based on a survey of 450+ Twitter responses.
Tips for adapting to a sudden, non-ideal remote work setup at home, focusing on practical solutions for common challenges.
A solo developer shares financial results and lessons from his second year building software businesses after leaving Google.
