5 ms·

>The ones I am thinking about are people who pick up new things absurdly quickly; pick up on patterns very easily; have general experience in enough domains to

by carlmr 8y ago

>The ones I am thinking about are people who pick up new things absurdly quickly; pick up on patterns very easily; have general experience in enough domains to make quick connections; etc. That's my experience as well. Generalists are often the most productive people. A good generalist can often grasp the whole system faster than a niche programming language specialist. And you usually don't need those niche programming skills for 99.9% of problems. Humans are capable of much more than the small niches companies put us in. Generalists are generally (hrhr) ignored by HR though. They don't fit any mold so have a harder time getting hired. The most successful ones I know usually freelance.

Steve44 8y ago
When I stopped programming I moved more into technical testing and that morphed into 'project guru' on some quite large projects. I could understand from low level network protocols up to the big fluffy clouds, I could also pick things up very quickly as I understood all the building blocks if not the latest buzz words. From my first exposure to SQL I was optimising databases better than the incumbent dba within a couple of months, and that wasn't even my job. I loved the work, but the downside was no one ever advertised for that role despite it was very important to the project.
- geezerjay 8y ago
  > From my first exposure to SQL I was optimising databases better than the incumbent dba within a couple of months, and that wasn't even my job. That doesn't mean much, as in the not so distant past (and in some small shops even today) the resident database expert is far from experienced or even technically apt. In fact, it was and still is a job that was assigned internally to someone who happened to have anything to do with the project, who was thus forced to accumulate yet another responsibility.
seanmcdirmid 8y ago
As a specialist who is currently looking for a job, HR generally only seeks generalists. Almost all interview loops that have been standardized seriously prefer generalists. The mold doesn’t fit anyone and are just generic programming/system design questions that do not evaluate specialist skills and experience at all. PL specialists are also pretty good generalists. I mean, what hasn’t Jeff Dean done and do people even remember that he has a PL PhD anymore?
- throwawaymath 8y ago
  I think whether or not you're a capable generalist is independent of whether or not you have a PL PhD. Jeff Dean is a generalist because he invested significant time in working across a wide variety of problems, not because of his PhD. If anything, a PhD makes you a specialist by default. You need to do extra work to gain diverse experience across the stack. This is to say that I don't think you should use Jeff Dean as an argument for hiring PL specialists in generalist roles.
  - seanmcdirmid 8y ago
    Google does this though. Whenever is PL PhDs get together, someone invariably talks about how they are doing ads for google these days. It’s actually so common that it has become a meme.
- barrkel 8y ago
  I think experience in compiler and language design is a strong signal of meta-thinking about problems and high-level abstraction. Compiler implementation requires a kind of rigorous thinking and separation of concerns to keep straight, because you're writing code that writes code, and need to model execution explicitly. Also, all edge cases and interacting features need to be considered in both disciplines - you generally can't get away with smoke and mirror demos or handwaving. I don't think it adds up to generalist though. Generalists need knowledge in a lot of different things (though one man's generalist is another man's "full stack" web app developer), or else they're just smart people who don't know much yet.
  - romeisendcoming 8y ago
    Very insightful: 'They are smart people who don't know much yet.' One thing to consider is that understanding only how a compiler organizes things or how a good assembly programmer understands the world is not conducive to anything but optimization. The true generalist, while able to perform binary analysis and understand executable file organization, is not tied to that. They are pattern people. Learn the pattern, see the relation.
  - 8y ago
jpatokal 8y ago
I hire at a FAANG for two roles where we specifically target generalists: Solutions Architect (design solutions for complex real-world problems) and Technical Solutions Engineer (last line of support for really gnarly cases). Both need people who can cover a lot of ground, and it's hard to be good at either if you don't have significant practical experience and can't traverse the stack from source code to tcpdumps if needed. That said, being just a generalist is not going to cut the mustard, you're going to need depth in at least one field, plus you need to be able to talk to customers too. Mandatory plug: if you think you'd fit the bill and are keen to explore, find me through my HN profile. Bonus points for being anywhere in APAC, although I can refer you elsewhere too.
- cc81 8y ago
  Do you (or anyone else) know of any more resources of what a Solutions Architect is doing day to day at that company? What artifacts are they producing, how much hands on are they, do they belong to teams etc? I have the title right now but it is a new one in the company and it is up to me to navigate really what it means for us. EDIT: And are there any books or other resources you or you see Solution Architects recommend?
- thepredestrian 8y ago
  Do you happen to hire co-ops for these type of roles? I have recently had interest in consulting
nickjj 8y ago
> Generalists are generally (hrhr) ignored by HR though. They don't fit any mold so have a harder time getting hired. The most successful ones I know usually freelance. I think as you gain experience you naturally become more of a generalist over time. I've been a freelance developer for 20ish years and I would consider myself a generalist at this point, but it took many many years to get to this point. Everything from learning the Linux basics, how networking works, various programming languages and web frameworks, database modeling, dealing with the ops side of things, and the list goes on and on. Basically I spent a majority of my life learning all of these things in a lot of detail, but most of it ended up being on a need to know basis. Basically once you become somewhat proficient in something, you naturally start learning about some other related topic. Even today I still think I know almost nothing in the grand scheme of things.
arandr0x 8y ago
I don't know if I'd call that talented though? I mean, I also got the right number in the IQ and motivation lottery, but not only is that like 80% biochemistry, it's not a differentiator in the sense of doing qualitatively different things. I do all the same things as everybody else, just faster and without guidance. But I work with people who are extreme specialists. (I don't mean in React. I mean in computer vision or non linear optimization, that kind of thing.) There is an entire class of problems that only those people can address properly; I could learn to but it would take me a couple years and the output from these years would be significantly below state of the art. In general they're skilled, not just talented, but they also work with mental models that require some amount of essential ability to grasp and that plenty of people will never be able to fully understand. Although, the most successful developers I know (of) are both generalists and extremely talented. Their special talent is "people understanding"!

by carlmr 8y ago

Steve44 8y ago

When I stopped programming I moved more into technical testing and that morphed into 'project guru' on some quite large projects. I could understand from low level network protocols up to the big fluffy clouds, I could also pick things up very quickly as I understood all the building blocks if not the latest buzz words. From my first exposure to SQL I was optimising databases better than the incumbent dba within a couple of months, and that wasn't even my job. I loved the work, but the downside was no one ever advertised for that role despite it was very important to the project.

geezerjay 8y ago
> From my first exposure to SQL I was optimising databases better than the incumbent dba within a couple of months, and that wasn't even my job. That doesn't mean much, as in the not so distant past (and in some small shops even today) the resident database expert is far from experienced or even technically apt. In fact, it was and still is a job that was assigned internally to someone who happened to have anything to do with the project, who was thus forced to accumulate yet another responsibility.

seanmcdirmid 8y ago

As a specialist who is currently looking for a job, HR generally only seeks generalists. Almost all interview loops that have been standardized seriously prefer generalists. The mold doesn’t fit anyone and are just generic programming/system design questions that do not evaluate specialist skills and experience at all. PL specialists are also pretty good generalists. I mean, what hasn’t Jeff Dean done and do people even remember that he has a PL PhD anymore?

throwawaymath 8y ago
I think whether or not you're a capable generalist is independent of whether or not you have a PL PhD. Jeff Dean is a generalist because he invested significant time in working across a wide variety of problems, not because of his PhD. If anything, a PhD makes you a specialist by default. You need to do extra work to gain diverse experience across the stack. This is to say that I don't think you should use Jeff Dean as an argument for hiring PL specialists in generalist roles.
- seanmcdirmid 8y ago
  Google does this though. Whenever is PL PhDs get together, someone invariably talks about how they are doing ads for google these days. It’s actually so common that it has become a meme.
barrkel 8y ago
I think experience in compiler and language design is a strong signal of meta-thinking about problems and high-level abstraction. Compiler implementation requires a kind of rigorous thinking and separation of concerns to keep straight, because you're writing code that writes code, and need to model execution explicitly. Also, all edge cases and interacting features need to be considered in both disciplines - you generally can't get away with smoke and mirror demos or handwaving. I don't think it adds up to generalist though. Generalists need knowledge in a lot of different things (though one man's generalist is another man's "full stack" web app developer), or else they're just smart people who don't know much yet.
- romeisendcoming 8y ago
  Very insightful: 'They are smart people who don't know much yet.' One thing to consider is that understanding only how a compiler organizes things or how a good assembly programmer understands the world is not conducive to anything but optimization. The true generalist, while able to perform binary analysis and understand executable file organization, is not tied to that. They are pattern people. Learn the pattern, see the relation.
- 8y ago

jpatokal 8y ago

I hire at a FAANG for two roles where we specifically target generalists: Solutions Architect (design solutions for complex real-world problems) and Technical Solutions Engineer (last line of support for really gnarly cases). Both need people who can cover a lot of ground, and it's hard to be good at either if you don't have significant practical experience and can't traverse the stack from source code to tcpdumps if needed. That said, being just a generalist is not going to cut the mustard, you're going to need depth in at least one field, plus you need to be able to talk to customers too. Mandatory plug: if you think you'd fit the bill and are keen to explore, find me through my HN profile. Bonus points for being anywhere in APAC, although I can refer you elsewhere too.

cc81 8y ago
Do you (or anyone else) know of any more resources of what a Solutions Architect is doing day to day at that company? What artifacts are they producing, how much hands on are they, do they belong to teams etc? I have the title right now but it is a new one in the company and it is up to me to navigate really what it means for us. EDIT: And are there any books or other resources you or you see Solution Architects recommend?
thepredestrian 8y ago
Do you happen to hire co-ops for these type of roles? I have recently had interest in consulting

nickjj 8y ago

> Generalists are generally (hrhr) ignored by HR though. They don't fit any mold so have a harder time getting hired. The most successful ones I know usually freelance. I think as you gain experience you naturally become more of a generalist over time. I've been a freelance developer for 20ish years and I would consider myself a generalist at this point, but it took many many years to get to this point. Everything from learning the Linux basics, how networking works, various programming languages and web frameworks, database modeling, dealing with the ops side of things, and the list goes on and on. Basically I spent a majority of my life learning all of these things in a lot of detail, but most of it ended up being on a need to know basis. Basically once you become somewhat proficient in something, you naturally start learning about some other related topic. Even today I still think I know almost nothing in the grand scheme of things.

arandr0x 8y ago

I don't know if I'd call that talented though? I mean, I also got the right number in the IQ and motivation lottery, but not only is that like 80% biochemistry, it's not a differentiator in the sense of doing qualitatively different things. I do all the same things as everybody else, just faster and without guidance. But I work with people who are extreme specialists. (I don't mean in React. I mean in computer vision or non linear optimization, that kind of thing.) There is an entire class of problems that only those people can address properly; I could learn to but it would take me a couple years and the output from these years would be significantly below state of the art. In general they're skilled, not just talented, but they also work with mental models that require some amount of essential ability to grasp and that plenty of people will never be able to fully understand. Although, the most successful developers I know (of) are both generalists and extremely talented. Their special talent is "people understanding"!