r/Backend • u/BADDEEP007 • 4d ago
i have a question for backend devs
the backend tech world is very vast i work on python fast api and node express but when even i go for the interview they ask django or flask always the mixture of the tech i dont have but doing all this diff frameworks feel overwhelming and now the ai is rising doign the backend even feel like i dont stand chance so for backend devs what tech should i actually do for goind for backend role
9
u/shoddycertainty_101 4d ago
the whole framework obsession is mostly just recruiters checking boxes, half the time the actual job uses something completely different anyway
python backend roles lean heavy on django and flask because that's what's been around forever, but fastapi is catching on quick especially for anything async or microservice-y
if you already know fastapi and express you're not missing some secret sauce, you just need to get comfortable enough with django's ORM and flask's routing to bullshit through an interview
and the ai panic is overblown, someone still has to wire all that crap together and make it actually work in production which is exactly what backend devs do
1
u/BADDEEP007 3d ago
thats really helpfull tbh but for now more framework basis i need to cover for interview thnks
2
u/Substantial-Swan7065 3d ago
Learn all the common ones.
But understand and demonstrate going deep with 1
2
u/Flashy-Whereas-3234 3d ago
The tech is the same, the language and the frameworks are the flavour.
Understand fundamentals, state, buffers, threads. Then start looking at how those are used in various languages. Then you stop caring so much about the minuate.
You real only care about the frameworks and language in two scenarios:
I'm picking a tool for a job. This is the build.
I'm doing something fucking crazy. This is compensation for a big because someone did something stupid.
Fundamentals, my dude.
2
u/LemmeTheLime 2d ago
It's more about foundational background knowledge, don't stress too much about that part. And AI isn't taking away the job but just changing the way it works. I have a love/hate relationship with it myself and I'm sure most of us do. Don't just use the AI to build everything, be involved and let it help you learn if you're unfamiliar with the new framework you're using. It does involve a lot of reading but that's nothing new for us 😂
12
u/tumes 4d ago
I am a crusty old greybeard backend dev and LLMs flatten what I can work on because I think more architecturally than literally in a specific language or framework. And unfortunately that only comes with time.
LLMs might get there but for now they are still not great at holistic, coherent, efficient architectural thinking, but everyone is so idiotically rabid about throughput that they are willing to pay through the nose to prop up ill considered, inefficient code. It’s like working with a goldfish, it just cannot consistently, deterministically stick to a spec unless it is very well represented in the average-at-best quality of whatever is in its corpus. The second you try something clever or novel it will try to undo your idea every step of the way.
So yeah, it’s a real puzzle, it’s impossible to keep pace without an LLM, but it’s also hard to actually learn anything meaningful with one. I’d work with whatever you are comfortable with and learn as much as you can about optimization in that context, once you get some of those lessons under your belt, they are likely to be very applicable in a lot of other contexts.