a lot of devs just don't have the first clue of what they are doing

they haven't put in the work

they'll blame absolutely everything else (language, framework, pattern, etc.) instead of actually putting in the work and making it easier for themselves

sad

https://devrant.com/rants/6183818/...
🤡

said by the guy who over-hyped his code and when got confronted by actual devs ... resorted to "Well I guess there is always room for improvement."

Don't you literally sell courses to beginners? If anything, you should hand your courses for lower cost and help newbies rather than bitching and moaning about them.

Real seniority is when you realize that it isn't just you but that coding is actually an objectively hard problem and faulty neuronal networks like us have basically zero chance to get it right on first try no matter how hard we try just because of the absurd amount of paramters involved in any nontrivial software.

Don't expect to git gud just by working hard. And don't assume that all the permanoobs didn't work hard. A lot of them do work hard but they will still never git good.

If a dev has a good foundation of skills I will forgive them for complaining and blaming the problem on some specific framework etc. Even if the fix is ”clearly stated under heading 4 of the readme” as devs we have soooo many pieces or tech to deal with - we have the right to hope pieces work as we hope. And we can’t be expected to go down every rabbit hole and become experts on every piece we use

@electrineer wow! Brutal 😂

@jestdotty I did this for thirty years and nope, bug-free code still is just a myth. What really helps is making it easy for me and the compiler to spot bugs as and after they happen. Static analysis, optimizing for minimal cognitive complexity, writing tests for stuff that is complex but easily testable and shit tons of experience do help a lot. I also do a lot of manual testing and read and understand all my code again before committing...

But nope, it isn't bug free. And as long as i don't do actual mathematical proofs for each line (which isn't feasible), it probably won't ever be. But because my code is written to be read by humans, if a bug gets found, i can normally easily locate its cause and fix it.

I think, i got gud. But i didn't git gud at anything else. And i definitely don't expect that everyone can git gud at software development.

@SidTheITGuy after monthhs still going on about that generic code you don't understand? Must be that it deeply bothers you how you still don't understand it.

What were the "critiques", oh yeah "using a const when the variable is used only once" obviously people don't know what code DX is.

But no, you're right, lets go to the middle of the line at column 70 to change the hardcoded string instead of assigning it a variable name so we can clearly see what the example case is doing.

🤡

@electrineer ah yes let me "put in the work" to make a pull request for env variables to work again

we all know how fast pull requests get merged into react

🤡

@fullstackcircus that's a response to your own rant, not my comment.