> This is anti-intellectualism: "architecture is hard, so let the smart people at Google handle it."
No, it's not intellectualism, it's pragmatism.
It's important to recognize what you are good at and what others are better at than you are. Just because something is hard doesn't mean you should dedicate time to learn it or you'll be called an anti-intellectual.
I don't fix my car myself nor stitch my dog myself.
Same goes for computer science. It's a very, very wide field and you can't possibly expect everyone to know everything about it. I'm comfortable in my ability to write decent, well architected Javascript (and Haskell, and Scala and Java) but when it comes to creating a Javascript data binding framework that's efficient and follows good conventions, it's just not worth my time to learn how to do it properly versus using a framework written by experts who've spent years thinking about the topic.
The best developers I've ever worked with are the ones who know exactly when not to roll their own implementation.
No, it's not intellectualism, it's pragmatism.
It's important to recognize what you are good at and what others are better at than you are. Just because something is hard doesn't mean you should dedicate time to learn it or you'll be called an anti-intellectual.
I don't fix my car myself nor stitch my dog myself.
Same goes for computer science. It's a very, very wide field and you can't possibly expect everyone to know everything about it. I'm comfortable in my ability to write decent, well architected Javascript (and Haskell, and Scala and Java) but when it comes to creating a Javascript data binding framework that's efficient and follows good conventions, it's just not worth my time to learn how to do it properly versus using a framework written by experts who've spent years thinking about the topic.
The best developers I've ever worked with are the ones who know exactly when not to roll their own implementation.