a generalist's guide to becoming useful
Specialization is a response to expensive knowledge.
If you were starting something in 1920 you needed a chemist, because chemistry lived inside a chemist. There was no other container for it. Same with the machinist, the accountant, the draftsman. Expertise was a person, and people are expensive and slow to duplicate, so you hired one of each and organized the company around the seams between them.
That constraint has mostly dissolved. The org chart has not noticed.
I can learn enough Python in a weekend to be dangerous. I can read the lectures. I can pull the paper, get a signaling pathway explained at whatever depth I ask for, download the CAD tool, and find someone online who already made the mistake I am about to make.
None of that makes me a chemist. That is not the claim. The claim is that the floor moved.
So what is actually scarce now?
Not knowing things. The ability to enter an unfamiliar problem and become useful inside it.
Those are different skills, and we keep treating them as the same one.
The useful version of this is narrower than "be curious about everything." Curiosity alone produces a person with a lot of hobbies.
What it actually takes, as best I can tell:
Learn what the problem requires, not what is interesting. Most of what is interesting is a detour with good branding.
Know enough to cross the interface. You do not need to be the biologist. You need to ask the biologist a question that does not waste her afternoon, and understand the answer well enough to build on it.
Build instead of collecting credentials. A credential describes a past. Nobody checks yours once you have shown them something that works.
Do not outsource understanding. It is easy now to hold an answer without holding the model that produced it. The gap stays invisible until something breaks, and then it is the only thing that matters.
Go where fields touch. Unclaimed problems sit at boundaries, because boundaries are nobody's job.
The failure mode is real and I have been in it. You end up knowing a little about a lot and being useful for none of it.
The difference between a generalist and a dilettante is whether you go deep when the problem demands depth. Breadth is how you find the problem. Depth is how you solve it. Both are required and they feel nothing alike.
I do not particularly want to be an expert in one thing.
I want to become the kind of person you can drop into an unfamiliar problem who eventually becomes useful in it. That is slower to build and harder to put on a résumé.
It also looks like the only durable version of the job.