They might overengineer things and make them more complicated than they need to be and it just slows down everyone else in the team.
Good engineering is really all about empathy and psychology.
They might overengineer things and make them more complicated than they need to be and it just slows down everyone else in the team.
Good engineering is really all about empathy and psychology.
Assuming people can keep fully in mind about 7-10 things at once, a person who can abstract can keep entire constructed systems in mind as one of those "things". A person who cannot abstract will only be able to hold that many immediately tangible source-code level concepts in mind, having a hard limit on the amount of complexity they can have in their projects before their mental organizational capabilities collapse, in the same way people throw up their hands and give up at math problems that are beyond them.
It's a necessary but not sufficient skill; as you mention, social tuning and business mindedness tend to round out effectiveness from just raw skill.
And if somebody's being an Architecture Astronaut in their "abstraction", then they're not abstracting what they're doing in context of making a workable system; they're just rote copy-pasting architectural memes that they think matches a pattern, just like the ineffective programmer.
And yes, I've dealt with real people on all ends of this spectrum, and there's stark common denominators in their respective successes and failures. That's not to say this article is any good, but the skill of abstraction is still paramount to software development.
By and large, the overwhelming majority of humans will bring you a cup or bottle of water if you ask them for “water”, rather than bringing you water in their cupped hands. Clearly all these humans can abstract.
If this conversation is to be meaningful in any way, it’d be helpful to use well defined, measurable properties (“can count to 10 without using their fingers”) rather than fuzzy things like “they can’t abstract” which is clearly plainly false.
Otherwise, these conversations merely devolve in “10x programmers are real and I only hire 10x programmers!” vs “anyone can be a 10x programmer given the right environment” and it just doesn’t go anywhere.
Regarding your last sentence, that's why I've been careful to call it a "skill", because it can be exercised, apprenticed, and gleaned. But for some people it just never gels.
This isn't the distinction between "10x programmer" and "regular programmer", it's the distinction of "has programmer skills" and "does not have programmer skills". And as much as the pointy-haired inclined hate it, software development heavily involves creativity and bespoke research, for which there's no reasonable objective skill measure besides simply doing the work.
Obviously this kind of complex logic is written by smart people who can keep long chains of logic in their minds but it doesn't mean that it's a good thing.
A less intelligent developer would probably have a hard time keeping long chains of logic in their mind and so would be more likely to keep their code simple and readable... Which often means better code.
But it depends what kind of problem is being solved. If it's a very complex problem like working with distributed systems then complexity cannot be avoided.
I disagree.
I'll give you a team of psychologists and I'll take a team of mathematicians and we can see who can build the better software.
Empathy and psychology are game changers only when they are built upon a broad and deep base of analytical thinking and problem solving.
If the project is like a game or something heavy on physics then mathematicians will have the upper hand.
I actually did a project for a professor of psychology at a university in the US. They didn't know much programming but I was impressed by the specifications document which they sent me because it didn't have any gaps or inconsistencies like most engineering specifications that I've seen before. The requirements were very clearly expressed.
Being able to share very complex ideas with a high degree of accuracy is is an extremely valuable skill.
Interesting. I've taught third year maths and psychology students and the maths students almost universally produce more sophisticated applications.
Of course it's hard to directly compare because the courses had different focuses.
> because it didn't have any gaps or inconsistencies
Mathematicians are very good at this - where they might fall down is eliciting complex requirements from others.
> like most engineering specifications
This is more of a deliberate choice on software projects than a lack of ability.
I remember the pre-agile days and specs were a lot better.
I'm not sure abstraction is the correct thing to look for.
There's an engineering joke about the difference between an engineer and a hobbyist being that anyone can build a thing for $20, but you need an engineer to build something that works just as well - or better - for 20c.
There's a lot of $20 code out there. 20c code is much rarer.
This isn't entirely related to IQ or the ability to hold a model of the entire codebase your mind, although both help a lot if someone has a talent for seeing the essence of complex relationships.
Some people get there after a few iterations, some people never get there at all, and a talented minority of developers tend to get there on the first try.