How about "tall and fat" (square)? I'd consider myself fairly expert in C and C++, SQL, Windows programming, UNIX/Linux in general, Delphi and a few other technologies, in that quite a few people have paid me for writing important applications using them, teaching them and writing about them.
It seems pretty clear that the model is relative to "total surface area". What you call a "tall and fat" square may be "short and skinny" relative to someone else's bar, but now we're just talking about total level of skill, which isn't really relevant.
Short fat engineers are undervalued
131–140 of 269 posts
Re: Short fat engineers are undervalued
#132Earlier quoted context omitted.
Fatness and lack of stature was the original topic.
But the comment you replied to talked about attractiveness in general.
> I believe there is ample research showing height and attractiveness (one could reasonably consider weight to be one determining factor in attractiveness) do play a factor in career success, compensation, and selection for leadership.
Look, only about obesity and height (and mainly height). To which they replied:
> I think it goes more the other way around. …
Which makes no sense because no one ever mentioned hair, so that can’t be used as a direct counter-argument to a comment about research on height.
Are we gonna continue this? This is enough for me.
Re: Short fat engineers are undervalued
#133Earlier quoted context omitted.
This is also the strategy I tend to take. Strong, broad fundamentals so I can quickly pick up specifics on the job.
IMHO, I just don't buy this. Every piece of technology has its own set of quirks, pitfalls, and shortcuts. You can jump around from Rails to Spring to iOS to whatever and be a decent individual contributor. But to be a real Senior/Lead engineer that can be responsible for a project you've gotta have the in depth knowledge.
Re: Short fat engineers are undervalued
#134When you're a bigger product organization, more specialized approaches can work better since you're better suited to find the right trade-off of "speed" vs "future-proofness".
This can backfire too though - many specialists can get lost in the weeds and over-engineer solutions that can cripple a business with maintenance costs simply because they want to increase their depth.
I think this entire contextualization is kind of ridiculous though. If you were to categorize short fat vs tall skinny vs T, you might see something like:
fullstack eng vs ML researcher vs backend engineer w/ ETL experience
The fact is that fullstacks _are_ utility players. I don't know that they're really at liberty to "take the helm" if they're not well-versed in the technology that differentiates the company (or team).
Re: Short fat engineers are undervalued
#135Do "height on demand". Constant abstract and compress the knowledge so you can ramp up in any area as needed. Really, this is why programming languages are my "home base" of expertise. It's the study of formal ideas and their communication.
can you expand on this? i feel like i do this but not quite sure what you mean
Re: Short fat engineers are undervalued
#136Earlier quoted context omitted.
People whose value lies in coordination often need to dabble in multiple fields. Think of a technical artist in a game company.
I would count coordination here as a deep technical skill, which requires a depth of study and/or experience. You are selling your coordination skills. It's the stick of the T.
Re: Short fat engineers are undervalued
#137Earlier quoted context omitted.
This is also the strategy I tend to take. Strong, broad fundamentals so I can quickly pick up specifics on the job.
This still restricts you from getting many of the jobs that require narrow specialization. Specializing on the fly only works to a certain extent and only if you get the opportunity to do so in the first place.
Re: Short fat engineers are undervalued
#138The other thing is that you often just need problem solvers where it doesn’t even matter how wide their experience is. You just need someone who knows the basics and is adaptable.
Re: Short fat engineers are undervalued
#139Earlier quoted context omitted.
It depends, if your "master of many" list is all old technologies, or all new technologies.
How about the newest version of an old technology
Re: Short fat engineers are undervalued
#140I think there's some dynamics at play here that obscure the situation. First of all, there's a tendency for depth engineers to be more visible. But this is extreme; there's a handful of top names in StackOverflow for a tag like csharp or django, but that doesn't mean number 1000 in a given tag is an amateur at it, he's likely pretty good. Similarly, not everyone writes respected blogs, but the people who do tend to b…
I wonder what is the average time for an experienced engineer to transition into a different, but similar technology (like RoR -> Django) and be able to work productively in it.
It can’t be very long. Maybe 2 weeks? If you had a number, you could calculate the costs as part of a standard onboarding process. You’d just need to make sure that you hire someone who can demonstrate a willingness to learn the new thing.
This seems like it could be much cheaper than hiring an expert with the most years of experience in the particular combination of technologies in your stack, without compromising on quality.
And the perspective from someone with a breadth of knowledge is more likely to yield innovations that provide your company/project with a competitive advantage, compared to the expert that has been working on the same thing for many years.