As I organize the history of programming, I think the OP's analogy is right. I remember that in the early days, code that just worked as long as it was implemented was called 'cowboy coding.' These days in the US, it's not considered a good coding practice, but there were many programmers who missed it.During that time, many star programmers emerged. The legends we know today. When cowboy coding started causing problems with collaboration, rules had to be created, and people wrote those rules. Whether it was creating something from 0 to 1 or various other areas, stars seemed to emerge everywhere.
But as time passed and businesses became more sophisticated, the early implementations piled up layer after layer, and human cognitive limits started to show. It seems like it's becoming increasingly difficult for extremely talented star programmers to emerge in specific fields.
In reality, everything—networking, databases, browsers—has become so much harder than in the old days. When I first learned computers, it was opening Notepad, creating an HTML file, and loading it. These days, people start with Python.
So as an industry becomes more advanced, it seems harder for a star programmer who can control everything alone to emerge.
Star programmers are appearing in the AI field right now because it's a new, unexplored territory. They implemented a lot early on and started creating things from 0 to 1, which excites people. But no matter how much I think about it, I don't have the ability to create from 0 to 1. I can't even take something from 1 to 100. I can only combine things at the 20–30 level to make a single product. That's why I think it's hard for me to become a star programmer.
I also want to become a cowboy somewhere, so I've been wandering through an empty pasture, but I don't know where that place is
7/3/2026
at
12:43:08 PM
OP here. Glad you enjoyed this.It’s an interesting point - I guess I implicitly acknowledged internal frontiers like the ones appearing with AI, but more explicitly acknowledging that as you have is valuable I think.
I do think there are frontiers (mostly in startups, I believe I am working with one now). They do have their tradeoffs. They can be exciting, but also frightening, uncertain, and professionally deadly (personally deadly if you tie your life savings up in them).
I do think frontiers exist, can be found, and can be created. But that’s a difficult and risky proposition!
by rhunterharris
7/3/2026
at
1:02:48 PM
You're really good at coming up with easy-to-understand analogies. I enjoyed reading it. I was able to grasp your points right away. Personally, I think you have a talent for teaching.
by jdw64
7/3/2026
at
10:51:46 AM
> In reality, everything—networking, databases, browsers—has become so much harder than in the old days. When I first learned computers, it was opening Notepad, creating an HTML file, and loading it. These days, people start with Python.That’s because all the low hanging fruits and most of the high ones have been taken. The only thing left for most people are people’s problems, not technical ones.
Complex solutions that are easy to use but hard to understand are easily available (and useful). While the simpler ones require some elbow grease and the will to learn every knob.
In the old day, you mostly have the bios and some memory buffer to do graphics, now you have complete solutions like SDL. But that is supported by a big tower of abstractions.
by skydhash
7/3/2026
at
11:29:32 AM
As things become more advanced and industrialized, I'm not sure when I'll be able to find a blue ocean
by jdw64
7/3/2026
at
12:19:30 PM
Currently, I’m trying to learn more about the technology I use (Computer organization, OS, codebase of various software), some advanced topics that I really like (distributed systems, compilers, control of dynamic systems), and refreshing my knowledge from college (math, physics and electronics).The primary reason is that I spent a lot of time on top of the tower, that I never really learned what goes into it. It’s quite uplifting to have another perspective on a practice you’ve been doing dogmatically. And the latest thing that I was able to do thanks to that was diving into Qemu’s code to learn how they implemented AVR emulation and understand everything easily. This week, I’m exploring OpenBSD’s PCI implementation.
by skydhash
7/3/2026
at
1:03:56 PM
What's your secret to keeping that passion alive? I guess I'll have to find my own way too
by jdw64
7/3/2026
at
1:56:33 PM
Mostly constraints. You put yourself in a situation where you lack something and then you try to solve that problem. The whole “receiving fish” and “having to learn how to fish”. Also putting yourself in a room where you’re the ignorant one (even if the room is metaphorical). Convenience is a nice road to complacency, even if it really helps with time management. The trick is to make it gradual, not immediately jump in the deep end.
by skydhash