As a frontend developer, I thought backend was just "sending data to the frontend." Oh, how naive I was. 😅
Recently, I decided to level up and dive into NestJS + Prisma for backend development. Here’s a hilarious (and slightly painful) recap of my journey.
Phase 1: “How Hard Can It Be?”
Me, confidently installing NestJS:
npm i -g @nestjs/cli
nest new my-backend
Feels good. Feels… easy. 😌
Then I opened the main.ts file and saw decorators, modules, controllers, and services.
Frontend Me: “Where’s the App.js and why does everything look so… serious?” 😳
Phase 2: Prisma, Why You Betray Me?
Prisma ORM? Sounds fancy.
Me: "Okay, let’s just create a simple user model."
model User {
id String @id @default(uuid())
name String
email String @unique
}
Then I tried to migrate the database:
npx prisma migrate dev --name init
🔥 BOOM. ERROR. 🔥
Prisma: "You must define a database URL."
Me: "Bro, I thought we were friends?" 😭
Phase 3: Authentication – The Final Boss
Frontend: “Just send a token, bro.”
Backend: “Hash passwords, verify JWTs, handle refresh tokens, protect routes, configure CORS…”
Me: "I just wanted to build a to-do app 😭."
After 5 hours of debugging, I finally logged in successfully… only to realize I forgot to hash the password before saving it. Now, passwords are stored in plain text. Hacker’s dream. 😭
Phase 4: When It Finally Works
After countless YouTube tutorials and Stack Overflow sacrifices, I finally got my API running! 🎉
Tested it with Postman, saw a 200 OK, and felt like a backend GOD.
Final Thoughts: Should You Try Backend?
✅ If you enjoy suffering.
✅ If you want to feel like a hacker while writing SQL queries.
✅ If you want to flex that you know “full-stack.”
On a serious note, learning backend completes your dev skills and makes you appreciate the work backend engineers do. Would I do it again? 100%. But I’ll always respect my frontend roots. 🙌
💬 Your Turn!
Frontend devs, have you ever tried backend? How did it go? Let’s share our pain (and wins) in the comments! 😂
Top comments (25)
This pain is real 😢 I once tried connecting a simple php application to my frontend and send data to mysql database, took me 2 hours to figure out the error.
But it did work 😅 This is true once we know how backend works writing a cleaner frontend becomes easier ✨️
This was a good read 📚 Keep it up 🌟
Haha, I feel you! 😭 Backend errors have a special way of making us question our life choices. Two hours for a PHP-MySQL issue? That’s actually a win.
And you're absolutely right! Once we understand the backend logic, we start writing frontend code that’s API-friendly, optimized, and doesn’t send 500 unnecessary requests per second. 😂
Thanks for reading! 🚀 Keep building, keep breaking things (responsibly), and keep growing! ✨
😅
Haha, looks like we both know the struggle too well! 😆
Oh, absolutely! If struggling were an Olympic sport, I’d have at least three gold medals by now. 😆
Hahaha, same here! 😂 We’d be the GOATs of debugging struggles. 🏅🏅🏅 Someone should sponsor us—maybe Stack Overflow or GitHub? 😆
Hahaha, exactly! 😂 We deserve lifetime premium memberships on Stack Overflow and GitHub Copilot for our legendary debugging struggles. 🤣
Maybe even a Netflix documentary: "The Debugging Diaries: A Tale of Infinite Console Logs." 🎬💻
What do you think—should we start a GoFundMe for our struggle sponsorship? 😆
OMG, "The Debugging Diaries" needs to happen! 🎬💻 Starring us dramatically staring at the screen, whispering "but it was working yesterday..." 😭😂
And yes, let’s start that GoFundMe—sponsored by Ctrl + C, Ctrl + V University and Stack Overflow Warriors Association. 😆
HAHAHA yesss! 🎬💻🔥
Opening scene: Dark room, screen glowing, tired eyes staring... 😩
"It worked on my machine..." whispers in despair. 😭
Mid-scene: Dramatic background music 🎻
Stack Overflow tab: "This question has been asked before. Marked as duplicate." 😵💀
Final scene: We copy-paste from ChatGPT, pray, and hit refresh... 🫠
"AND IT STILL DOESN’T WORK!??!" 🤯
Sponsored by:
✔ Ctrl + C, Ctrl + V University 🎓
✔ Stack Overflow Warriors Association 🛡
✔ The “Just Restart It” Tech Support Team 🔄
Let’s pitch this to Netflix ASAP. 😂🔥
HAHAHA this is GOLD! 😂🔥
We need Morgan Freeman to narrate this masterpiece:
"In a world where bugs lurk in every line of code... two developers fight for their sanity... armed with nothing but console logs and sheer desperation." 🎬💻
Final twist: The bug was a missing semicolon. ROLL CREDITS. 😭😂
Netflix, CALL US. We have a blockbuster on our hands! 🍿🔥
Funny 😄
Haha, thanks, Fredrick! 😆 Backend struggles are too real, but at least they give us good stories to tell. 😂
Have you had any recent “WHY IS THIS NOT WORKING?!” moments in coding? Let’s share the pain. 😅
Always !! My case is reversed though, I experience moments like this more on the frontend
CSS 😅
Ohhh, CSS—the true final boss! 😅 One minute, everything looks perfect; the next, one missing semicolon turns your layout into modern art. 🎨😂
or try something like
font-family: "var(--wp--preset--font-family--source-sans)";or prepend.to a CSS class name in your HTML markup: neither makes sense, but both are formally correct, so no stylelint warnings in the editor 😅I still prefer CSS debugging over "500 Internal Server Error" =>
tail /var/log/error.log=> spend 2 hours trying to find a directory where that specific server puts its error logs, where that's configured, and if I even have sufficient permissions to read that file.Haha, so true! 😂 CSS may be weird sometimes, but at least it doesn’t hide errors in some deep, mysterious folder.
Spending hours just looking for the error log instead of fixing the error? That’s next-level pain. 😭 I think I’ll stick with CSS struggles! 😆
At the begging, I was thinking how fronted can be connected with backend?
Miss those days!
Ahh, the golden days of innocence! 😂 Back when we thought connecting frontend to backend was just "send data, get data"—before CORS errors, authentication headaches, and database migrations shattered our dreams. 😭
Miss those simpler times, but hey, look at us now—debugging like pros (most of the time 😅)! 🚀🔥
Ahh, really missing those days but still enjoying my current works. That’s the life of a programmer.
Totally! 😅 There’s something special about those early days, but honestly, the journey is what makes it all worth it. Every new challenge is just another chapter in the adventure of being a programmer. 🚀
And hey, as long as we’re still enjoying the ride (and maybe yelling at our screens sometimes 😂), we’re doing something right!
The struggle 😅
Haha, the struggle is too real! 😅 But hey, what’s coding without a little bit of pain and a lot of debugging? 😂🔥
dasdas
sas
s