3 ms·
I think there needs to be a clearly defined difference here between professionals and experts. You can be a professional in the field, but until you understand
by mikewarot 3y ago
I think there needs to be a clearly defined difference here between professionals and experts.
You can be a professional in the field, but until you understand all the layers of abstraction, you aren't an expert. You can't diagnose those deep problems and fix them.
Professionals are paid to work in an area, and are thought to know enough not to be horribly dangerous.
Experts, on the other hand, are supposed to understand and have some competence in all the layers of complexity/abstraction present.
It can take decades to reach expert status in a given area.
A few weeks ago I had occasion to talk with a working computer security professional, and asked him about data diodes[1], and often they are used... he'd never heard of them. Often here on HN, I make comments about capability based security[2], and everyone mistakes it for the permissions flags on smartphones. This tells me there aren't many experts in the field of computer security.
The same is true in other fields, you can be a CNC machinist, but until you know about the Whitworth 3 plate method[3], you're not an expert.
[1] https://en.wikipedia.org/wiki/Unidirectional_network https://en.wikipedia.org/wiki/Unidirectional_network
[2] https://en.wikipedia.org/wiki/Capability-based_security https://en.wikipedia.org/wiki/Capability-based_security
[3] https://www.wadeodesign.com/flatness-3-plate-method.html https://www.wadeodesign.com/flatness-3-plate-method.html
- phkahler 3y ago>> You can be a professional in the field, but until you understand all the layers of abstraction, you aren't an expert. Let's not inflate titles here. I've noticed what the author is writing about and will offer another example. Remember when the bad-guy hackers used to make hacking tools and exploits available for free? Before that was big business? Then a bunch of kids would leverage their hard work to cause trouble. Do you recall what those guys were called? Script kiddies. A lot of so-called professionals these day are little more than script kiddies. That's not to say they aren't effective or useful (the old hackers caused plenty of trouble) but they really don't know the internals of the tools they use. They can keep things going until something weird happens. I'm not sure what I think of this state of affairs. Not everyone can go deep, but I do feel the bar has been lowered too far in many cases. It's like millions of small components... NPM: because nobody can be bothered to figure out some problem and write 50 lines of code themself.
- itomato 3y agoIt’s also Gatekeeping disguised as Leadership in a Quadrant.
- deleted 3y ago[deleted]