3 ms·
Way too much specific knowledge about code/processes doesn't translate well across firms. If you view being indispensable as a formula for job security, rather
by noisy_boy 5y ago
Way too much specific knowledge about code/processes doesn't translate well across firms. If you view being indispensable as a formula for job security, rather than doing that for code/processes, do it for business knowledge. You'll still be considered very valuable, you'll get a lot more exposure/recognition to/from the decision makers, your deep knowledge will translate across firms and you'll be considered more valuable the older you get which, instead of having to deal with ageism, will open up more avenues like switching to being an expert consultant while having the freedom to be choosy about the kind of projects you do.
Of course, this hinges on the requirement that you actually care/like knowing about the business side of things and are willing to spend the time/effort towards learning (which isn't super common among techies). Sometimes, the opportunity simply isn't there or not encouraged.
- chii 5y agoand this job you describe is the CEO (or CTO, or whatever CxO level people). It is indeed indispensable - a firm shows a poor signal if they have to switch CEOs, or one gets fired, or resigns without a good replacement. The problem is that there's usually only 1 CEO to a firm, and not everybody can get to that level.
- civilized 5y agoWhere is this company where the C-suite has the only people who Know The Business and everyone else is just a coding monkey? Maybe at a tiny startup, but outside of that, I wouldn't expect to see it.
- alar44 5y agoManufacturing. A lot of times the guy invented and built the product himself along with the rest of the business over the years.
- JimBlackwood 5y agoHow would you go about learning the business side? Coming from a more business oriented team, it’s something I definitely struggle with.