Most writing about software process is about teams: how to plan the work, review it, and release it. Those choices are often not yours to make. How you work as one engineer always is.
This site is about that part of the job. These are personal standards: habits for writing, testing, and shipping code that work in any team, any process, and with any tools, whether you are in your first job or working toward principal.
I'm Erik Gassler. I taught myself to program in 2007, and I've been a software engineer ever since, at companies from a four-person online shop to Microsoft. Today I lead UI work at Opyn Health and build a game engine in Rust.
The way I work, small and tested changes pushed to production several times a day, was never a rule a team handed me. It was a set of habits I kept from one job to the next. On this site I'm writing those habits down, so you can try them in your own work. The first pages are on their way.
My book, CASE: Continuous Agile Software Engineering, lays out the twelve tenets behind how I work: keep it simple, build in small steps, test continuously, and automate what you repeat.
Get the book on Amazon
For how a whole team can work this way, see Continuous Agile Software Engineering, the companion site for the book.
You can also come chat with us on the Stoic Dreams discord server.