3 ms·
> A developer leaving the company is not responsible for a successful handover or that the documentation is correct. But if the handover was unsuccessful, it
by tablespoon 4y ago
> A developer leaving the company is not responsible for a successful handover or that the documentation is correct.
But if the handover was unsuccessful, it can call into question the skills of that developer. I mean, instead of being a "10x" developer, maybe they were actually a 1x developer that look a lot of shortcuts and wrote unmaintainable spaghetti code (or somewhere in between). Maybe they were someone who hoarded domain knowledge and refused to share it. In any case, the employer didn't realize the claimed value of that employee's work.
- AtlasBarfed 4y agoNo it doesn't, it calls into question how much redundant knowledge, code quality, documentation, and support the org values. Which 90% of the time for anything but features and UI appearance is no value. That allows the construction of micro-empires and dependence. Orgs either recognize that and provide resources, or they rely on shorter-term one man hero efficiencies, and pay the piper later. They paid the piper later. And who knows what "19" means. 19 offshores, so that's more like 6x the cost? And offshores are probably short term so they assume they'll hire one or two offshores long term which will ... maybe ... eventually get cheaper. That's the beancounter logic. So they think long term they saved money.
- gsibble 4y agoExactly. I was working 100 hour weeks, almost all spent writing code and given no time for documentation, knowledge transfer, etc.. They bet the house on me and wouldn't pay me appropriately.