>nooooo clean code is bullshit and it doesn't matter at all noooo
>noooi i don't want to get a job i want to be like my heroes and lbe a rockstar coder even though i can't do hello world
Alright, LULZ. If you're SO sure 'clean code' doesn't matter, then try to decode this thing.
https://github.com/kevinlawler/kona/blob/master/src/kx.c
This is what you get when you think clean code is useless.
Why the fuck are there so many clean code threads recently? Which e-celeb are you fags shilling this time?
see
also someone mentioned "uncle bob" in that thread, that comment got a few you's, so it got made into at least three threads, even before the original comment 404'd.
this has to be minified or obscurified
you can't convince me someone wrote 1k LOC like this
It's an actual programming style, APL/K style. The people who do this claim it's far more efficient, both mentally and computationally.
Some nagger said it sucks and now every NEET in this board says it sucks. Someone has to set the record straight.
>APL/K style
writing C in pure autism style had unreadable results, who would've thought?!
>both mentally and computationally.
if(g) cd(g);
if(u) cd(u);
if(v) cd(v);
>modular, carefully architected code, just like clean code nerds advocate for
>except the variable names are short and nothing is documented
yes, this really "owns" the clean code haters
My company shared a video of uncle bob from the clean code series, by the end I had cancer.
He kept repeating buzzwords while moving from the car to the kitchen to the fucking treadmill.
Fucking boomer.
At work someone mentioned uncle bob in the Teams chat and some onions dev immediately replied that uncle bob is problematic because he's a sexist and racist and should not be mentioned.
Letting people tell you how to format your code is the most reddit thing I've ever heard of.
>Clean Code
Ah yes, 100x slowdown just to make your code look pretty!
>t. intern that didn't get a return offer because his code was too shitty
But enough about you.
>that book
decent book but for me it's picrel
I unironically got rejected from 2 jobs because I said that OOP sucked and that you should use imperative style. Apparently I came across as "aggressive" in both interviews. I fucking hate OOP fags so god damn much. Got another interview tomorrow, I'll just lie to get the job if they ask me about OOP again.
Shill
>Shill
Shill for what? They asked me about "OOP fundamentals" and I told them that I didn't know them, and that OOP is bad, leads to poor performance, and should be avoided with imperative programming taking favor.
Referring to the next interview, just going to shill and say you love that goyslop
Ah okay, yeah that's my plan. I thought you were calling me a shill lol.
Yes, shill the OOP! I then once you in reverse uno that bitch
>> I told them that I didn't know them, and that OOP is bad
> Doesn't know OOP, says it's bad
lol. Please read about it and form your own opinion instead of copying what is said in LULZ.
saying that OOP sucks is one thing.
not knowing OOP fundamentals and then saying that OOP sucks is another.
you're wasting the interviewer's time.
you're stupid, buddy.
all code should by default be clean and maintainable. if performance is a concern, localize and optimize the hot paths based on profiling results.
absolutism is cringe. use your common sense for whether or not certain clean coding principles are good or not in that context.
i know its hip to flamewar but clean coding is often subjective. the biggest example of this is knowing when to refactor to multiple methods/functions.