Coder wrote a bug so bad security guards wanted a word
(www.theregister.com)
from cm0002@lemmy.world to programming@programming.dev on 16 Dec 15:14
https://lemmy.world/post/23203488
from cm0002@lemmy.world to programming@programming.dev on 16 Dec 15:14
https://lemmy.world/post/23203488
#programming
threaded - newest
Someone wanted the Milton life.
It’s like Superman III
the english syntax of this article gave me an aneurysm. was this ai?
Yeah I got two or three sentences in and just closed the window.
Buffalo.
I took a look at the “coder” and said no thanks.
en.m.wikipedia.org/wiki/Double-entry_bookkeeping f.t.w.
Unabashed plug for GnuCash. It’s FOSS, double-entry, and capable enough for oddball personal finances or business finance, with all the spreadsheet exporting one might need.
Related:
news.alvaroduran.com/…/engineers-do-not-get-to-ma…
That’s a process error, not an individual’s fault. Sounds like not a single person reviewed the code, they just said, “sounds good, deploy!” on a major production system.
You can be certain that there are tons of other bugs in the system that just have more subtle effects.
I’m struggling to understand this story.
I get the idea. But the way it was written has a “I heard from a guy who did a thing that looked like this…”
Maybe it’s written that way to protect the privacy/trade secrets. But it also makes it hard to have any takeaways beyond why a dev team approved of pushing code like this to prod with minimal testing.