Tag: code best practices
-
What’s in a name?
Naming things well is a huge deal. It’s hard and it should be hard. Poorly named things can mislead/confuse people, slow down velocity, and cause poor separation of concerns in design/implementation. On the other hand, well named things will allow others to correctly understand the function and use of an object, as well as encourage…
-
Simple is Better
Design Philosophy Generally, if a software package is hard to install, configure, or to otherwise use, I avoid it. If it’s hard to maintain or even tell what’s happening when its running I avoid it. I’m not being arrogant, I’ve just done it wrong more than once and had to live with it and/or fix…