Earlier quoted context omitted.
As a SW developer you provide two benefits to the company: - the build phase: develop spaghetti code - the maintain/insurance phase: maintain the spaghetti code and keep it up to date with the software package dependencies required by the spaghetti code In the long term its easier/cheaper to have the person who originally wrote the spaghetti code be around to maintain and add one off small feature improvements to it…
There's one more reason - the one I use to rationalize my idleness to myself: in addition to our work output, the corporations are also paying us to be a part of their "reserve army". We might work 3-4 hours a day, but when things escalate, the company taps into its reserves to get stuff done. Having doldrums about that is like soldiers worrying they only spend 3 hours a day in combat
"Google has a secret ‘bench’ program that keeps execs at the company even when they’re not leading anything"
https://venturebeat.com/2015/05/09/google-has-a-secret-bench...