3 ms·
I've seen situations like these before. This is why off-site backups are so very important. I've also been in the same position of providing data from a backup
by johnklos 1y ago
I've seen situations like these before. This is why off-site backups are so very important. I've also been in the same position of providing data from a backup that someone was intentionally trying to destroy to escape responsibility.
This story even hints at a common theme that happens even when people aren't trying to destroy data - that some people will tear down whatever they inherit, then blame their predecessors for the problems that result.
- apples_oranges 1y agoBut if you don’t blame them it can also backfire. I inherited a bad codebase once and tried my best to improve it. But there was only so much time. When I left the guy after me blamed me for the still bad parts immediately.
- ipaddr 1y agoHe would blamed your new code if you rewrote. People who blame are juniors. You are not really a senior if you blame.
- jbeninger 1y agoJuniors blame. Seniors silently judge.
- pavel_lishin 1y agoIt's a proud tradition, to gasp silently, mutter in anger as you run git blame, and only discover that you're the person who wrote the code about 20% of the time.
- lukan 1y agoAh that reminds me of a classic Dilbert comic, The code mocking https://www.reddit.com/r/ProgrammerHumor/comments/195lc8/when_you_hand_over_code_to_others_for_maintenance/ https://www.reddit.com/r/ProgrammerHumor/comments/195lc8/whe... (Reddit, because Dilberts creator and his website have gone off the rails)
- teddyh 1y agoBetter link: <https://dilbert-viewer.herokuapp.com/2013-02-24 https://dilbert-viewer.herokuapp.com/2013-02-24>