A software engineer shares strategies for managing cognitive load and improving productivity through documentation, delegation, and focused task completion.
A software engineer discusses strategies for prioritizing and integrating technical cleanup work into the development process, arguing against isolated "technical sprints".
Explains the concept of bikeshedding, where teams focus on trivial details over critical issues, and offers strategies to stay focused.
A developer advises against naming projects too early, sharing a strategy of using temporary code names to let ideas evolve freely.
A tech founder shares how Mergify built a project management approach based on simplicity, ownership, and autonomy, moving beyond rigid Agile dogma.
A developer reflects on the struggle of choosing between finishing old side projects and starting new, exciting ones.
Engineers should focus on understanding the underlying problem behind a task, not just executing it, to avoid creating useless or poorly designed features.
A freelance React developer argues for charging by the hour instead of by project value to handle scope creep and changing requirements.
A critique of modern bug trackers, proposing a 'separation of concerns' principle to better distinguish factual bug records from planning data.
A technical breakdown of the launch process, systems, and architecture behind the release of the Pile-Up Poker game on the Puzzmo platform.
A developer explains why they prefer using simple Makefiles for project automation, citing consistency and ease of use across different technologies.
A review and key takeaways from the classic software engineering book 'The Mythical Man-Month', focusing on Brooks' Law and project management.
A simple, five-step formula for building trust through reliability, clear communication, and consistent action in work and life.
Explores how senior engineers must shift from assigned tasks to self-managing a complex mix of projects, tasks, and priorities.
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.
