Comments on: Writing code that you’re proud of

By: Sam

Sam — Mon, 19 May 2008 22:11:27 +0000

An inspirational post, good job

By: Weekly Links: Silverlight 2, ASP.NET MVC, C# 3.0, .NET 3.5 SP1… | Code-Inside Blog International

Mon, 19 May 2008 19:43:37 +0000

[...] Writing code that you’re proud of [...]

By: Wöchentliche Rundablage: Silverlight 2, ASP.NET MVC, C# 3.0, .NET 3.5 SP1… | Code-Inside Blog

Mon, 19 May 2008 19:42:02 +0000

[...] Writing code that you’re proud of [...]

By: Lars Corneliussen

Lars Corneliussen — Mon, 19 May 2008 07:45:04 +0000

When I post code on my blog I always had to refactor and document it at least a bit to be able to say: “I’m proud of it!”

I should always write code like this.

@Chris: I also don’t like theese arguments. But it is still an issue, and it requires some discipline to just not offer “bad code” to our “managers” – because collegues also do, and it works – sometimes, somehow.

By: Chris

Chris — Mon, 19 May 2008 03:05:35 +0000

Hmmm, the comments on managers not allowing enough time are annoying. Didn’t they allow enough time to get the crappy code done?

I’d be willing to bet that since the term “manager” is even being used as a description of the person driving the development effort, that they probably have no way of measuring or detecting good versus bad code in the first place.

So why not produce the good code and set the expectation for the manager for how long it takes to produce stuff?

By: mibus

mibus — Mon, 19 May 2008 02:50:12 +0000

I haven’t got much I’m proud of lately, mostly because I can’t spend countless hours perfecting things – reality gets in the way, and I need to move on and stay productive.

By: Fruity Loops

Fruity Loops — Mon, 19 May 2008 02:03:55 +0000

Jim – Code should be self commenting. This does not mean that methods shouldn’t have XML comments to describe the parameters and what the method does (API Documentation).

Methods should be short enough that they don’t require any additional comments to explain what they do.

I hate it when you get comments in code like:

// Set the object fields
Object.Field1 = Field1.Text
…

// Save the object
Object.Save();

if it is obvious to a developer what the code does, don’t add unnessecary comments.

By: Anis uddin Ahmad

Anis uddin Ahmad — Sun, 18 May 2008 17:47:20 +0000

It’s possible to not having enough time for clean up some code.
But, if there is a chance to a snippet to be edited or visited by other programmer, it’s a MUST to cleaning up, documenting and following standard coding style.
Documenting code for self reference is also an important point.
Thanks for this NICE post.

By: Dew Drop - May 17, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - May 17, 2008 | Alvin Ashcraft's Morning Dew — Sun, 18 May 2008 02:09:46 +0000

[...] Writing Code That You’re Proud Of (Jason Young) [...]

By: Dalton Filho

Dalton Filho — Sun, 18 May 2008 01:56:50 +0000

I always document code for an odd reason: I don’t trust my memory.