TTP

The cursor blinks at the top of an empty file.

Before the First Keystroke

It is two in the morning. The house is entirely asleep. I have just run touch feature.tmpl.

There is a specific physical sensation in the chest right before the first keystroke drops. If you sit still enough to measure it, you can catch it. It feels exactly like the sound of rain.

Not the storm. Just the shift in barometric pressure. The sudden, quiet realization that water is about to fall.

Scaffolding as a Raft

This is the domain of TTP. The scaffolding we build before the actual work begins. Before the logic, before the state management, before the clever abstractions that will inevitably leak, you have to lay down the shape of the container.

A template is a boundary line drawn in the dirt. A to-do list is a contract with the person you will be at 9 AM tomorrow, when the coffee hasn't hit yet. A plan is the lashings on the raft.

You don't write these to be clever. You write them to keep from drowning. If you are going after something pale and enormous past the shipping lanes, you need a deck under your feet.

Manifestation as Scope-Setting

Some nights, setting up the .tmpl is just typing. Muscle memory. Other nights, it borders on Prayer. You declare the variables you desperately hope will resolve. You write the acceptance criteria for a system state that currently feels impossible. Manifestation as scope-setting. You name the outcome precisely enough that you'd recognize it if it walked into the room.

The blank file is not an enemy to be conquered. It is a weather system.

You set the boundaries. You write the plan. You snap your fingers. The first test fails. The rain starts. You write the smallest thing to turn it green.