Design Docs and RFCs
Listed inDesign Docs and RFCsWorking as an Engineeron
Proposing a change so reviewers can disagree with the reasoning rather than the code.
Intermediate8 minDraft
#process
The parts of the job that are not code: writing, deciding, disagreeing, mentoring, and growing past your current title.
12 articles
Listed inDesign Docs and RFCsWorking as an Engineeron
Proposing a change so reviewers can disagree with the reasoning rather than the code.
Listed inMentoring and Being MentoredWorking as an Engineeron
Growing other engineers deliberately, and getting more out of the seniors around you.
Listed inWorking with AI Coding ToolsWorking as an Engineeron
Where generation helps, where review load goes up, and staying responsible for code you did not type.
Listed inTechnical WritingWorking as an Engineeron
Design docs, RFCs, and READMEs that get read — starting with the conclusion and cutting the rest.
Listed inWorking with Product and DesignWorking as an Engineeron
Translating constraints into options, and surfacing the cost of a requirement early enough to change it.
Listed inWhat Seniority Actually MeansWorking as an Engineeron
Scope, judgement, and multiplying other people — none of which is measured in years or languages.
Listed inScoping and ShippingWorking as an Engineeron
Cutting a project into shippable slices, and finding the 20% that delivers most of the value.
Listed inLearning ContinuouslyWorking as an Engineeron
Depth versus breadth, choosing what to ignore, and building durable knowledge over trend-chasing.
Listed inDisagreeing WellWorking as an Engineeron
Separating the technical argument from the social one, and disagree-and-commit as a real option.
Listed inThe Debugging MindsetWorking as an Engineeron
Binary search over the system, questioning assumptions, and knowing when to stop and sleep.
Listed inMaking Technical DecisionsWorking as an Engineeron
Reversible versus one-way doors, deciding with incomplete information, and committing once you have.
Listed inOnboarding into a CodebaseWorking as an Engineeron
A repeatable first-two-weeks approach: ship something small, then map the system around it.