I love guard clauses and conditions. Simply put, a “guard” in programming is something that checks that inputs are as expected. If they are not, the code either fails or defaults to some predefined result. I want to argue that
Don’t Pad Your Comments
So I met this comment the other day†: †anonymized and exaggerated for entertainment purposes
|
1 2 3 4 5 |
/// <summary> /// The purpose of an objective highlighter is to highlight the relevant objectives. /// </summary> public class ObjectiveHighlighter { |
Don’t write comments like this. Let’s break this down: “The purpose of an objective highlighter is to highlight the relevant objectives.” First off, we are
Don’t Break the State Machine!
Designing finite state machines requires good discipline and a shift in design paradigm. It’s very easy to “break” a state machine by implementing improper design. It is very tempting to take shortcuts, but it never leads to clean lasting code.
Technical Debt and Delivery Times
Today, I want to muse on how new code features take ever-so-longer, specifically, how increasing delivery times are the symptoms of bad code. I’ll focus primarily on recognizing the issue (rather than avoiding or solving it). The Mystery of Increasing