LabRatz

I've lately been falling into the trap of thinking about implementation more than coding. All the more crippling since I don't even have a barely functional demo. It reminds me of a favorite phrase coined by a Japanese mogul who played a key role in reconstruction negotiations during Japan's occupation, Shirasu Jiro. An iron rule of conduct he enforced at his country club golf course was "play fast". It was how he lived his life as well, right until the very end. I think it applies to code as well. The less time you spend implementing the more you forget and have to backtrack or break stuff inadvertently. It's not an excuse for sloppy code either. If you want to code fast, in other words get something done, you can't be going back and forth. Just like golf, taking random shots at the ball will keep you wandering the course for lost balls. Not only will you be holding back the people behind you, you'll also pose a safety hazard. All the best coders do in fact code fast and their code is quality too (though there are exceptions). You simply can't produce a ton of sloppy code without everything come crashing down in flames.