you are viewing a single comment's thread
view the rest of the comments
[–] 21 points 2 years ago* (1 child)

You’d be surprised with inheriting tech debt. Quite often there’s no documentation, the last person to log in to the system is an admin that quit 3 years ago, but it doesn’t much matter because that’s only for a direct console login which normal users don’t do when accessing the application. With tribal knowledge gone and no documentation, only when you pull the network for a bit do you discover that there was this one random script running on it that was responsible for loading up all the needed data in the current system, when 9 of the other 10 times those scripts were no longer needed.

In a perfect world you’d have documentation, architecture and data flow diagrams for everything, but “ain’t nobody got time for that” and it doesn’t happen.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 2 years ago

    Had that the other way around recently. A docker container failed to come back up after I had updated the host OS.
    Was about ready to restore the snapshot, when I looked further back in the logs on a hunch.
    Turns out that container hadn't worked before the update either. The software's developer is long gone, and no one could tell me what it was supposedly doing.

  • source
  • parent