|
|
|
|
|
by 6ren
4614 days ago
|
|
Yes, coming up with the problem is often the hard bit. But it happens the other way too, in that many young inventors tackle problems because "they didn't realize they were 'impossible'". More knowledgeable folk can do this too, but it requires a certain... disrespect for authority. Like Einstein's flexibility with time and space (though he was young then; he didn't make breakthroughs in later life, possibly because he himself became an authority). Fortune favours the delusional. |
|
There are a couple of other factors to consider. First, there are problems that can be solved with new tech that couldn't be solved with old tech. The web opened up a huge front of new solutions over the past 10-20 years. Mobile is opening up another wave of solutions.
And finally, consider the "aspirin or vitamin" question. Vitamins are tempting, but aspirin sells better. Me, I'm working in more or less the monitoring space for configuration management. My key competition isn't other monitoring tools, it's the DevOps movement and automation tools like Chef and Puppet. When people have enterprise configuration management suck, those are the recommended solutions. But they're vitamins being sold as aspirin. Simply getting to where there's organizational buy-in to go to DevOps or to automate what was once manual is a whole fresh sort of pain. My competitive advantage is a near-painless dose of aspirin - immediate relief without having to change the whole model.
Ain't no college kid coming up with that.