3 ms·
It’s not like learning stops but the curve flattens out a lot. Another problem is that in tech 20 year old knowledge is worth way less than 20 year old knowledg
by spaetzleesser 5y ago
It’s not like learning stops but the curve flattens out a lot. Another problem is that in tech 20 year old knowledge is worth way less than 20 year old knowledge in for example cabinet making.
- PaulDavisThe1st 5y ago> Another problem is that in tech 20 year old knowledge is worth way less This is a widely held position, which sort of makes it a self-fulfilling prophecy. But I'd argue that it's not true. Most of what I know now that is really valuable isn't related to the technology of today or 1986. It's related to how to work, how to design systems, how to decompose problems, how to scale, etc. etc.
- Pokepokalypse 5y agoI refer to my resume as "a graveyard of obsolete technologies"
- canadian_tired 5y agoI could do the same. But really, it's also my value proposition. "What's that you say? Your org has a dozen crappy systems of questionable lineage and you need to migrate to SomethingFromThisDecade? Let me pick it apart for you and we can build a plan together." It's not much, but it's honest work. (and I happen to enjoy it...so win-win)
- jehb 5y agoYou might be surprised at how many companies are running 10+ year old technologies that were designed around the constraints of the 10+ year old systems that they replaced. If that's your thing, you can build a pretty strong career around being the person to keep that system humming along.
- Tarucho 5y agoBut this happens in tech management too. Last 20 years: CMMI? RUP? PMI? XP? Scrum? Design Thinking? Project to product management?