Development Practices

Documentation is a tool for setting up context. It should help future developers answer who, what, when, where, why, and how.

Ever look at old code and think, "Why the #@*% did they do that?" Don't be part of the problem. Be intentional about describing what you did and why.

When your backlog is empty, it can be hard to know how to spend your time. Here are a few important things you can make progress on.

Don't use ad-hoc error handling in your application. Instead, use this step-by-step process so that your code is predictable and maintainable.

Use the most appropriate data structures provided by the programming language. Keep your error data as simple as possible without losing information.

Think of each error as either an exception or a failure (depending on how severe/rare it is), and classify the error based on what caused it.