The Missing README: A Guide for the New Software Engineer

The Missing README: A Guide for the New Software Engineer

Authors: Chris Riccomini & Dmitriy Ryaboy
Published: 2021

Overview

The Missing README fills the gap between what you learn in school and what you need to know to thrive as a professional software engineer. Written by two experienced engineers who scaled systems at LinkedIn, Twitter, and other tech companies, this book provides practical wisdom on becoming an effective engineer beyond just writing code.

Key Highlights

Getting Oriented

• First 90 days matter most - Focus on understanding the codebase, team dynamics, and business context before trying to make big changes
• Map the terrain - Create mental models of how systems work, who owns what, and where decisions get made
• Build relationships early - Your network is as important as your technical skills

Professional Development

• Staff+ engineers focus on leverage - Move from individual contributions to force multipliers
• Technical judgment improves with experience - Learn to make tradeoffs between speed, quality, and complexity
• Document your decisions - Architecture Decision Records (ADRs) create institutional memory

Working with Code

• Code reviews are teaching moments - Use them to share knowledge, not just catch bugs
• Incremental improvements beat grand rewrites - Large refactors rarely succeed; prefer small, continuous improvements
• Understand the why, not just the what - Every line of code solves a problem; know which problem

Technical Leadership

• Influence without authority - Staff engineers lead through expertise, not management
• Write RFCs and design docs - Formal proposals create alignment and surface concerns early
• Be a multiplier - The best engineers make everyone around them better

Navigating Organizations

• Understand your company’s tech strategy - Align your work with business priorities
• Build a mental map of stakeholders - Know who makes decisions, who influences them, and who implements them
• Communication is a technical skill - Clear writing and speaking are essential for senior ICs

Quick Facts

• Target audience: Software engineers at any level, but particularly valuable for those aspiring to Staff+ roles
• Core thesis: Professional software engineering requires skills beyond coding—understanding systems, organizations, and people
• Unique value: Bridges the gap between junior and senior engineering by making implicit knowledge explicit
• Best for: Engineers transitioning from mid to senior levels, or anyone looking to increase their impact

Practical Takeaways

For immediate application:

1. Start maintaining an engineering journal to document decisions and learnings
2. Create a stakeholder map for your current project
3. Write one-page technical proposals before starting significant work
4. Schedule regular coffee chats with engineers in adjacent teams
5. Contribute to technical documentation, even if it’s not assigned to you

For long-term growth:

1. Develop expertise in one area deep enough to be the go-to person
2. Build a track record of shipping projects that solve business problems
3. Practice writing technical documents and RFCs
4. Mentor junior engineers—teaching clarifies your own thinking
5. Study how senior engineers make technical decisions

Why This Book Matters

The Missing README addresses the “hidden curriculum” of software engineering—the unwritten rules and practices that separate effective engineers from average ones. It’s particularly valuable for engineers working in fast-growing companies or transitioning to more senior roles, providing a roadmap for the non-coding aspects of technical leadership.

The book emphasizes that technical excellence alone isn’t enough; understanding organizational dynamics, effective communication, and strategic thinking are equally important for career growth and impact.