How is coupling backend + frontend as a single nextjs app a good idea? What the fuck is this?

What if you have to create new replica sets of a backend because of high load pressure? What about load balancers?? What if i want my backend to be a microservice? How do i unit test the backend if its cluttered with frontend? WTF IS THIS

WHY DID NEXTJS THINK THIS IS A GOOD IDEA AND WHY DO SO MANY DEVS LOVE THIS IDEA AND GLORIFY NEXTJS?

Nextjs seems like the type of framework that was built by a frontend web developer who just refuses to learn backend technology at all costs.

---

its been a few hours and the concept of nextjs is bending my mind rn. I thought nextjs is just another frontend framework. A react killer. Only to find out its both a backend + frontend framework.

Cluttering backend stuff into frontend is gonna get messy no matter how much you try to modularize the code. Am i lost or am i right???

---

Scratching my head over nextjs. Looks like a great framework for small-mid project but definitely not large project. The more shit the project needs the more messy shit become. Angular has modularized all of this in separate folders -- components services guards interceptors (now new stuff coming called Signals) etc. All of it is separated in individual folders and kept frontend-only. Simple enough. No backend clutter

---

Can i even use nextjs strictly as a frontend framework while it uses my custom backend built in java spring boot? For example use nextjs /api/ folder to handle custom routes built outside of nextjs framework?

Am i insane here

Is django worth learning? What's the best backend framework according to you to make great software

All is well until one of the interviewers starts dropping questions like:
- Where do you see yourself in x years
- What gets you out of bed every day
etc.

that give you some nice mid interview existential dread.

I hate it when people don't understand that programmers are prone to depression just like anyone else in other professions.

And my blood literally boils when someone says "Stop overthinking". Like bro, overthinking is literally how I make a living.

If I stop thinking about how my code can fail, I no longer can make a living out of this. I'll be no better than a handicapped PTSD possessed war veteran.

Also, IMO, you're born with an overthinking mind. It's not learned or acquired from an influence. I wish I could stop overthinking, but I have to accept it's beyond my control and try to tame it best I can.

It just sucks. But it is what it is. I know my head is spitting words out at full capacity right now, which just leads to depressed thoughts, and it will calm itself right down after some time.

The moment I see a mention of "preferred pronouns" on your resume, It's gonna get thrown in the bin, straight up.

I don't want my colleagues/team members to tiptoe around you.

I'd like to use snake case like everywhere. Got that from rust.

Now in typescript, but seeing libraries and baseline core libraries in camel case, I end up going back to camel case.

I guess consistency is more important to me

Just because Elon Musk is acting like a horse let loose in a hospital over at Twitter does not suddenly give all employers the right to treat us like animals. I will not give you double the work performance for the same amount you agreed to pay me. I will give you the bare minimum and until you pay me more, you will not get more, and even then, what makes you think I will give you more? I rather work less hours a week rather than continue contributing to keeping the corporate machine running just so that you can stuff you and your shareholder's pockets rather than helping your employees, who by the way are your customers too! Why be loyal to you when corporations are not loyal in return?!

#CorporateCringe

a dude just DROPPED the whole Fu**ing mongodb cluster. like Right Now.

multiple databases, expanding multiple projects.

fortunately in dev. but dunno how much data is recoverable.

A few Challenges at my job:
- a CEO with zero tech skills and zero memory.
- a sysadmin with literal brain damage and epilepsy (but he's great, we just have had to learn how to deal with it)
- another (volunteer) sysadmin who we call @God on Slack and who usually only shows up in extreme crises.
- the budget of a tiny organization, the web traffic of a huge site.
- incoherent business logic subject to the whims of volunteers and the loudest users
- a main revenue stream that contradicts our main mission.

it's fun! woot.

Don't you love when the designer can do their pretty shit without consulting you and then the client ask you why the shit the designer made looks so different.

We were in a meeting today and it came my turn to talk.

me: "I am working on something not fun. I am tracking down a bug in X software that a customer has issues with."
boss: "It is like an easter egg hunt."
me: "Yes, but instead of eggs I am going to find a pile of crap."
boss: "Laughs..."
me: "Its not chocolate..."
boss: "next..."

The original code I am wading through is very likely my boss' code.

Manager: How come the intern does way more tickets than you?

Dev: Because you told me to only give him the easy ones since he either can’t do them otherwise or takes too long on the hard ones

Manager: Well how is he going to learn if we only give him easy ones?

Dev: That’s what I told you when you orig—

Manager: Assign him ALL of the hard tickets on your board immediately!

*Tickets closed per day drops significantly*

Manager: WHAT IS TAKING SO LONG ON THESE TICKETS!!!!!

Dev: …