為什麼微軟製造差的程式設計師？

banq發表於2010-08-01
微軟程式設計師
Why Microsoft Makes Bad Programmers

原文：After the LIDNUG presentation, we stayed online to discuss unit testing experiences. A couple of things stayed with me from that talk. One: we’re (we developers) are obsessed with tooling and technology (you didn’t expect hard news here, right?). Our main focus should be about solving the business problem first. But, us geeks, we like to know more about the how, rather than the why.

The second is that Microsoft, by providing better and better VS experience, and a couple of great technologies, created less and less gifted programmers, and more professional debuggers. And I mean the people, not the tools.

Microsoft is not the only culprit (hey, it’s true around the software world). With our obsession for tools and technology (which MS provided), we needed better tools for getting ourselves out of more and more messes. So MS obliged, and gave us better debuggers, and for that we became proficient at excavating software problems.

If we chose the road less travelled, we would be working on eliminating bugs before they happen. This of course falls under the jurisdiction of better programming.

So the next time someone asks: why isn’t TDD catching on? You can blame Microsoft, or their tools, or the software industry in general. Tell’em I said so.

What can you do? Now, that’s your responsibility and what makes you a professional.

Think about your code before you write it. Make sure it works. Review it. Think about where the bugs can hide, and leave traps for them, to catch them when they rear their ugly head.

微軟提供越來越好的視覺化VS經驗，偉大的程式設計師越來越少，更多的是除錯程式設計師。

微軟之類廠商提供了很多強大工具，比如單元測試和BUG發現，這些會慣壞程式設計師，使他們容易編寫出很多BUG的程式，反正在後面有測試環節測試，有好的工具可以發現(其實沒有一個工具可以發現大的設計缺陷，方向性問題)。

好的方式是：在寫程式碼之前好好考慮你的程式碼，確保他們寫出來後能夠工作，檢查複習它，想想BUG會隱藏在那裡，哪裡會留下陷阱，在它們剛剛露頭時就扼殺在搖籃中。





[該貼被banq於2010-08-01 10:58修改過]

相關文章