Opinion - Thoughts on building & selling software

Thoughts on building & selling software

Sign in Subscribe

Opinion

my thoughts and feelings

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.

Liquid Skills

As we move through life, we end up acquiring various skills to help us improve our careers. Some we focus on & develop deliberately, while others seem to be acquired almost by accident.

Burn It Down

As the year comes to a close, I am drawing the curtains on my Ship It experiment. I wrote up a small write up of everything, you can read it here. This article will try to summarize my feelings about the experiment as whole & outline where I am going to go from here.

Knowing When to Quit

Knowing When to Quit

For the past few months I have had pet project. I know, huge surprise. This was the one I thought, "When this is finished it will be a game changer". I stayed up late writing code, designing the perfect architecture, creating flawless CI/CD pipelines; It was truly a wonder

Ship It. Even If It Sucks.

Ship It. Even If It Sucks.

I love starting things. Right now I have 13 unpublished drafts for blog articles on various topics. I am the proud owner of thirty-nine domains. Six of them are in use. Ideas are great. I've got hundreds of them. Working products are better. Starting a new blog, app, or website

Why I Over Explain Things

Why I Over Explain Things

Hi. My name is Matt & I am a constant over explainer.

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?