If it was my home, I would hope the crew boss would tell them to go build a shed or something first.
They'll never be architects (they don't want to), but they'll earn enough to buy whatever students want and they'll always find some work no matter what is being built and where.
2. Then the worker tries it while the supervisor watches.
3. Feedback is given
4. Repeat 2-4 until satisfactory work is achieved.
Depending on the task this may be as little as 5 minutes for something simple or much longer for more complicated things.[1]
[1] I own a rough framing business
Where most people are failed by those around them, like parents and school's is pointing out when you leave education, you wont stop learning, and its always good to ask questions and plan ahead what you want to do with your life.
Arguably have a bucket list which will change as you age in order to have something to aim for, and dont get caught in the trap of settling for second best or end up being used by people who think might be your friends but only knew you because of what you could do for them on the cheap.
Now you might have called your summer job slave labour, I look at it as being paid to exercise as well as learning new skills and make new contacts.
On the subject of aimless excited programmers, there's lots of ways to look at programming before learning a language.
If one wants to earn a lot of money, then consider database related programming, everything is data, even spreadsheets can be considered flat files of sorts. And whilst you probably wouldnt use javascript to write a database app in, even though you could stuff data into a cookie and run it client side, there are better general purpose languages suited to database work, besides the obvious sql languages.
If chasing the money, consider looking at what's involved in high frequency trading where you'll be writing your own OS to maintain the super high speeds required for algorithmic trading. Co-locating data centres as close as possible to trading exchanges is just one part of the problem. [1]
IF you want to do apps for smart phones, again look at the languages that deliver the most for you, but also consider whether you should go with a popular language like dotnet or java thats portable across platforms, or whether you want to go with a niche language that might become less popular over time especially when considering there are thousands of languages that exist, with many having fallen by the wayside.
[1] https://www.ted.com/talks/kevin_slavin_how_algorithms_shape_...
Similarly in software, if you care only about programming and languages and whatnot and not the product - it's all you need with the right team/org. You won't be a product owner and you wont advance to "decision-making" levels in the company, but if you don't want to why would you need to.
The issue I have with is the statement of "make a career out of it". I don't think you can, at least not in the software industry, a lot of folks are perfectly competent developers but can't move forward and eventually get replaced by younger/cheaper developers because they are basically doing the same thing for the past 10 years.
I agree with having passions for something, but making a career out of it is a lot harder if you don't do the "extra".
I'd argue that they are replaced (if they are, because I'm not sure, there are not a lot of old folk because IT industry is pretty young, I already worked with a few 50+ mid devs and the pay is kinda reverse, because old folk already have homes and don't need to pay off huge mortgages) not because they didn't get promoted (mid dev -> product owner / domain expert) but because they stopped upgrading the skills relevant to their current job.
So in terms of the example presented by the author it would be developers that are no longer even hyped about languages/tools. And in our imaginary "tiling specialist" it would be a guy that didn't care that the current fad is some kind of funky pattern + new material of tiles and still wanted to lay old ceramic square tiles for his entire life.
I'm still not convinced that there is a scenario where you __have to__ care about "the domain" / "the problem being solved" / "the bigger picture" that much. You can, it will improve some aspects of your career, but you don't have to and it would degrade other aspects of said career (we all have about 16h max productive hours daily, and I'm being generous).
The difference is mostly of culture, and seems completely irrelevant to what you are trying to say.
But as many are also saying, being aimless is an opportunity to learn, explore and discover new possibilities. It's like how many of us are playing with ChatGPT at the moment. It's a journey of discovery that can lead you to realise the potential and create something truly amazing in later time. Would anyone say porting ChatGPT to many existing applications aimless?
I would. It's FOMO not innovation.
The problem is you can't tell which it'll be in advance.
I disagree.
I've rarely seen any programmers that are domain experts, most of those domain experts are actually hired in a consultancy role.
As they work through the projects programmers can become very familiar to a specific domain but in general that's not their job and they will be treated as such. They will be consulted on implementation but less likely, if at all, on strategy. Which is what I would expect from a domain expert i.e. a consultant.
The highest paid programmers move jobs most often the lowest paid don't that'll tell you what becoming a domain expert means for a programmer.
The other thing I find curious in your comment is the implication that strategy is usually set by domain experts who tend to be consultants. This very much runs counter to my experience, where consultants are brought in for specific jobs or problems where an outside perspective is needed, but generally those things are scope-boxed or time-boxed tangents to the business. The big strategy is generally set by leaders and influencers within the company via a mix of formal and informal venues. These individuals will have the most knowledge of the context specific to that business and how it competes in the marketplace. Consultants, by contrast, can develop a cross-cutting knowledge of industry, which can be a valuable data point well worth paying for, but a company who relies on consultants as the primary driver of strategy is rudderless and probably in decline.
I've been in several that had these types. I think the only companies that didn't were companies in industries that didn't need any specific domain experience example here are one that did:
* Oil and Gas (Flow metering)
* Network Timing and Sync testing
* Health and Care (Worked in Care and had several)
* Practice Management
Ones that didn't
* Data analysis
* Data warehousing
We need a lot of "bricklayers" that don't care about the problem but can be elastically moved around between projects to implement the ever increasing backlog of "solutions". Entire companies are created that solve that exact problem.
There are endless examples from other "industries". There are people that love painting, but never care who sees their work. They love the creative process. There are people that love carpentry, but hate doing utilitarian furniture that sells well. They love how zen manual labor can be and that the result is physical.
It's not "wrong-way-aroundness", it's just a different goal.