The Blank Terminal

The skill is not knowing what to type. The skill is knowing how to begin when you do not yet know what to type.

I remember the blank terminal. A real codebase, a problem I only half understood, and a cursor blinking on an empty line. I remember it clearly because the feeling never went away. It just changed what it was pointing at.

I am not writing this from the mountaintop. I am writing from memory of that desk.

The same blank, every altitude

The blank follows you. A beginner stares at an empty terminal. A senior engineer stares at a blank architecture document. A lead stares at a team problem nobody has named yet. A manager stares at an initiative with no edges.

The surface problem changes. The recurring skill does not: knowing how to begin when the next move is not obvious.

What this book is

This is not a book about becoming the engineer who always knows the answer. It is a book about becoming the engineer who knows what to do when they don't.

The promise is small on purpose. When you do not know what to do next, these are some of the landmarks that have helped me find the next move. Landmarks, not a system. A landmark does not walk the path for you. It tells you where you are, and it earns its keep when you are lost.

What I claim, and what I do not

I am not the best engineer you will read. I did not invent the ideas underneath this book. I do not have a universal method, and I have not finished the journey myself.

Here is what I can defend: this is a model I use to think about work, composed from ideas I learned from others, refined through my experience, and still evolving. Take what is useful.

Calibration cuts both ways, though. Humility is not a shrug. Some practices in this book carry decades of evidence and use behind them, and where that is true, I name the source and say so plainly. "This worked for me" marks the personal claims. It does not soften the established ones.

How to read the claims

Not every sentence in this book carries the same weight. Five kinds of claims appear, and the writing tries to make each one recognizable:

• Established practice. Decades of use behind it. The source is cited.
• Borrowed principle. Someone else's idea, named, that earned its place here.
• Personal synthesis. My arrangement of the above, marked as mine.
• Observed pattern. Something I have watched happen enough times to report.
• Hypothesis. Still being tested. The book says so where it appears.

When the text says "this is how I think about it," that is a synthesis, not a law. When it cites a name and a year, the confidence was earned elsewhere and you can go check it.

I have been lost here before. Here are the landmarks I use now.