writing less code and going with the grain
Periodically we need to remind ourselves of good common sense coding practices. Two simple but very powerful are: 1. write less code Sometimes the best solution is just to write less code. We need to think before implementing: how can I write less code? I may come up with an acceptable solution, but there may be a better solution with less code. Its possible my first solution is not the best. A good time to do this thinking is before you get too far into an implementation. At a certain point you're too deep, too far along to easily change or reverse course. But even if you are, don't be afraid to change course, even if you may lose some time. Its still typically more efficient to change when building a feature than after its been released to production. 2. "go with the grain" Systems are often built in a certain way and when we change those systems we should try to follow that way. Build on the existing architecture, on the current algorithm on existing conventions o...