The concept is presented in a binary because of how spoken languages are presented. you are either "fluent" in a language or you arent. Knowing a few words vs conversational french is a discernable difference, while of course the process of learning is gradual, I believe it's partially referring to the confidence to use something actively.
"Learning to program" constitutes being able to interpret nearly any code in that syntax, and to produce your own working code without outside intervention that actually does something useful. This is all that is required for most business programming, so it's the goal. A question could be posed - Can you make a CRUD app in X without someone helping you, or at the very least pseudocode one?
People want to be in the yes camp to the above question
But then I agree that nowadays a few years education seems like a minimum.
What I found interesting was that part of his "learning journey" was to write a textbook about Rust even though he has never completed a major project with it. I wonder how many "how-to's" out there (not just for programming) are basically notes written as the author was learning that thing themselves. It's a pretty gutsy move and I don't don't think that I would do it
Somethings are not, but some are. Just like everything else, software work also ranges from easy to hard.
I've been writing C++ on every OS for the past 20 years and still don't consider myself a good programmer. I read every day to improve myself though but I still have a lot to learn.
That is how it works at most places for anyone starting out.
All the formal education is great for seniors and the 3% who do more than push boxes all day. For anything else, it ranges from useful to an active detriment. Given most devs will not be expected to be productive regardless of education and sit 5 years doing mostly the same work, that's a lot of time to train someone into the ideal cargoculter, which will keep them hireable in most of the market.
Vice versa, someone who sees inefficiencies, knows things can be better, etc.? Yeah, you get a few "look I did these amazing things and now my company loves me" stories, but the vast majority will struggle balancing their own desires and thoughts with company processes and political walls.
Except it's exactly how it works: Your soccer friend can probably job-hop for years before everyone realises they have no idea how to tell a computer what to do, and by that point, they might be ready for management.
Why are you so mad? You think hard work should be appreciated or something?
Whereas smacking a few bits of wood together (framing) gets you in the door as a carpenter. But there's a whole bunch more to learn if you're going to do fine woodworking. However, you can be productive form day one if you're willing to learn. That's the same as being a developer these days.
People will pay for low end skills because they are still a skill. You have a comp engineering degree. What are you working on in your job? Does the education fit the work, or on reflection do you have a little too much qualification for the work you're doing?
I wish I understood the "grain" in programming better. It's a lifelong search.
- copy/paste. You made one perfect table leg? Great, now make another 3. From scratch
- undo. Cut that plank a bit short? Start again
- incremental changes. Want to change the angle of that join? Start again
- imports. Don't want to make those fancy doohickies that go along the edge? You could try to buy some but it's not like there's an international database where you can pick and choose often for free
- debugging. Oh, your wardrobe just fell in a heap when you installed it? Hopefully you can salvage some of the materials and then figure out what went wrong
I'm not a very good programmer either, so I'm sure there's more
Carpentry is reasonably attractive in terms of actual work, so that if it payed as well as software development, many people would want to take it up. My point is that a larger portion of the population would have the necessary ability (and, I assume, inclination) to become a competent carpenter than a competent software developer.
I suspect a lot of entry-level programming jobs are like that, even if they don't intent to be apprenticeships.
Not quite a violin, but once upon a time I bought my first guitar and literally two weeks later was playing to a paying crowd of ~100 people. I certainly wasn't producing quality, and still can't, but I found something that a small number of people valued.
Some goes for software. You can create the most horrible monstrosity imaginable, but it can very much still deliver value. The audience who finds that value may be smaller than a master craftsman can attract, but at software scale a small audience is still huge.
I know a guy who works in the food industry. Not a CS nerd by any stretch, but he started dabbling in Python, and then got a huge raise because he could use Python to autogenerate PowerPoint decks that present a bunch of otherwise tedious-to-assemble information in a fraction of the time.
Could a professional developer do a better job? Almost certainly.
Did the company need to go find/hire one to achieve a huge efficiency gain? Nope.
Will the same guy be able to spearhead some massive greenfield app dev project? Not anytime soon.
The same thing is happening across industries. People with iPhones and Davinci Resolve are churning out social media content that previously would have required $100Ks of equipment and specialized training.
Will these same people direct the next Oscar winner? Probably not. But that’s beside the point.
There seems to be the perception that you can just "get into programming" in a few weeks and then you are a competent programmer creating anything of high quality and value. It's not the case for skilled carpenters, neurosurgeons or concert violin players. How come people seem to believe it's true for the art and craft of software engineering? I've been a computer nerd since high school, studied a Comp.Eng. degree for 5 years, went to grad school for another 4 and now I'm in an industry job for 3 years, and I consider myself only marginally competent at my craft. How come my soccer friend thinks he can watch a bunch of Javascript youtube clips and take an easy distance course at a university to score him a high paying job 2 months from now? That's not how it works, neither with carpentry nor with neurosurgery nor with concert violinists nor with software engineering.