Experienced Devs

I don't buy this article in the same way others here seem to be doing. It sounds like the author is a little too... in love with himself? He's entrenched in a certain mindset where he's the "enthusiast developer" and others are lesser, while trying to empathize with his lessers as if to say "well, you know, your way of working is ok too!" It's the image of admonishing his old way of thinking, but he hasn't abandoned or renounced that way of thinking, he's just lamenting it. All of the arguments presented are colored by this personal bias.

I wish I could break down every part of the article that I take issue with, but just to illustrate my problem, here's some side-by-side quotes where I think undermines the author's own points:

Once I introduced the word “generation” to my thinking, it became easier to make sense of many contentious, unresolved issues in tech that flared up over the past decade by looking at them through the lens of intergenerational conflict.

If you allow for the possibility we’re undergoing a generational change, maybe this debate over “passion” is evidence that the assumption that most programmers will always be passionate about programming was mistaken and counter-productive.

If you were hoping to bridge the gap between two different kinds of developers, where you see yourself squarely on one side, then calling your relationship with the other side a "conflict" is not going to win over any friends.

When I saw the title, I thought "just another blog on 10x developer". I don't really know why I decided to read on, but I'm happy I did. Searls touches on many more while investigating the topic. The writer approaches the topic from a inter-generational point of view and also goes in to things like "passion" and "craftsmanship". I would even say, this is not about the 10x developer at all. This is about how as a young engineering discipline we are still trying to find better ways of doing things.

It’s an open secret that the industry has no idea how to teach people to program. Computer Science degrees famously don’t prepare programmers for the job of programming, which has always been left as an exercise to the student to figure out on their own time. If the industry is going to outlive us enthusiast programmers, will it adopt a sustainable approach to educating the next generation that doesn’t require people to teach themselves everything?

There's nothing new in this post. The idea that there's a generation of people who grew up programming because of the cheap computers they owned is exactly why the raspberry pi foundation was set up. So maybe there'll just be a generation that didn't grow up with programming and they'll be the exception.

But beyond that, this guy really needs an editor. Just to chop down half of the wall of text. He does have some good points though.

It’s an open secret that the industry has no idea how to teach people to program. Computer Science degrees famously don’t prepare programmers for the job of programming

This is depressingly true. I had an intern last year and he was utterly hopeless. So I went and looked at the syllabus for his course and it was no surprise at all. It didn't cover anything that would be relevant to the industry. It barely covered programming at all. I poked around at a few UK universities looking at their syllabuses and only found one that sounded better than useless.

What I would say is that a lot of people seem to choose to do a CS degree when they should choose a software engineering degree. About the only use a CS degree might be would be to get through data structure/algorithm sections of interviews.

For me, the main takeaway is 'programmers nowadays seem to have a life and we need to adapt to that'. Well, it's a good thing when people have something except for their work, I think. It feels like this is going to slow down the industry a bit, but I don't think it's a bad thing. Besides, we're getting better and better tools, the AI is on the rise, so maybe we will be able to be as productive as before while not investing so much time.

As a side note, I feel like I don't belong to the 'passionate' generation the author refers to, but even then I am curious enough to sometimes dig into the problem. I'd even go to a stretch to say that it's not a passion for computers and programming that discerns good programmers but curiosity, and it is more often can be seen in very different people and is less destructive as a personal trait, I believe.

I thought it was a good article. Well-written and reasonably well-argued. That said, I think that he missed a couple of things. I had a whole wall of text in preparation for my own blog post, but during the edit it really came down to a couple of things.

I think the industry's obsession with 10x programmers is really about the quest and desire for mastery. Mastery is something that exists in any field, so that means we can look to history for comparisons.

He argues that mastery is disappearing. My opinion is that what he's really seeing is the normal lifecycle of any industry that leads to less dependence on mastery.

Everything from furniture making to mechanical work has gone through the cycle. People doing what they need out of necessity, people getting good enough to offer their services on the market, masters arising from the truly dedicated and/or obsessed, shops run by masters to increase output by using the labour of apprentices and journeymen (and budding masters), and, finally, factories.

The difference between a master's shop and a factory is critically important. In a master's shop, everyone is gaining skill in the profession with mastery always possible to achieve for anyone with the right combination of desire and talent. In a factory, tasks are broken down into their component parts so that mere repetition and maybe some automation is enough to make extract masterful work from the process instead of depending on individual mastery.

Your local mechanic's shop, especially if it's a dealer shop, has more in common with a factory than a master's shop. A race team is where you're more likely to see a master's shop in operation.

I think that what we are seeing is the transition from masters' shops to factories.

There are still passionate people becoming master mechanics or furniture makers. I think the same is true of 10x programmers. But the tools some of those master programmers build will help everyone else do higher quality work and the processes they develop will eventually enable the extraction of masterful products from well-engineered processes executed by low-skilled people and, of course, automation in the form of AI.

It can't come soon enough. These 10x devs are toxic. They do things like sabotage fakerJs on Github.