you are viewing a single comment's thread
view the rest of the comments
[–] 59 points 6 months ago (10 children)

I program for ships (the water kind) and buddy, you ain't seen nothin'. I'm talking server infrastructure from 1991. Spaghetti code from the 80's. I had a program that had to run on a dos box, and we had to replace the whole thing because the original developer fucking DIED and no one could read his shit.

  • source
  • hideshow 10 child comments
  • [–] 14 points 6 months ago (1 child)

    I feel like a lot of people are in the bank of "why change of it ain't broke?" That's how you have people working some CNC machines on hardware and software available when the business started.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 6 months ago (4 children)

    I worked in medical electronic manufacturing. Changing a single setting for ease of use to the operator was planned as a 2 year project. Literally change a 0 to 1 in one of the files....

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 6 months ago (1 child)

    I'd imagine that one is because of medical more than anything else. There are all sorts of regulations around medical devices. That slows shit down.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 6 months ago

    Absolutely. I got well acquainted with the regulations. The sad part is it was so slow to update anything nothing got updated.

    This system needs to be operational by next week. It will be a month before its well made. This needs to be operational by next week. Ok, but then we can fix it right?

    Not to mention any changes to anything got evaluated as either a notice update, a 90 day submission, or a full submission(6 months - 2 years depending on fda, bsi and severity of change). That's in addition to the actual work. I could make a change in a afternoon and may see it in production next year.

  • source
  • parent