Topic
Collaboration
Communication, engineering culture, and team practices that make work sustainable.
Join the Team Before You Try to Change It
Adapt to a new engineering team through timely questions, visible progress, early review, and small evidence-based changes after trust is earned.
Turn Production Incidents into Shared Domain Knowledge
Use incident reviews, working notes, concept maps, and rotated operations to reduce domain knowledge gaps across a software team.
Win Technical Arguments with Small Proofs, Not Opinions
Diagnose why a proposal is blocked, build a small proof, strengthen your reasoning, understand the opposing case, and treat new technology as company risk.
Git History Is a Team Asset, Not a Work Diary
Split work before polishing commits, shape pull requests for reviewers, and leave a history that helps the next engineer understand changes and recover a release.
Software Should Survive the Developer Who Built It
Good company software reduces debt, fits the team's operating ability, and remains understandable and repairable after its original developer leaves.
Choose Experience and Judgment over Development Jargon
Theories and patterns are useful references, but a developer still needs to explain the code, its tradeoffs, and what happened when it was operated.