Discusses why blindly copying technical solutions or processes from one team to another often fails due to unique team and company contexts.
A guide on how engineering teams should approach technology selection, emphasizing problem-fit, proven solutions, and team experience.
Explores how AI, particularly GPT-based systems, might change software development by potentially shifting from traditional source code to prompting languages.
A software engineer turned vendor discusses the loss of credibility and offers advice on how to be taken seriously when selling software.
A developer argues that AI should focus on automating tedious tasks to free up human energy for creative and meaningful work.
A developer argues for proactively cleaning up unused code and dependencies to prevent future technical debt and hidden bugs.
Explores the distinct roles of Platform Engineering and DevOps in software development, highlighting their differences and complementary nature.
Explains the core principles of DevOps, including the Three Ways, collaboration, CI/CD, and automation for efficient software delivery.
A developer argues that AI will augment, not replace, front-end developers, addressing fears about the future of the profession.
A comprehensive guide for aspiring tech conference speakers, covering proposal writing, preparation, slides, demos, and networking benefits.
Argues that Tech Leads, who code and manage small teams, are more effective than detached Engineering Managers in software organizations.
A summary of the book 'Teaching Tech Together', highlighting key methods for effective technology education like live coding and learner personas.
A guide on writing effective RFCs (Request for Comments) for engineers to improve communication and technical planning within teams.
An experienced interviewer shares what they look for in junior software engineering candidates, focusing on mindset over technical skills.
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 developer argues for minimal, strategic code commenting, using examples to show how clear naming and structure can often replace verbose comments.
Argues that deploys and releases are distinct concepts and that relying on deploys to change user experience is problematic.
Senior engineers must excel at communication and problem articulation, not just technical skills, to be truly effective.
Discusses the importance of user-centric thinking in software engineering and how RFCs can prevent common pitfalls like building the wrong thing or over-engineering.
A tech manager argues that team problems are often human issues, not process flaws, using a PR example to advocate for direct communication.
