One Year of Shipping It: A Retrospective
In January of this year I started an experiment to ship one new thing every month for one year. As December comes to a close I would like to reflect on the past year to evaluate how the experiment went. Here is a breakdown of what I worked on this year & some quick thoughts about each project.
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
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 feature. It
Ship it: Six Months In
I am a little more than six months into a year long challenge to deliver something new each month [https://www.matthensley.io/ship-it/]. Forcing myself to make something new every month is proving to be pretty challenging, but also fun. I went into this experiment with the expectation that
Monetize Your Side Project: Ways To Get Paid
When you start building a side project, it is hard to resist daydreaming of one day gaining millions of users and, as a result, earning millions of dollars. Unfortunately, most developers don't know where to begin when thinking about charging for their app & some are even deterred by the idea
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
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.