To save the author some work dear reader, imagine the 3 Spiderman meme. Fill in “Who owns client data validation?” as the title and label the Spidermans (Spidermen?) Controller/Service/Persistence. One place has to own that responsibility. Let’s say we had a bug where we accidentally allowed updating …

Sometimes, it’s what you don’t say that hurts you the most. Let’s go. Side Effects A warning before we begin, I will use the words “side effects” heavily in this post. I come at this from the functional school of thought. Quite honestly, in said school of thought, “side” …

Chess has a long history of structured openings. You have a set of steps that put you in a certain position, with known strengths and weaknesses. You basically start the actual game several moves in. From the opening, you have several options to branch out from. There is also a common nomenclature. If I say, …

The primary point of good Software Design is to separate out what your code does from how your code does it. Being able to make this distinction in real time when coding is critical. Let’s explore. Core versus Shell Look hard enough in the right places and you’ll find the saying: ”Functional Core; Imperative …

Code has one of two roles: Add value to your business Drive the prior bullet point The first bullet point is usually called service code. It’s the service your company is being paid to do. The second bullet point can be one of many things, it could be controllers/webapps/etc. It can be cron jobs that perform …

I’ve seen multiple criticisms of Uncle Bob’s Clean Code involving the (short) length of functions. I’ve also seen multiple great responses to those rules of thumb. I want to derive another way to reason about the length of a function. Let’s begin. Thoughts I want the number and …