Most buzz revolves around a reasonably good idea. It's rare that something hyped doesn't include a good idea that'd be worth knowing. At the same time, there's the tendency to want silver bullets.
Ultimately there's no substitute for
trusting your own common sense as to the worth of said buzz. It's important to recognize that you have expertise as well, and your own opinion is not worthless. Some "experts" are just opinionated people who are louder.
humility in the face of the knowledge that lots of people who're doing this are smarter than you are and if your common sense tells you they're full of it you may very well be missing the point.
Of course it doesn't help that these two statements are mutually contradictory. Now if we could only find the right buzzword to tell us which to apply in any given situation...
I think it really comes down to experience. Premature optimization, in my opinion, is pretty logical. Why optimize everything before the code flow is largely complete? Sometimes you are surprised by what needs to be optimized and what doesn't. I've made this premature optimization mistake before.
When you see a buzzword, research it a little, find out what it's about and form your own opinion. If your opinion is different than everyone else's, then maybe do a post and find out why your opinion is different.
For example, I still disagree with Test Driven Development, unless I am contracting out my coding, then I'll write the tests that need to be passed. I figured I was missing something since my opinion was different. But, asking other developers, who I have a lot of respect for, and non-developers too, almost all had the same opinion I did. I can certainly think of numerous cases where TDD would be valuable and applicable, but at this time it's not a buzzword for me.
The important thing to remember is that there is no silver bullet. Whenever there's a new technology, a lot of people will try them on a lot of different problems, and after a while a (loose) consensus emerges regarding the fit of the technology to different domains. Whenever somebody is using one technology for everything, you can be sure that they are either doing only slight variations on the same thing or using a badly fitting technology most of the time.
发布评论
评论（5）
如果/当有人对你说了这些笼统的陈述之一时，总是问他们“为什么？”。
如果答案有意义并且适用于您正在做的事情，那么它可能值得关注。
如果答案是“嗯”或“因为乔尔这么说”，请随意忽略它。 :-)
If/when someone says one of those blanket statements to you always ask them "Why?".
If the answer makes sense and applies to what you were doing then it's probably worth heeding.
If the answer is "Ummm" or "Because Joel said so" feel free to ignore it. :-)
大多数议论都围绕着一个相当好的想法。 炒作的东西很少不包含值得了解的好主意。 与此同时，人们倾向于寻求灵丹妙药。
没有什么可以替代
当然，这两种说法相互矛盾也于事无补。 现在，如果我们能找到正确的流行语来告诉我们在任何特定情况下应用哪个......
Most buzz revolves around a reasonably good idea. It's rare that something hyped doesn't include a good idea that'd be worth knowing. At the same time, there's the tendency to want silver bullets.
Ultimately there's no substitute for
Of course it doesn't help that these two statements are mutually contradictory. Now if we could only find the right buzzword to tell us which to apply in any given situation...
我认为这真的取决于经验。 在我看来，过早的优化是非常合乎逻辑的。 为什么要在代码流程基本完成之前优化所有内容？ 有时您会对哪些内容需要优化、哪些内容不需要优化感到惊讶。 我以前就犯过这个过早的优化错误。
当你看到一个流行语时，稍微研究一下，找出它的含义并形成你自己的观点。 如果您的观点与其他人不同，那么也许可以发帖并找出您的观点不同的原因。
例如，我仍然不同意测试驱动开发，除非我将我的编码外包，然后我将编写需要通过的测试。 我想我错过了一些东西，因为我的观点不同。 但是，询问其他我非常尊重的开发人员以及非开发人员时，几乎所有人都有与我相同的观点。 我当然可以想到 TDD 有价值且适用的许多案例，但目前它对我来说还不是一个流行词。
I think it really comes down to experience. Premature optimization, in my opinion, is pretty logical. Why optimize everything before the code flow is largely complete? Sometimes you are surprised by what needs to be optimized and what doesn't. I've made this premature optimization mistake before.
When you see a buzzword, research it a little, find out what it's about and form your own opinion. If your opinion is different than everyone else's, then maybe do a post and find out why your opinion is different.
For example, I still disagree with Test Driven Development, unless I am contracting out my coding, then I'll write the tests that need to be passed. I figured I was missing something since my opinion was different. But, asking other developers, who I have a lot of respect for, and non-developers too, almost all had the same opinion I did. I can certainly think of numerous cases where TDD would be valuable and applicable, but at this time it's not a buzzword for me.
我想只有一种方法可以解决这个问题，而且你已经命名了它——保持良好的嗡嗡声。
I guess there is only one way to figure out this and you already named it - good buzz stays.
重要的是要记住，没有灵丹妙药。 每当出现一项新技术时，很多人都会尝试解决许多不同的问题，一段时间后就会就该技术对不同领域的适用性达成（松散的）共识。 每当有人在所有事情上使用一种技术时，您可以确定他们要么只是对同一件事做了细微的变化，要么大多数时候使用的是不合适的技术。
The important thing to remember is that there is no silver bullet. Whenever there's a new technology, a lot of people will try them on a lot of different problems, and after a while a (loose) consensus emerges regarding the fit of the technology to different domains. Whenever somebody is using one technology for everything, you can be sure that they are either doing only slight variations on the same thing or using a badly fitting technology most of the time.