As an aside, TFA says: We’re talking about skills that span kernel-level programming, hardware quirks, low-level debugging, distributed systems, security, orchestration logic, even the capability to work with the UI/UX team... and the ability to explain all that without scaring interns. You can’t just hire for that. You have to grow it. Nurture it. Beg for it. Or in some cases, resurrect it. If you are that person, w…
You can't git clone a team
61–70 of 115 posts
Re: You can't git clone a team
#62Earlier quoted context omitted.
Before they were multiple people they were one person. A single person can in fact write a program for a computer.
Sure, some C code, some html, a table here, a colspan there, and you can have a website made by a single person... if we want a website to look like it was made on an 1980s computer by a single person.
Re: You can't git clone a team
#63As an aside, TFA says: We’re talking about skills that span kernel-level programming, hardware quirks, low-level debugging, distributed systems, security, orchestration logic, even the capability to work with the UI/UX team... and the ability to explain all that without scaring interns. You can’t just hire for that. You have to grow it. Nurture it. Beg for it. Or in some cases, resurrect it. If you are that person, w…
Hate to break it to the author, but there are plenty of people who can write a driver, bootloader, distributed systems, PAXOS, etc. but there's NO JOBS DOING THAT so they all work for making .
The author mentions their grand strategy is fishing for talent out of universities, which is probably smart. Pulling people out of generic web dev world to go write "container orchestration logic" (or some other niche) is going to be a hard sell - most of those people were burned before by straying too far from the lucrative web dev jobs. Nothing like going into job interviews and telling the hiring manager that your last job was some ultra-obscure niche.
Re: You can't git clone a team
#64Re: You can't git clone a team
#65Earlier quoted context omitted.
The question was "what is the best way to market yourself?" and your recommendation is to keep quiet and do less marketing. If that has worked for you, that's amazing! But it seems really counter-intuitive to me.
No he's saying if you are a generalist you shouldn't try to market yourself as that. Usually employers are looking for specialists that are perfectly moulded to the one exact task they need at that very moment. It's misguided of course, but that's what they think they want and if you say "I've done all sorts of things and I'm good at all of them" they'll hear "I don't have much experience with anything" and discount…
- resumes which claim generalist tend to be SEO’ed than real, or AI generated and they will say experience dozens of technologies most of which would be untrue, throw everything and see what sticks .
In most cases it just tells me what they have heard of rather than what they know especially if they are not very senior .
- It takes really hard effort to be beyond a superficial generalist, even when they know some of those skills and remember them during an interview it is not with a lot of depth they pursued only in passing interest not in a professional capacity (that is fine, but it is a lot work to make the distinction in evaluation on all relevant skills in a timed interview)
- It is harder or simply not viable for a specialist to interview a generalist , so you need to have few to hire more . If you don’t have any or they are not doing interviews you are not going get more .
- Being a generalist with depth of understanding means you are the type of person who needs to understand things properly before doing them . .You are lot of time learning things which are not required for get the task completed.
That means either you need are prepared to spend a lot of personal time and be perpetually stressed or be slow in completing something .
It is hard thing to master to let it go . I don’t think I have learned it yet
- Complexity and depth of technologies change a lot in short duration when they are corporate backed .
I learned Linux architecture or vim or git 20 years ago they haven’t changed much. You can be productive in any of these to stacks very quickly even if you didn’t use them for years .
Last I worked on android or swift is more than few years ago . I doubt I could even build a serious app without spending major time . To be productive to learning curve is steep and the prior knowledge is limited in usefulness.
Re: You can't git clone a team
#66Earlier quoted context omitted.
The question was "what is the best way to market yourself?" and your recommendation is to keep quiet and do less marketing. If that has worked for you, that's amazing! But it seems really counter-intuitive to me.
No he's saying if you are a generalist you shouldn't try to market yourself as that. Usually employers are looking for specialists that are perfectly moulded to the one exact task they need at that very moment. It's misguided of course, but that's what they think they want and if you say "I've done all sorts of things and I'm good at all of them" they'll hear "I don't have much experience with anything" and discount…
That's something hiring managers do find compelling.
Re: You can't git clone a team
#67Re: You can't git clone a team
#68Map knowledge doesn’t make you able to drive. Driving happens in real time - steering, obeying road rules, avoiding accidents.
In engineering, the real time part is when you use mental models you’ve painstakingly developed - how the hardware works so you can debug it, what syntax is valid in your programming languages, what APIs exist in your stack. But, those depend on knowledge - so mental models can be self-taught with AI as tutor in your own time. The LLMs supply the knowledge, you integrate it via study - or a side project.
An organization cannot clone itself a team, it’s true. They need engineers now, not in 6-12 months. But - a motivated individual can use AI to make themselves employable as a full stack engineer faster now than at any point in history.
How cool is that!
Re: You can't git clone a team
#69As an aside, TFA says: We’re talking about skills that span kernel-level programming, hardware quirks, low-level debugging, distributed systems, security, orchestration logic, even the capability to work with the UI/UX team... and the ability to explain all that without scaring interns. You can’t just hire for that. You have to grow it. Nurture it. Beg for it. Or in some cases, resurrect it. If you are that person, w…
Demonstrating that you are a stable hire who will fit well with the team is almost all that matters. You wouldn't be having an interview to begin with if you didn't technically qualify-ish. Even when speaking to technical interviewers, you will intimidate them. Actually selling yourself comes after your first 90 days of acclimation.
Re: You can't git clone a team
#70The value of knowledge is plummeting. It can, will, and should be subsumed by LLMs. Consider London’s black cabs. Drivers pass a gruelling exam to prove they know “everything” about one part of London. But, Google Maps puts that knowledge and more on every rideshare driver’s dashboard, for free, no advance study needed. Map knowledge doesn’t make you able to drive. Driving happens in real time - steering, obeying roa…
The lack of training material for LLMs is of course a lack of training material for people too. Some areas of software have a long history of relying almost entirely on an oral tradition to pass down knowledge. This has some advantages but it doesn’t scale and it makes it basically “dark knowledge” for LLMs or people without access to those that know it. If you want to get into an area like this, you often need to find a way to spend a lot of time with people that already know it.