Everything I build, in one place
Six fields, one method: understand the process before touching the technology, and build something that keeps working after I leave the room. Each one has its own page here — what goes in, how it gets built, and how long it takes.
How the work runs, whatever gets built
Every project starts in the same place: a conversation about the process itself. Where the time burns, who hands what to whom, what falls between the cracks, and what already works and shouldn't be touched. Only once that picture is clear do I talk about tools.
From there it's built in stages, so something working is in your hands early rather than only at the end. A first version you can run on a real case, fixes based on what actually happened, then extension. That's also what prevents the project that ends in a slide deck.
What you're left with is a system you operate, not a dependency on me. Training for the team, documentation of what was built, and a clear line between what you can change yourselves and when it's worth calling.