Clean Code - Thoughts on building & selling software

Thoughts on building & selling software

Sign in Subscribe

Clean Code

writing clean code

Your Variable Names Could Be Better

Clean Code Featured

Your Variable Names Could Be Better

Variables are such a fundamental building block of software development, many developers tend to overlook the important role variable names play to ensure a clear & maintainable codebase.

Design Pattern Primer: The Factory

Design Patterns

Design Pattern Primer: The Factory

When writing object oriented code we end up needing to create a lot of different objects. Sometimes the process to create those objects is complex or maybe we don't know exactly which type we will need to create. Situations like these are where using the Factory pattern comes in handy.

Having a Refactor Plan

Having a Refactor Plan

The Boy Scout Rule [https://deviq.com/boy-scout-rule/] is mostly non-sense. In any moderately complex system the smallest changes can have wide spread & unforeseen effects. Technical debt is a problem & fixing it should be just as important to the business as fixing a bug or adding a new

Code Clarity: Thinking About Code as Questions & Answers

Code Clarity: Thinking About Code as Questions & Answers

Anyone can write code a computer can understand. It takes an expert to write code a human can understand. In this post we are going to look at an example of how to add clarity to our code by thinking about our logic as a set of questions & answers.

Private Methods: What Do You Have To Hide?

Private Methods: What Do You Have To Hide?

We constantly refactoring & improving code bases but, sometimes we can be lukewarm about what we are doing. Enter the private method: Codebase Ruiner.

You (Probably) Don't Need An Interface For That

You (Probably) Don't Need An Interface For That

It's easy to do things in the name of best practices but, how often do we sit down and ask ourselves if that is the right thing to do in our current situation?