705
Sometimes, it's backwards (sh.itjust.works)
submitted 2 years ago* by to c/programmer_humor@programming.dev
188 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 years ago (1 child)

It IS bespoke internal development, not for deployment outside of the facility.
The computers running the software exist only to run this software and have no business talking to the internet at all.
IT is provided by an external third party vendor who operate on an inflexible "best practices dogma".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] 1 point 2 years ago* (last edited 6 months ago) (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago

    Sounds like you’re stuck in a worst practices mindset.

    Worst/Pragmatic.
    If I get a timeline for a feature request, then everything can be scheduled, tested, whitelisted, delivered at a reasonable time.
    That's the rarer event - normally it's more like "the scale head has died and a technician is on the way to replace it" and whilst I modify the program in question to handle this new input, hundreds of staff are standing around and delivery quotas won't be met.
    Is my position arrogant? This is the job.

    Sign your damn releases and have the whitelisting done by cert.

    I'll see if this is possible at the site in question, thank you.

  • permalink
  • fedilink
  • source
  • parent