Menu

I stopped rebuilding the same .NET backend every project (here’s what changed)
📰

I stopped rebuilding the same .NET backend every project (here’s what changed)

DEV Community·Ayman Atif·7 months ago
#yDxxPMnF
Reading 0:00
15s threshold

A couple of years ago, every new .NET project I started looked exactly the same.

The first few days were always the same routine:

set up JWT auth

add roles

figure out refresh tokens

recreate the folder structure

It felt productive at the time.

But looking back, it was just repetition.

The worst part wasn't even the time I lost.

It was the same small mistakes that kept coming back over and over:

auth edge cases

inconsistent structure across projects

temporary decisions that somehow stayed forever

Every project started out messy before it even had a chance to become something good.

At some point, I just got tired of it.

So instead of rebuilding everything from scratch again, I created a base system I could reuse on every project.

A simple rule: if I have solved it once, I should not have to solve it again.

I ended up with something like this:

a Clean Architecture structure auth already wired up with JWT, roles, and refresh tokens

a predictable project layout

no more "I will fix this later"…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.