3 ms·
I'm curious - is that unique to tech? (It seems to be the common worldview from what I've seen, but I've only ever worked in tech.) It occurs to me that the Pe
by geofft 9y ago
I'm curious - is that unique to tech? (It seems to be the common worldview from what I've seen, but I've only ever worked in tech.)
It occurs to me that the Peter Principle implies basically the opposite: in companies where it applies, you're not promoted based on any evaluation of whether you can do your target job, you're promoted based on demonstrated ability in doing your current job, and a presumed ability to pick up new things as needed. If these companies handled promotions the way tech seems to do hiring (a lot of companies expect experience with large-scale deployments before they'll hire you for large-scale deployments, with specific languages before they'll hire you for that language, etc.), you wouldn't have the Peter Principle; you'd have the opposite problem of failing to hire/promote people who could be quite competent but have no experience to prove it a priori.
- rhapsodic 9y agoI think in professions that make use of lots of expensive, specialized equipment, the only way to stay up to date is through learning on the job or in a formal training/educational environment. Programming is not like that. Pick any mainstream language, and all of the resources you need to develop a deep level of expertise in it are readily available, for free or relatively inexpensively. And accordingly, many developers proactively develop deep levels of skill and expertise on their own initiative. And my observation has been that these are the ones sitting atop the profession.