5 ms·
Expertise is a weird thing. In today's world, one that changes so rapidly, it's very hard to become an expert in something and have the value of that expertise
by bane 12y ago
Expertise is a weird thing. In today's world, one that changes so rapidly, it's very hard to become an expert in something and have the value of that expertise remain valuable. It used to be that expertise in some field or area would last generations, and guild-like systems of master/apprentice developed in response. Now you can't even make it through a degree program before the things you started to learn about at the beginning become virtually obsolete by the end. Watching the front page of HN and you'll see entire frameworks and languages come and go virtually as quickly as the seasons. When I was starting out, it was fully possible and reasonable to consider becoming an expert in COBOL and one or two kinds of mainframes and make a career of it.
Expertise today requires that you start to think and operate at a higher level of abstraction in order to cover what you know, and where your knowledge might go. Or it might require you to make connections between old ideas that are still valid and new ideas as they appear. You might even be able to change career paths entirely, but things you learned as an expert in your old one might make you special and unique in your new one -- somebody with rare and unique talents. Like automating business processes in a non-technical career.
I've been thinking a lot about beliefs and belief systems recently. I'm not quite sure I have any meaningful or concrete conclusions yet, but I'm pretty sure I'm going down the path of thinking that beliefs should generally be treated and handled with extreme caution, that they're some kind of holdover from an earlier evolutionary stage -- a vestigial kind of proto-thought process wedged somewhere between pure animalistic instinct and enlightened reason.
They aren't inherently bad just like instincts aren't inherently bad, the instinct to pull your hand off a hot stove is good for example. Perhaps they some kind of optimized way of thinking that evolved when we had less hardware to compute with. An estimation system that got us through hundreds of thousands of long cold nights, alone in the world of beasts...when we couldn't quite think through everything. But now we can, and this old wetware technical debt kind of gets in the way now and again.
It tends to make us rigid and lazy in our thinking...why think when believing is less work?
Maybe it's possible to hack our beliefs be believing in the right things, by believing in reason, or believing that things should be changing, believing that we should evaluate and challenge ourselves from time to time, believing that we should feel like we're just on the edge of discomfort and force us to use this new better and harder to use equipment we've been gifted with.
- eropple 12y ago> Watching the front page of HN and you'll see entire frameworks and languages come and go virtually as quickly as the seasons. ... Expertise today requires that you start to think and operate at a higher level of abstraction in order to cover what you know, and where your knowledge might go. I'm glad you wrote this, because so many people bemoan the first quoted bit and don't take into account the second. Sure, FooFramework is out of fashion, but the underlying knowledge that a good programmer, one I'd consider an "expert", persists. The knowledge that makes a person a good programmer, the real skills involved rather than the minutiae and the whatevery bits involved in translating that knowledge and those skills into a particular use case, have personally served me well (so far) in web development, mobile development, devops, and game development.
- tjl 12y ago> it's very hard to become an expert in something and have the value of that expertise remain valuable. That may be true in programming, but that's not the only field. Much of my mechanical engineering knowledge dates from the 19th century and earlier and is still valuable. Even my FEA knowledge (which relates heavily to programming) is still good. Practically all my undergraduate knowledge is still valuable, let alone my Master's and PhD knowledge. It's quite clear that you're approaching this strictly from a single viewpoint. If you really want to think, you need to broaden your view. Even in programming there's still things that change at a slower pace. Sure there's a lot of things changing in regards to the web, but areas such as numerical methods change more slowly.
- bane 12y agoYes, of course you are correct in many senses. But I'm hard pressed to think of a field that hasn't seen tremendous change in just the time I've been working professionally let alone my lifetime! Even the art of cuisine has changed so much that some chefs I know are struggling to keep up late in their careers - it seems like all the top chefs are new and almost impossibly young. It really used to be that you could learn your skill, unchanged from your teacher, and do it for your entire natural life, passing it along to your proteges who would then do that same skill exactly the same for their entire lives. So while I'm pretty sure the basic physics you use is largely unchanged, I'd bet that a mechanical engineer for even a generations ago would have trouble recognizing much of what you're doing today. We have materials, measures, testing and production methods available to us today that would have looked like magic to somebody in the 60s. It's like comparing a flint-lock musket to a modern rifle. A gunsmith from the flint-lock era would know the basics, but his expertise would be obsolete. Even in software, most of what I learned in my undergrad CS program has stayed refreshingly relevant, but the act of writing software itself has completely transformed a half dozen times since I graduated. It means I can sit down in a new environment and learn the syntax, practices and idioms of a language and dev environment relatively quickly. But in many cases you quickly start to feel like you're treading water at the same time, having not 20 years of experience but risk having 1 year of experience 20 times unless you carefully cultivate your expertise to prevent that. My civil engineering friends seem to have similar feelings, lots of the physics and basics they learned are still relevant, but the theory and implementation, especially the huge changes in Urban planning are having tremendous impact on their ability to cultivate expertise. I have a landscape architect friend who graduated hoping to design golf courses and parks and who now spends most of his time working on energy efficient certifications (LEED) and planning for new construction and retrofits. Something that didn't even exist when he entered his line of work. Instead of becoming an expert in park design, he's become an expert in LEED certification. Even my pastry chef friend left pastry school, where she intended to make traditional French pastries, and entered a world expecting innovative techniques and ingredients catering to the allergen/wheat sensitive/low carb/vegan/no GE/whatever crowd of the month. She doesn't just make scones, she has to make 6 kinds of each scone suitable for everybody's special dietary decision. You're right in that they're all still doing mechanical physics, looking at water management, and baking things in an oven. Expertise in those subjects transcends. But being an expert in their fields is impossible because the expression of what their entire fields are are being redefined almost every day. What they're becoming experts in, and something their predecessors didn't have to do, is riding the wave of change. This is a fundamentally different kind of expertise that maybe only ever existed in human history during times of war, or great societal upheaval. "May you live in interesting times" is a curse, not a blessing. It's to be seen if this is simply the new state of things from now on or a time of upheaval that we can't recognize and things will settle down at the other end.