Tracking the standard is valuable but not everything in the standard is equally good. Standards are good for a lot of reasons but primarily because standard means consistency on steroids. In short following standards means being consistent not only with your but with other organization's rules too. This is cool because other organizations can be the ones … Continue reading Value Standards →

Writing sustainable code is a long term commitment. To be effective you must be consistent. Consistency allows: Easier expert chunking Tooling (very very important) Allows us to stop arguing about stuff that doesn't matter! (Even more important) What do I mean by consistency? Well consistency includes: Naming and formatting Parameter ordering Namespace naming Declaration order … Continue reading Be consistent →

Every time, when developers argue about some coding or project management rules, they bring up a lot of cases when these rules simply fail. In my opinion, this can be a very dangerous thing. Our jobs as developers is to code scenarios and think about all the possible outcomes of our algorithms. We want to know precisely when an … Continue reading Do not make rules for exceptional cases →

When talking about effective programming and style guides you can't list every dumb thing you shouldn't do, but I think you can follow some higher level principles. For example, my first advice would be "Don't be clever".  Being clever leads to highly un-maintainable  and potentially dangerous constructs. It is often tempting, to surprise yourself and your … Continue reading Be resonable →

I decided to write a short series of "Effective Programming" tips and for the first article I choose to  talk about style guides. What is a style guide? A Style Guide is a set of standards for writing and designing code. How do we format our code? When talking about style guides, the first question that … Continue reading Effective programming: Style Guide →