engineering-culture
8 posts
Rushing feels fast but creates rework, bugs, and firefighting. Why pausing for refactoring, tests, and CI upkeep is an investment in speed, not lost speed.
technical-debt · testing · ci-cd +2
Stop asking who wrote the legacy code. Separate responsibility, accountability, and blame, and make inherited code owned rather than orphaned.
engineering-culture · leadership · team-management +3
A blameless postmortem model that fixes the system instead of finding a culprit, with a copy-paste template and where individual accountability still applies.
engineering-culture · incident-response · psychological-safety +4
The team documents a mature engineering team owns: onboarding, working agreements, Definition of Done, on-call, knowledge transfer, and what makes each one good.
engineering-culture · hiring · documentation +4
AI absorbs more of the implementation, so the framework name matters less than four feedback loops. A decision lens for tuning flow, cadence, WIP, and review.
leadership · agile · team-management +3
An analysis of the DevRel role, how it differs from marketing and sales engineering, the skills it needs, and when companies should invest in it.
career · developer-experience · engineering-culture
A field guide to spotting, managing, and resolving conflict in software teams, with practical frameworks and early-warning systems that turn friction into performance.
leadership · team-management · best-practices +4
Protect your team from single points of failure through knowledge distribution, documentation strategies, and systematic risk management.
team-management · documentation · knowledge-sharing +5