From the repair bench to my first deploy

I spent years fixing phones and circuit boards before I wrote my first line of real code. It turns out that habit — isolate the fault, change one thing, test, repeat — is most of what debugging software is too.

The habit that carried over

On the repair bench, you never replace three components at once and hope one of them fixes it. You test one change at a time, because otherwise you don't actually know what fixed it.

I write code the same way now. Small commits. One change, one test, one clear result.

What's next

This blog is where I'll write about that transition — technician to builder — along with what I'm shipping at Letyar Labs.