Thinking about productivity at job, I wonder whether there is a trade-off for the company, of a similar type like when you have a trade-off between short-tem productivity and long-term productivity. Maybe what is most productive (long-term) for the employee is not what is most productive (long-term) for the company. Like, maybe if you get too good, then the rational choice for you would be to leave (perhaps to start your own company). On the other hand, if you are perhaps less productive but more easy to replace, the company gets less value from you, but it can keep going if you leave for whatever reason, which also gives you less of a leverage in negotiation.
I think about this because you write about power of specialization, but in the software development I think I see the opposite trend: specialists being replaced by “full-stack developers”, who are later unified with system administrators into “DevOps”, who later become “DevSecOps”, and god knows where this will end, maybe one day we will see a “DevSecOpsManagerAccountantSalesmanJanitor” and I sincerely hope I will be retired by then.
I found that all of them are 5% signal and 95% noise and their most important messages could have been summarized on 5 to 10 pages respectively. Ironically, a book that supposedly tells you how to save time inflates its content by out-of-context quotes, analogies that don’t even support their point, personal stories that also don’t support their argument, pseudo-scientific explanations which broadly support their claim, and incredibly lengthy descriptions of ideas that can be entirely described in one short sentence (maybe they had to hit a page count).
Yeah, I have seen books that had less content than this post. I suppose you have to produce a certain minimum amount of pages, otherwise people would not pay for the book (or would even read it in the book shop for free).
This was awesome!
Thinking about productivity at job, I wonder whether there is a trade-off for the company, of a similar type like when you have a trade-off between short-tem productivity and long-term productivity. Maybe what is most productive (long-term) for the employee is not what is most productive (long-term) for the company. Like, maybe if you get too good, then the rational choice for you would be to leave (perhaps to start your own company). On the other hand, if you are perhaps less productive but more easy to replace, the company gets less value from you, but it can keep going if you leave for whatever reason, which also gives you less of a leverage in negotiation.
I think about this because you write about power of specialization, but in the software development I think I see the opposite trend: specialists being replaced by “full-stack developers”, who are later unified with system administrators into “DevOps”, who later become “DevSecOps”, and god knows where this will end, maybe one day we will see a “DevSecOpsManagerAccountantSalesmanJanitor” and I sincerely hope I will be retired by then.
Yeah, I have seen books that had less content than this post. I suppose you have to produce a certain minimum amount of pages, otherwise people would not pay for the book (or would even read it in the book shop for free).