I like the theme but indeed this article misses out on so many opportunities to make a good case. The innovators they are picturing are the "corporate innovators", which is different from the young kids disrupting markets altogether. The former are evolutionary, the latter really shine when they're revolutionary, which often needs a new company to take over instead of a big corp reiventing itself.<p>But both are great drivers of human progress. If we only developed by leaps and bounds, revolutions, we'd be hard pressed to avance at all. I like the concept of slow hunches. These are the ideas that you breed in your head over years, decades. They often need to meet other slow hunches other people have been breeding to really shine. This is a slow innovation that startup culture completely misses out on. It's the foundation of scientific research, but it's also very much directly (albeit slowly) applicable to business. I have a few slow hunches of my own, which have been evolving over the last 5 years (I'm 23). They have spawned little ideas and projects already, but the main branches keep pivoting and growing because they're far from concrete yet to be even market tested or MVP-built.<p>I feel my best innovation comes about from deliberate mixing of areas of knowledge. And it seems to me every week I have a new interest. I want to understand painting, poetry, design, writing, statistics, politics and a lot more. There's all this breadth I don't yet have, and I feel that's what makes good innovators, they're generalists, and criss-cross the DNA of different areas to create new mutations all the time. Most suck. In this sense, I'll be so much better at 50.<p>It's also why I don't see myself calling software development my career in 20 years. I feel like I want to build a career that ages well, and though surely I'll be a better developer at 40, many market dynamics will be playing against me in the field of tech. If it's even relevant anymore in 2030. Maybe robot code-monkeys will do, at least CRUD and interface design, much better.<p>I want to be a writer. I'm using article writing as a platform for all my expression and creativity. Want to understand something better? Write as best as I can about it, then edit, cut, edit. Like when it's said that you should always write all software as if it were open source (commenting, modularity, extensibility, docs), I write my thoughts as if they were published. I want to hone the craft, and eventually, as the decades pass, have a respected career for writing insightful articles where I wouldn't for writing old-man's code (Though I'm pretty sure I'll actually pay my bills with software still.)