My Answer to Rebuilding

If you have read my introduction, you know my mantra: I hate rebuilding. Every time I started a new project from scratch — setting up authentication, JWT, Docker, user management, role guards — I was not building the product. I was rebuilding the scaffolding I had already built a dozen times before.

The RAD-System is my answer to that problem. It is a full-stack framework I built for myself, open source on GitHub, that eliminates everything I call "development background noise" — so that from minute zero, I can focus exclusively on business logic.

It is not meant to be the framework for everyone. It is built around the way I think and the patterns I trust after 40 years of building systems. If you share that approach, it might work for you too.

Security and Abstraction by Design

The question I asked myself when I started designing the RAD-System backend was simple: what is the code I write every single time I start a new project? Authentication, audit fields, CRUD operations, ownership checks. Always the same things. Always with the risk of getting one of them slightly wrong.

My answer was to write them once, correctly, and never write them again. That is the entire philosophy of the RAD-System backend — a NestJS layer where the repetitive 90% is handled by two abstract classes, and your job is only the 10% that is actually specific to your product.

The full source is on GitHub.

Angular Without the Ceremony

I have used Angular since its early versions. Over time I have seen the framework accumulate ceremony — NgModules, complex provider chains, state management libraries that require their own learning curve just to store a simple flag. For most applications, it is too much.

The RAD-System frontend is my attempt to use modern Angular the way it was meant to be used: lean, modular, and without dependencies on libraries that solve problems I do not have. The source is on GitHub.

Designed to Be Simple in Production

One of the things I have learned across many projects is that deployment complexity kills maintenance. If putting a new version live requires someone to remember a sequence of steps, connect to multiple servers, or have the build toolchain installed in production — things will eventually go wrong.

The RAD-System Docker setup is built around one principle: production servers should be as dumb as possible. They run containers. They do not build code. The source is on GitHub.