I moved from frontend (React.js / Electron.js) to backend (NestJS) — and I won't lie, the first few months humbled me.

I'd written backend code before. Express, REST, GraphQL. But it was a small project. No real users. No real consequences.

This time was different.

Real users. Real production environment. Real data, with all its messy edge cases.

Staging existed. CI/CD was solid. None of that prepares you for what happens when actual humans hit your API in ways you never tested for.

I learned fast: → "It works on staging" means nothing once real traffic hits → Edge cases aren't edge cases — they're Tuesday → Error handling isn't optional, it's the job → GraphQL resolvers can quietly become N+1 nightmares → The cost of a bug in prod is not the same as the cost of a bug in a small project

I broke things. I fixed things. I got paged for things I didn't think were possible.

That experience changed how I work with clients.

I don't just ship features. I think about what breaks at scale, what edge cases get missed in happy-path testing, and what decisions today become technical debt tomorrow.

If you're building something that needs to actually work in production — not just in staging — that's exactly the kind of engineer I am.