Developer's Toolkit

Blog archive

Good Code or Code That Works

At VSLive! Boston last week, I also sat in on a session by Jackie Goldstein on worst practices in coding. What he did was to display code examples and ask the audience what was wrong with them. The code worked, but was slow or inefficient or both, and Jackie led the audience on a journey of discovery of poor coding.

The interesting thing is that most of his examples depended on having an understanding on how underlying mechanisms worked – usually the .NET Framework. He also illustrated differences between the .NET Framework 1.1 and 2.0 that has an effect on coding practices when moving from one to the other. The common thread was that writing good code required knowledge of more than just the programming language (C# or VB.NET, in this case).

Joel Spolsky (www.joelonsoftware.com) has pointed out on multiple occasions that writing code requires a significant understanding of all layers of abstraction, from the programming language down to the hardware. He has lamented the fact that it is possible to graduate with a degree in computer science from an otherwise reasonable school by just using Java, and not understanding the concept of pointers (http://www.joelonsoftware.com/articles/ThePerilsofJavaSchools.html).

I like abstractions. They tend to simplify otherwise difficult concepts, and accelerate productivity for programmers. But I found myself nodding in agreement with both Jackie and Joel, in that knowing your programming language is not enough. I have never encountered the situation that Joel describes (http://www.joelonsoftware.com/articles/GuerrillaInterviewing3.html), in which programmers simply do not get pointers, but I can see it happening without a proper grounding in languages.

You might make the argument that such an understanding is nice to have, but no longer a necessity, because languages have moved beyond the need to directly manipulate the data in specific memory locations. There is a certain amount of truth to that. Millions of Java and VB programmers are a testament to the ability to write software effectively without pointers. And Jackie's .NET examples certainly did not require the use of pointers.

But the point that you need a deep understanding of everything the computer is doing still holds. Jackie's poor code did run, and was correct, but use managed memory poorly, or used an inappropriate .NET class or method. The fact remains that if you do not know what the underlying layers are doing, you will make the wrong programming decisions.

Posted by Peter Varhol on 10/29/2006 at 1:15 PM


comments powered by Disqus

Featured

  • VS Code Now Has Apple Silicon Builds for Native Mac Development

    Goodbye Rosetta, hello M1. Visual Studio Code has been updated with new builds that let it run natively on machines with Apple Silicon (M1), the company's own ARM64 chips.

  • Visual Studio 2019 for Mac v8.9 Ships with .NET 6 Preview 1 Support

    During its Ignite 2021 online event for IT pros and developers this week, Microsoft shipped Visual Studio 2019 for Mac v8.9, arriving with out-of-the-box support for .NET 6 Preview 1, which the company also released recently.

  • Analyst: TypeScript Now Firmly in Top 10 Echelon (Ruby, Not So Much)

    RedMonk analyst Stephen O'Grady believes TypeScript has achieved the rare feat of firmly ensconcing itself into the top 10 echelon of his ranking, now questioning how high it might go.

  • Black White Wave IMage

    Neural Regression Using PyTorch: Training

    The goal of a regression problem is to predict a single numeric value, for example, predicting the annual revenue of a new restaurant based on variables such as menu prices, number of tables, location and so on.

Upcoming Events