Tags
12 articles
Design internal developer platforms that accelerate delivery using self-service infrastructure, golden paths, platform APIs, developer experience metrics, and adoption strategies that earn trust instead of mandating compliance.
Apply SRE toil reduction principles to everyday engineering work by identifying repetitive manual tasks, measuring their true cost, building targeted automation, and establishing a culture where toil elimination is treated as real engineering output.
Structure technical RFCs that clearly communicate the problem, evaluate alternatives, propose a solution, and drive team alignment on architecture decisions, with templates and examples for common engineering decisions.
Battle-tested code review practices that go beyond catching bugs, focusing on feedback calibration, review sizing strategies, and creating a review culture that accelerates both code quality and team development.
Move beyond surface-level retros with structured facilitation formats, actionable output patterns, and follow-through systems that turn team feedback into measurable changes.
How to run one-on-one meetings that build trust and accelerate growth — covering question frameworks, career development conversations, difficult feedback delivery, and tracking action items across sessions.
How to run blameless incident postmortems that produce actionable improvements — with templates, facilitation techniques, and patterns for turning production incidents into lasting organizational learning.
A practical framework for delivering constructive feedback, receiving criticism without defensiveness, and building a team culture where honest feedback is normal — with specific techniques for code reviews, 1-on-1s, and retrospectives.
A senior engineer's guide to mentoring that actually works — structuring 1:1s, giving feedback that sticks, calibrating challenge levels, and building independence rather than dependency.
Practical strategies for protecting focused programming time, reducing context switching, and structuring your day so that deep technical thinking becomes the default instead of the exception.
Practical strategies for recognizing, recovering from, and preventing burnout in software engineering — covering workload management, boundaries, and sustainable productivity habits.
How to give code reviews that catch real bugs, share knowledge, and improve team velocity instead of creating bottlenecks.