Re:Why bad scientific code beats code following "best practi...
by collyw on Monday May 12, 2014 @11:10AM
(#7733138)
Actually that sounds a bit like the bioinformaticians in the last pace I worked. They would write a script that took 3 hours to run, launch it, and play on facebook for until it complete. (They could have learned to use a debugger / IDE /library that would have improved their efficiency - I don't think any of them used "advanced tools" like those). As the database programmer I always had too much work to slack off like that.
Another point, is that when I have to make a bigger architectural decision, then I don't jump straight in and code. I usually come up with two or three possible solutions in my head (or on a piece of paper). I will stare at the wall for most of the afternoon, go for walks, as I play the ideas off against each other. After a day or two I usually have an idea of which solution is better, and why.
Another point, is that when I have to make a bigger architectural decision, then I don't jump straight in and code. I usually come up with two or three possible solutions in my head (or on a piece of paper). I will stare at the wall for most of the afternoon, go for walks, as I play the ideas off against each other. After a day or two I usually have an idea of which solution is better, and why.