Notes on building for the web

A practical look at where to store your app's files — managed cloud services vs self-hosting, what open-source options exist, and why a licensing change pushed me from MinIO to RustFS.

Dokploy deploys my apps, Mailcow runs my email, Postgres holds my data — and Novu and WAHA are the two I'm still wiring in. I didn't write any of it, and my whole setup now leans on it. Here's me working out whether that's a solid foundation or five dependencies I can't escape — and the one question I ask before adding another.

mailcow is installed and your first domain works. Here is how to add a second domain properly: every field in the domain form, every DNS record and why it exists, and the alias options nobody explains.

Two weeks ago a random YouTube video sent me down a rabbit hole — could I run my own email server? Turns out yes, and I did it using Mailcow on my existing VPS. Here's what I learned along the way.

I have spent a lot of time recently inside codebases written with heavy AI assistance. The code works, the tests pass, and there is nothing underneath it - no structure, no decisions, no trail to follow. Why that is harder to work with than ordinary legacy code, and where I think the line actually sits.

The AI was not the shortcut. The planning system was. Here is the documentation-first workflow I used to turn a risky 3–4 month legacy upgrade into a focused two-week clean-architecture rebuild.

Suggu turns repetitive .NET project work into safe, repeatable commands—for developers at the keyboard and coding agents working across a repository.

Autocomplete never changed how I worked — it finished the line I was already typing. An agent that reads the whole repo, runs the tests and reads the output is a different shape of tool. Here is what actually earns its keep on an Angular frontend and a .NET API, and the four things it still does not solve.

Most Angular projects do not collapse under the framework. They collapse because nobody can answer where a new file goes. A folder-by-folder walkthrough of a structure that scales, with Storybook and component-driven development wired in from the start.

I used to deploy by SSH-ing into a box, hand-writing Nginx server blocks, and running certbot from memory. Dokploy replaced all of it with a UI and a git push. Here is what actually changed, what it does not solve, and the two things that still bit me.