Bad scientific code is bad, and bad programming code is bad. Every time you do a clever thing, you have to do three things: 1-Document your smart idea on your

Bad scientific code is bad, and bad programming code is bad. Every time you do a clever thing, you have to do three things: 1-Document your smart idea on your code. 2-Document your smart idea, preferably on drawing. 3-Document your smart idea, preferably on audio-video. People forget their smart ideas after 6 months or so. So basically if you have to debug the code later you have to spend at least the same amount of time you spent developing the smart idea in the first place each time you have to debug. In my opinion, smart ideas are great tough, if you follow the three principles above solving a bug becomes fast. Most people don't know about psychology so they believe that because they know it today, they will know it on six month time. Or worse, they fear that if they document their work they could be fired(this is the mentality of weak programmers that know they are weak, hopefully you wont work with these people, if you do quit as fast as possible).