Creating a Design Inspiration Archive

One exercise I’ve been doing for at least 8 years now is collecting media that intrigues me. Every day, I visit a few sources on the internet or stumble across content that introduces me to a new ideas, beautiful pictures, great layouts, or amazing typography.

I have collected over 4,210 pieces of media into folders on my computer. That turns out to be over 1 piece of media every day for the last 8 years. This post dives into why I find the collection process therapeutic, meaningful and important. Read more on Creating a Design Inspiration Archive…

Sticky Documentation, Part 2: Source Control History as Documentation

Last week, I introduced a concept I’m calling “sticky documentation” and reviewed a few ways that we can make the most of the “stickiest” documentation we have: the code. Today, I’d like to talk about another form of “sticky” documentation: source control history. Read more on Sticky Documentation, Part 2: Source Control History as Documentation…

Specifying the Destination of an Unwind Segue Programmatically

I once wrote an iPad app to help people take self-guided tours through a museum. One of the interesting parts of this application was that many of the views were implemented by the same view controller. The functionality of each screen remained the same with slightly different assets in each view. This would be a problem if I needed to Unwind to certain screens in my application.

Read more on Specifying the Destination of an Unwind Segue Programmatically…

Functional C# Application Composition, Part 3: MethodToDelegate

In part 2 of this series I made a case that switching from Stateless Single-Responsibility Objects to delegates and static methods lets us write simple, pure functions and lets us remove a lot of boilerplate.

Nevertheless, there was still one bit of boilerplate I hadn’t yet removed. It dealt with encapsulating dependencies to a method in order to match a delegate signature for use in other parts of the application. Read more on Functional C# Application Composition, Part 3: MethodToDelegate…

Web Application Architecture from 10,000 Feet, Part 3 – Frontend Development

In part 2 of this series, I focused on the basics of back end development. Here, I’m going to talk about developing client-side code.

Building Blocks

The front end of a Single Page Application (SPA) is composed of three major things:

Read more on Web Application Architecture from 10,000 Feet, Part 3 – Frontend Development…

Sticky Documentation, Part 1: Code as Documentation

I support and maintain a variety of applications in production. Some of these applications consist of what might be considered “legacy” codebases. When troubleshooting issues with these applications, detailed and accurate external documentation is not always available. I often find myself acting as a code archaeologist, reliant on only the contents of the source code repo to get to the bottom of a thorny problem. Read more on Sticky Documentation, Part 1: Code as Documentation…

3 Reasons to Attend GLSEC 2015

It’s that time of the year again. SoftwareGR is once again presenting the premier technical conference in West Michigan—GLSEC (the Great Lakes Software Excellence Conference).

The conference is on Monday, May 11th and will be held at the Prince Conference Center at Calvin College. Read more on 3 Reasons to Attend GLSEC 2015…

Functional C# Application Composition, Part 2: Delegates

In my previous post on the Stateless Single-Responsibility Object (SSRO) approach to C# application composition I reviewed the concept and its shortcomings.

To recap:

  1. You end up with a ton of classes splitting up semi-related logic across multiple files. This is necessary to conform to the classname == filename convention.

Read more on Functional C# Application Composition, Part 2: Delegates…

loading…