Becoming a Better Developer
The bottom line is: developers don't need yet another reference manual. Instead—better, in addition to a reference—they need to understand how the old and the new features can be used to create more efficient, robust, reusable, and secure code. In the programming world, you can often achieve the same result with two or more equivalent techniques, but each one has its specific pros and cons, and often selecting the right approach can have far-reaching consequences on the end result. You need more than a mere reference book to gain the knowledge needed to detect these subtle differences.
A common misunderstanding in the programming community is that all you need to write great applications is familiarity with the .NET Framework and related technologies, such as Windows Forms and ASP.NET. Granted, you do need to learn these technologies to create real-world programs, but that familiarity isn't a surrogate for in-depth knowledge of low-level mechanisms that enable you to reduce memory and resource consumption, adopt effective optimization techniques, or leverage inheritance to write more concise and reusable code. I have seen too many applications that have a great user interface, yet perform very slowly and aren't structured in an orderly manner. Maintaining and evolving these applications are nightmares and cost much more in time and money than if they had been written with a solid understanding of the .NET Framework basics in mind.
0 comments:
Post a Comment