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

#programming

threaded - newest

oleorun@real.lemmy.fan on 16 Dec 15:21 next collapse

Someone wanted the Milton life.

troybot@midwest.social on 16 Dec 18:57 collapse

It’s like Superman III

shoulderoforion@fedia.io on 16 Dec 16:02 next collapse

the english syntax of this article gave me an aneurysm. was this ai?

Sir_Kevin@lemmy.dbzer0.com on 16 Dec 18:46 next collapse

Yeah I got two or three sentences in and just closed the window.

Steve@startrek.website on 16 Dec 20:20 next collapse

Buffalo.

breakcore@discuss.tchncs.de on 16 Dec 21:04 collapse

I took a look at the “coder” and said no thanks.

perviouslyiner@lemmy.world on 16 Dec 16:07 next collapse

en.m.wikipedia.org/wiki/Double-entry_bookkeeping f.t.w.

litchralee@sh.itjust.works on 16 Dec 17:20 next collapse

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.

mox@lemmy.sdf.org on 16 Dec 20:09 collapse
CarlMarks@lemmygrad.ml on 16 Dec 17:09 next collapse

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.

ByteOnBikes@slrpnk.net on 16 Dec 21:25 collapse

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.