you are viewing a single comment's thread
view the rest of the comments
[+] 44 points 2 years ago* (last edited 1 year ago) (8 children)
  • [–] 40 points 2 years ago (4 children)

    If you manufactured the software then your engineers understand it

    Ah I see the misunderstanding, the engineers were sacked after they finished writing the code.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 2 years ago (2 children)

    Of course they didn't leave any documentation because management said that writing it was a waste of time

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 2 years ago (1 child)

    I see we have the same managers. Were you also advised that public facing databases were better than an API in a VPC and that 1 password shared among colleagues is easier than managing credentials?

    Don't worry, I found a new gig starting in a few weeks (out of the pot into pan )

  • source
  • parent
  • hideshow 1 child comment
  • [–] 12 points 2 years ago*

    How about a bot that types slowly, so it can have time to consider what it's going to say? Or perhaps a web page with an "Analyzing issue" status bar that takes several minutes to complete, because computers just do better if they're given time to work on a problem?

  • source
  • parent
  • [–] 2 points 2 years ago*

    Lol at the notion that you'll get to speak to any engineer when your machine breaks. Best they can do is a call center in India getting paid minimum wage that follows a script and circles around a bit between them until you either give up or they RMA your stuff to feed you a bill later for repairs.

  • source
  • parent