I’ve spent years building enterprise systems in the .NET ecosystem.
It shaped how I think about architecture, reliability and engineering.
I still appreciate everything it taught me.
But over time, I started to notice something.
When you want to build and ship products on your own, speed and reach matter a lot more than heavy infrastructure.
That’s where the modern JavaScript ecosystem stands out.
React, Next.js and Node let you build full products end to end.
One person. One laptop. No waiting for long deployment pipelines or giant environments.
You can ship something real in hours instead of weeks.
This shift is not about abandoning .NET.
It’s about expanding my toolkit and creating things that can reach anyone, anywhere.
So I’m starting a new chapter.
I’m learning the modern JS stack, building products in public and sharing the whole journey as I go.
If you’re also making the same transition
You’re not alone
Let’s build better things together
Top comments (4)
Thanks for reading! If you have any questions about the transition from .NET, drop them below 👇
We use .NET heavily for work and I'm curious, how do you manage without tools like Entity Framework? I guess when you're setting up databases from scratch you can do whatever you want, whereas most of our stuff is wrapped around existing SQL Server DBs.
Thanks for the question.
In my previous .NET projects we actually never used Entity Framework. Most of the systems were older and everything was built around SQL Server stored procedures and a custom data access layer. We usually worked with DataSet or DataTable and converted them into our own classes inside a DLL.
So I never relied on EF or LINQ abstractions.
Working close to SQL was already part of my daily workflow.
Because of that moving into the JavaScript ecosystem did not feel limiting. I still write SQL when I need full control and when I want a bit more structure I use tools like Drizzle, Prisma or Kysely. They are lighter than EF and they match the SQL first mindset much better.
So for me it is not about managing without EF. It is simply continuing the same direct SQL approach but in a more flexible stack.
Would love to hear if anyone else made a similar tech-stack switch. What surprised you the most?