featured in #258
Engineering Teams Are Just Networks
- Marianne Bellotti tl;dr: "If you want to hire well, have modest baseline of minimum qualifications and think of your engineering organization as a network." Marianne illustrates why this is critical: people do not work out in their new roles "because their strengths do not align with the incentives the network creates."featured in #257
No Surprises: A Framework For Software Quality
- AbdulFattah Popoola tl;dr: Abdul outlines a "Maslow Hierarchy for software quality" to help you prioritize and calculate tradeoffs. The hierarchy comprises of security, usability, reliability, performance and integrity, and is explained in detail.featured in #257
featured in #257
featured in #257
Product Teams Own Capabilities, Not (Only) Code
- Jessica Kerr tl;dr: "As a software engineer, what is your job? and what is your value?" Jessica makes the point that delivering capabilities is critical to the health of software teams, not just delivering features or code.featured in #257
On Ships, & Shipping Incrementally
- Barry McCardel tl;dr: The only path around the 2.0 tar pit is incrementalism - replacing a legacy platform through small, deliberate steps.featured in #256
In Software, When An Engineer Exits The Team
- Doug Arcuri tl;dr: "There are moments during the transition where I battle an aggravated ego. But I check myself, calm down, and refocus back on this individual. I want them to succeed, and me stepping to hinder that would be incorrect. I’ll send recommendations and smile. They will become a better person because of this, and so will I."featured in #256
How Big Tech Runs Tech Projects And The Curious Absence Of Scrum
- Gergely Orosz tl;dr: Gergely covers: (1) various project management approaches based on a survey of 100 companies. (2) Setup and processes of project management in big tech. (3) Why big tech don't use scrum. (4) A POV on how to run projects in your team.featured in #255
Tales Of Regret From Onboarding
tl;dr: A collection of codebase onboarding stories from real developers. The anecdotes illustrate ways in which onboarding can go wrong and hints at how CodeSee can better the experience for the developers who come after us.featured in #255