Earlier quoted context omitted.
This might be good advice if you're building cookie cutter systems for clients that have high turnover of contractors, but for startups I think it's horrible. I'd take one person that really groks devops and database internals well enough to make informed choices over a million one-size-fits-all SQL/Mongo+MVC devs. Any day of the week.
but for startups I think it's horrible. Why? Wouldn't it make more sense for startups to color within the lines, in terms of getting features to market faster? I'd take one person that really groks devops and database internals well enough to make informed choices Funded or not, a startup has the responsibility to turn every dollar into a feature that creates revenue, not architecture.
I strongly disagree with the notion that any practicing or aspiring creator should refuse to learn about and consider the full range of tools at their disposal, simply because there's a popular default choice.
Specialized tools provide a form of leverage to those who understand and employ them wisely. Every problem I have ever come across that is sufficiently difficult and interesting to warrant forming a startup requires deeper insight on a technical level than "just ignore everything else and use X".
Can you imagine if the founders of Google took this kind of advice?