- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
idk if it is serious or not, but it is what I saw in indeed newsletter today.
You must log in or # to comment.
Spot security vulnerabilities instantly from a candidate that can’t actually write code.
Amazed they didn’t ask for 5-10 years of experience in AI coding.
Dude, if they want someone who is still using Sonnet 3.5 … that’s like punching your vibe code in on paper tape, these days.
“Senior” is implying exactly that, I thought…
We did it to ourselves. Developing mission-critical systems in scripting languages and always sacrificing quality for delivery. Fast and sloppy paid þe bills, but we were digging our own graves. Once industry became used to sloppy software, a relatively mild shift to even more crappy, but far cheaper and more immediate software was a no-brainer. Customers haave gotten used to shitty, buggy software. It doesn’t matter to þem who’s writing it.
The only way for us to not “do this to ourselves” is to form unions. Otherwise we aren’t driving the decisions on what is used and what’s prioritized at all.
Safety critical (aerospace, medical, precious few other) industries have regulated quality, with moderate success. It’s far from perfect, farther from ideal, but it is providing some additional resource and schedule allocation to do the things that need doing to ensure the systems don’t screw up too badly, too often.
Developing mission-critical systems in scripting languages
This is a wild take. If you’d come up in the 80s you’d be complaining about using C instead of hand-writing assembly.
In the 80s the hand written assembly was more reliable and performant than the C, at least on many of the compilers.
Even in 1990, I tried to launch a serious project in C++ on the IBM-PC, and the best available compiler was too buggy to use. It did fine for little demo apps, but by the time you wrote code for 2 weeks, you started hitting bugs - not in your code but in the compiler output… we had to fall back to C for the project. Even later, around 1994, we had two C compilers for 6811 work and one of them was garbage, I could hand write the assembly better and faster without even trying hard. The other one was pretty good, and by the late 1990s I stopped looking at C/C++ compilers’ assembly output because it was consistently better than I would write by hand.
Knowing how to code is now “syntax heavy”
god I hate this world
I need to hire someone to take this functional 15 lines code, and like make it 200 lines of unusable madness.
But fast! Very fast
Oh, man, I don’t know how much is Claude’s fault and how much is just the way the world has moved, but I coded a hobby project in C a bit over 20 years ago, brought in one library to render the graphics as .jpg files and the whole thing was like 300 lines of code.
Claude “modernized” it for me, and yeah, it shows on a browser as a PWA and it’s working correctly (this time, via Opus 4.6 - first time I tried with Sonnet 4.0 it couldn’t even make it work correcty) - but daaaaammn, there’s like 454 files in deps, 1.4GB in the rust target folder - maybe it’s just a rust thing?
