Side Projects 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.
Side Projects 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 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.
Clean Code Having a Refactor Plan The 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
Monitization 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"
Side Projects Ship it: Six Months In I am a little more than six months into a year long challenge to deliver something new each month. Forcing myself to make something new every month is proving to
SaaS 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
Monitization 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
C# 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.
C# 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.
.NET 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?
