Valley Talent
rkoutnik.com
rkoutnik.com
On the other hand I don't think that founders will say "Oh, I won't pursue that technical passion project - I'll just build another Twitter!" The incentives to plunge into hard technical problems are not (at their core) based on money. That's just a plus. And lots of investor money means that those with the skills are more likely to found a company instead of letting a side project languish on a hard drive somewhere.
So those who can build amazing things will continue to do so. The current funding environment isn't stopping them. Having more CRUD apps than you can shake a RAM stick at is a small price to pay for enabling the next Stripe or Heroku.
For example, would bitcoin be a 'crud app'? Is mint a 'crud app'? Is pinterest a 'crud app'? Facebook or Instagram?
Mint: (assuming the financial tracker) No, ask anyone who's worked with bank software before - it ain't pretty.
Pinterest/FB/Instagram: Possibly. At the start? Absolutely. What makes those companies valuable is their network effect - everyone you know is already there. Supporting users at that scale takes a lot more than just reading up on the latest APIs. FB invented a (sorta) new language to tackle their scaling problems.
Hm. It sounds like you don't know what CRUD means
http://en.wikipedia.org/wiki/Create,_read,_update_and_delete
bitcoin doesn't belong on that list, as the primary thing about bitcoin is the database, not the interface.
You could certainly call pinterest, facebook, mint and instagram CRUD apps at their core, though obviously, the CRUD nature is not what makes them special or interesting; but yes, the core facebook app Creates, Reads, Updates (though maybe doesn't delete) from a database; same with twitter and facebook and mint (though, of course, the technically hard part of facebook is getting the equivalent of a tremendously massive join to scale, not writing an app to display the data. Not figuring that problem out, I'm given to understand, is what killed friendster)
Of course, all of those apps, well, it's more about marketing than about the technical stuff. You have to come up with something people want, and coming up with something people want is a very different thing from solving technical problems. Now, of course, if it doesn't work nobody is gonna want it, so you have to have a minimum level of technical competency for your scale; friendster showed that.
But the truth of the matter is that 95% of what you build is stuff that nobody is going to want. And there is no way of knowing ahead of time if you are working on that 95% or on the 5%; So most people build version one cheap. They cut corners. They take on technical debt. Because they only need to build it to work long enough to make it obvious that it's something people want. After it is shown that this is a thing people might actually like, you can dump a bunch of money into rewriting it properly and/or propping up the crap you have.
I mean... look at how much effort facebook has put into... PHP.
The danger here, of course, is demonstrated by friendster. If you have enough interest to make your cheap demo fall over, you need to move fast in propping the goddamn thing up and then hiring some real engineers to build something that can actually scale.
Additionally, something I haven't seen mentioned elsewhere, but the API availability is unfathomably vast now. I was checking out Google's developer console and there are over 100 incredibly robust APIs just a GET request away. In the real world, you can order drone images, turn off your lights at home, monitor your health levels all from url endpoints. These computational implementations are encouraging talent to work on projects that are beyond the scope of a laptop and a dorm room.
I for one am optimistic in Valley Talent, and can't wait for the next few years.
Here are a few examples:
1) rent out cars that people leave at airport parking (i.e. flightcar, etc.) 2) group people together for a buying discount (i.e. groupon, etc.) 3) a middleman service that uses middlemen (i.e. magic, etc.)
Most of the hot new startups aren't delivering on a basic need (like food or shelter), but seem to be like one-off computer hacks. And that's not a bad thing. These are smart people bringing out clever solutions that deserve talented valley employees.
The returns that these startups will generate are much more attractive for short-term investors and will have clear advantages over the long-term mentality needed for building a hard new technology.
If I work on a project that is complex, I am a good engineer because I solve hard problems. If I work on a simple problem, I'm just another code monkey.
I think a good engineer can take a complex problem and frame it in a simple light. I think a less great engineer can take the same complex problem and come up with a complex solution. From many perspectives, the second engineer is the one innovating.
Note: I'm talking about complexity in a business sense. There are many problems that are mathematically difficult and don't fall under this umbrella.
For complex software, take a look at some of the database companies. For flight hardware + software, AirWare is doing some cutting edge work.
Even the "simple" gets complex at scale (ex. Facebook).
This is a common refrain? I'm an experienced engineer about as far outside Silicon Valley as you can get in the U.S., and in more than twenty years I have never heard this sentiment expressed. Perhaps the author needs to make some new acquaintances.
Because good coders borrow, but great coders steal.