Dirty Code
-
Argh. I'm working on a piece of software that was written by a junior colleague not long after he started. It was meant to kinda "break him in" but no-one reviewed his code. Reading through it is a nightmare. I can fully appreciate that it's not his fault that no-one reviewed his code (even though they were supposed to) but what I don't get is that he's left his code littered with useless comments, commented out code that he didn't need and wrapped them in regions marked "To Delete". It's doing my head in. Why didn't he just delete them? They have no purpose & we use source control for a reason! I'm going to use it as an opportunity to try and grow him into a better coder (I know I sucked when I started too) instead of just throwing my toys outta the cot. I might check up on some of his more recent contributions too. No real point to this post, just needed to get it off my chest.
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton
I gave up when I couldn't spell "egg". Justine AllenDave Sexton wrote:
I can fully appreciate that it's not his fault that no-one reviewed his code (even though they were supposed to)
Kudos for recognizing the (process) problem! Good will definitely come out of your experience. :thumbsup: /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com