<span style="color:#323232;">At a PV node, do not cut off from any TT hit.
</span><span style="color:#323232;">
</span><span style="color:#323232;">The SPRT result of this may be different than before thanks to LMR.
</span><span style="color:#323232;">
</span><span style="color:#323232;">Bench: 5212899
</span>
This is already how the military works BC they lost the source code for ancient machines. They’ve gotta now hire reverse engineer researchers to help out
I wrote a brief manifesto on my hatred of Python because some refactoring ended up having a comma at the end of a line, which screwed me over for about an hour until I happened to noticed it.
One of my previous employers once told me (abridged)
It’s not like old times when we could slowly work to get a perfect result.
Nowadays, we need perfect results, fast.
They were asking me to do technical content writing for their website.
I quickly realised that it’s actually the threshold for calling something “perfect”, that has lowered over time.
Clearly, I was not fit for that work, because instead of just plagiarising and paraphrasing stuff from other websites, I insisted on reading up on material from multiple sources, understanding it well and then writing it down myself. That makes it pretty slow.
That was a year before ChatGPT, or I would just have used that thingy.
I agree. We’ve let the standards for what is good drop.
I think it’s mainly because the “just works” mentality has become infectious among engineers. It’s one thing when just starting out, but as you learn more and gain experience you should care more.
People do the designing and architecture and programming just because it all pays well, not because they have a love for the craft.
I think the second, slightly less strong reason is because many engineers do not know how to effectively communicate with management when something will result in terribly written software and just do it anyway. Another skill I see less and less amongst my brethren.
People do the designing and architecture and programming just because it all pays well, not because they have a love for the craft.
True.
I like programming and tend to pride myself in making good code, but when I see other’s attitude at work, it makes me reevaluate what I care about.
Perhaps this is the reason of the memetic difference between corporate code quality vs OSS code quality. When I contribute to Open Source (at least to other’s projects), I see myself try to be as considerate as possible of multiple factors that I wouldn’t even care of at work.
many engineers do not know how to effectively communicate with management when something will result in terribly written software and just do it anyway.
I imagine this is partly a result of bad and misinformed managers too though. There’s a lot out there who have 0 clue wtf you do, just that you make computer do thing yet still act like they know your job better than you
spoilerNot a programmer, but I see this all the time in other fields. And all it takes is someone in upper management only being focused on time or costs, or someone in middle management acting like they know better than everyone else.
Previous commit was some stupid easy fix I didn’t even bother compiling. Well, I should have, because it was the first time in recent memory I committed some code with a missing semicolon…
Before anyone asks : no, we don’t do reviews ¯_(ツ)_/¯
“28496 - there, it’s fucking fixed you twat waffle.”
Ticketed bug bosses son found. Dude nagged his dad who nagged us until it got fixed. Boss doesn’t review code. And for the sake of a half dozen coworkers, I hope he never does.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.