Because the studio is small, the person listening to your needs is the same person writing the code — no handover where details get lost. This blog is not a sales page: it holds working notes, the calls I made, the reasoning behind them, and the parts that turned out wrong.
How I work
Understand first, build later
Before touching code, I make sure the problem is clear: who uses it, which part fails most often, and what a good outcome looks like.
Ship in small steps
The first version is as small as possible, but already usable. Feedback from real use beats a thick document.
Hand over cleanly
The code, documentation, and server access belong to you. I do not lock projects to keep you dependent on the studio.
What I hold on to
- Write and build it straight. If something is untested, say it is untested.
- Simple first. If one file is enough, three is too many.
- One real example beats ten lists of tips.
Tools
Not a required stack — just what shows up most often in the studio work.
- TypeScript
- Astro
- React
- Node.js
- PostgreSQL
- Docker
- Git
- Figma