Hero Image
Single Responsibility Principle

The ‘S’ in SOLID design principles is for the Single Responsibility Principle. It is also the easiest one, in my opinion. The gist of it is that every part of the system should have only a single responsibility, including the system itself. Take the below code p { } u p { } p { } p { } b u / u / u / l b / b / b / i l l l c i L i L i L c o c o c o c g g g l i i i a o c o c o c s i i i s d g d g d g o o o U A e D e M e s c s e s a s e t l i r i h e h l h v e t e U e a r e r s r t e U e e e e s r U e ( s r ) e ( r ) ( ) On the surface, this looks fine, but those methods’ logic is neither reusable nor easily refactored.

Sunday, January 15, 2023 Read
Hero Image
Implicit Usings CSharp 10

To get things started, let’s make a clear distinction between .net 6.0 and C# 10. Though they come out bundled simultaneously, their versioning is distinct. Where are my using statements? With version 10 of C#, we also get Implicit Usings. In the simplest of terms, this means that you no longer have to spend time thinking about which namespaces to include in your application, you can start coding and the namespaces will implicatively be included.

Tuesday, November 29, 2022 Read
Hero Image
Thoughts on the Airpods Pro 2nd Gen

First impressions I enjoy headphones, headphone technology, and all it entails. This includes earphone tech and how it’s all being brought together. The original Apple Airpod Pros were my favourite wireless earbuds for many reasons. When Apple announced the second generation I was intrigued, Apple wouldn’t bring something out unless it was an upgrade on the original, right? Either way, I bought a pair to find out and…I was impressed!

Sunday, October 30, 2022 Read