Interesting post on The Reg about Neil Ford‘s talk about how to improve you code. The talk was aimed at Java developers but there’s good advice for everyone in there. Here’s what he said in a nutshell:
- Write tests before writing the code
- Use static analysis tools
- Practice “good citizenship” by paying attention to how well your objects interact with the outside world
- Avoid indulging in speculative software development
- Simplify essential complexity and kill accidental complexity
- Challenge programming conventions
- Embrace single level of abstraction principle
- Leverage existing platforms with languages targeted at specific problems and applications
- Learn every nuance of the languages you are using
- Change your perspective and consider “antiobjects“
Phew . . I actually typed those out on my notebook computer was reading them off my desktop. There’s some definite wisdom in there. I don’t know if any of your cringed because you were guilty of breaking some of those in the past. I know I have. Read the complete synopsis here.
Some good advice. I especially think writing test before you right code can help.
what is the meaning of “Write tests before writing the code” ?
sorry I’m a newbie