3 ms·
Nice! You are correct of course, I did mis-understand your question. I suspect the minimax answer is Java. My reasoning for that is that enterprise shops both c
by ChuckMcM 13y ago
Nice! You are correct of course, I did mis-understand your question. I suspect the minimax answer is Java. My reasoning for that is that enterprise shops both consume and turn over a lot of Java programmers, this is in part to consulting gigs with Salesforce, SAP, Oracle, or IBM.
Thanks for the clear response and your excellent example. It is interesting to see what it optimizes for. I don't doubt you could stay employed "forever" at $45,000/year Java shop code monkey jobs for example. My personal conjecture is that Tech is not a 'connected graph' in the sense that not all nodes are reachable from any node, and not all paths can be traveled in both directions.
The example I am most familiar with is 'CEO taint' which is folks who get to a certain level, and then become CEOs of their own startup, where they reach a certain level of qualified success. Then, in a quest for finding their next engagement they are un-hirable because 'former CEO' isn't something you higher in to be a coder, and maybe not manager. Their only accessible nodes are 'new startup' or 'appointment as CEO to startup' or 'consultant'. If you can't get funding for a startup, and you don't have enough street cred as a 'consultant', its a really sticky place to be. The other common one I've seen is people who 'grew up' in a company, started right out of college and put in 10, 15, or 20 years, and then left as UberDistinguishedPrinciple Engineer/Scientist but were unable to find anyone who would hire them at a level and salary they could easily accept. But I'm wondering how much of that transition resistance is simply pride/wages related.