The Difference Between Good and Great Coders
Jeff Atwood's recent Coding Horror essay, When Understanding Means Rewriting, argues that software developers spend most of their time trying to understand old code. In my experience, that's true -- and not just because as soon as I check in new code, it becomes old code I need to maintain.
Atwood's thesis is that developers should rewrite code rather than trying to understand it, because it's difficult to read source code and source code itself doesn't always reveal the vision or the domain rules behind the project.
At best, that logic is... well, confused.
FIT, a very interesting tool. I was thinking on using FIT under PHP for a web project and found this:
|Time scales and program performance will often determine if code is to be written in a maintainable way or not. Given 3 days to code a solution which must run in 15 minutes, there is absolutely no use in writing a bit of maintainable code that takes 3 weeks to complete and 3 hours to run!|
|Jack, the grumpy old programmer
Programmers must understand that there are 4 audiences of thier code:
1. the compiler
2. the end user
3. maintenace programmers
4. the hardware that the code will run on
Most programmers don't know how to write "intention-revealing" code.
|Cass, how often does that happen? I've definitely written code that way, but it's been rare.|
|Bart van Kuik
|When exploring a piece of code, I find it invaluable to use a debugger and step though the code. This can easily be done with even a commandline-based debugger such as perl -d or gdb.|