A software consultant outlines four essential elements for an effective development process: visible, small, prioritized, and completed work.
A podcast episode discussing the pros and cons of solo versus team-based game development, focusing on decision-making, timelines, and motivation.
How a small team organized a 250-person tech conference in just two months, focusing on community and embracing serendipity.
A guide to customizing default issue labels for GitHub projects, including setup steps and limitations for organization accounts.
A comprehensive guide covering all stages of conference planning, from initial concept and budgeting to post-event follow-up.
Explains how the software development practice of 'grooming' can be applied to boost productivity in any project by preparing work ahead of time.
A monthly retrospective from TinyPilot's founder covering business metrics, goal progress, and software development insights.
Explains the distinct roles, responsibilities, and focus areas of Scrum Masters, Delivery Managers, and Project Managers in software development and project management.
A developer shares weekly progress on multiple projects, including iOS game updates, cross-platform mobile development, and podcast management.
Explores how software engineers create and focus on imaginary problems to escape boring tasks, leading to inefficient solutions and bad software.
Mitchell Hashimoto shares his method for staying motivated and completing large technical projects by breaking them into tangible, demo-able chunks.
A guide to using a simple four-column Kanban board to organize work, reduce stress, and improve visibility for yourself and your team.
A developer shares their methodology of 'Notification-driven Development' to efficiently manage GitHub notifications and maintain multiple projects.
A software engineer's reflection on the challenges of switching between coding (IC) and management roles, and the impact on productivity.
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 software engineer shares six practical strategies to prevent burnout, focusing on goal-setting, workload management, and self-care.
A guide to creating and sharing personal and team weekly digests to track work progress, increase visibility, and improve transparency in a tech workplace.
A beginner's guide explaining GitHub's core concepts like repositories, issues, and Markdown for professionals in non-technical roles.
A tech manager argues that team problems are often human issues, not process flaws, using a PR example to advocate for direct communication.
Argues that product backlogs are harmful, never shrink, and proposes working without them for better productivity and team alignment.
