Tags
7 articles
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.
Write technical RFCs and design documents that actually drive decisions by structuring proposals around trade-offs, alternatives considered, and measurable success criteria rather than exhaustive implementation details that nobody reads.
Develop an authentic personal brand as a software engineer through technical writing, open-source contributions, conference talks, and strategic networking that creates career opportunities without feeling performative.
Learn the structure, storytelling, and optimization techniques that make technical blog posts stand out, attract readers, and establish you as a credible voice in the engineering community.
How to write Request for Comments documents that drive clear technical decisions — covering structure, audience calibration, alternatives analysis, and building consensus asynchronously.
How to write technical documentation that engineers actually read — covering ADRs, runbooks, API docs, and documentation-as-code workflows.
Practical techniques for writing documentation, ADRs, and technical specs that your team will actually read and maintain.