Why Bloat Is Still Software's Biggest Vulnerability

Re:Why Bloat Is Still Software's Biggest Vulnerability by AlotOfReading on Friday February 09, 2024 @05:59PM (#39321547)

As someone who is separately both a programmer and an archeologist, I love the concept and the books. The real skills aren't always as far apart as you'd think either. I once spent a week deconstructing hardware to figure out what assembly language a project was written in. The assembly was only documented in a TRM in a dusty filing cabinet written before I was born. Once I could read the assembly I could read the source code and work my way up the stack to start answering the actual questions I had.

[ Parent | on HN ]

Re:Why Bloat Is Still Software's Biggest Vulnerability by lloeki on Friday February 09, 2024 @06:33PM (#39321827)

The nice thing with software is that everyone gets to be an archaeologist in short order; ~6 months is more than enough...

  - Howdy! there's a bug!
  - Okie, lookie!
  *dig dig dig, stares at line 47*
  - Oh my, this horsemanure could not have possibly worked, ever! What kind of damaged wetware wrote this?!
  $ git blame
  - Oh.

[ Parent | on HN ]

Re:Why Bloat Is Still Software's Biggest Vulnerability by jonathanlydall on Saturday February 10, 2024 @04:14AM (#39324758)

I like to say that git blame is a great tool for working out that the problematic code you’re looking at was in fact written by yourself.

[ Parent | on HN ]