3 ms·
You may not need to be a chef to know someone's cooking sucks, but you sure as hell better be a chef if you're going to lecture to a bunch of chefs about cookin
by jpwagner 17y ago
You may not need to be a chef to know someone's cooking sucks, but you sure as hell better be a chef if you're going to lecture to a bunch of chefs about cooking.
- sophacles 17y agoI call bs. Sure, the chef needs to go listen to other chefs about cooking, technique, ingredients, whatever. But I bet that same chef can go to non-chefs about things like book keeping, marketing, what customers want, etc. Further, plenty of restaurant owners, restaurant workers, restaurant enthusiasts and/or people who eat can totally get up in front of a chef and say: hey stop making crappy food no one wants it. Or even "this food that you are all making used to be trendy and clever, but now that everyone is doing it, its just sucky and boring. Here is something cool instead". Bringing the analogy back around, it is pretty arrogant for developers to think that the only person that can speak about the end product is another developer. Sure, I wouldn't listen to a marketer about what framework to use, but I sure would when it comes to declaring aggregators old-hat and sucky.
- sophacles 17y agoCan someone explain to me why this comment was modded to -1?