Getting Solid with SOLID – Part 2- Open/Closed Principle

Software engineering principles and patterns help us craft good clean software. One such pattern is an acronym we know as SOLID. “O” represents the open/closed principle simply defined: “open for extension, closed for modification”. Today I’m focusing on open/closed principle and how it pertains to modern application development.

Continue reading “Getting Solid with SOLID – Part 2- Open/Closed Principle”

Application logs are your friend (and how to read them)

Your software application will crash. Even the most principled software following the best practices will inevitably have a bad day. Figuring out why it crashed and how to prevent it is a skill in and of itself. Fortunately there are steps you can take to help you when this time comes. Application logs are your friend and it is necessary to learn how to read them.

Continue reading “Application logs are your friend (and how to read them)”

Getting Solid with SOLID – Part 1 – Single Responsibility Principle

Software engineering is full of patterns and principles to help you get the job done. Sometimes those patterns and principles are defined very abstract and difficult to understand. Let’s talk about SOLID design principles in a 5 part series. Today we’re discussing the Single Responsibility Principle.

Continue reading “Getting Solid with SOLID – Part 1 – Single Responsibility Principle”