Author: Chad Michel
SOLID, Part 4: Interface Segregation Principle
In this five-part series, I’m covering each design principle laid out in SOLID. In this post, I am covering the Interface segregation principle. The “I” in SOLID is a principle that is easy to skip over. Everyone will always remember the “S”, because it is first. The “L” is easy to remember because it is…
Read more…
SOLID, Part 3: Liskov Substitution Principle
In this five-part series, I’m covering each design principle laid out in SOLID. In this post, I am covering the Liskov substitution principle. Now is when things get interesting: program to an interface that can be implemented by many services. The Liskov substitution principle (LSP), created by Barbara Liskov, says we can substitute one service…
Read more…
SOLID, Part 2: Open / Closed Principle
In this five-part series, I’m covering each design principle laid out in SOLID. In this post, I am covering the Open / Closed principle. The Open / Closed principle is hardest to argue for. In our SOA (service-oriented architecture) world, we try to avoid using inheritance as a method to change behaviors. We would tend…
Read more…
SOLID, Part 1: Single Responsibility Principle
SOLID is an acronym created by Robert Martin (Uncle Bob) to describe five principles we should follow to make software designs more understandable, flexible, and maintainable. In general, these are very good guidance. While I don’t think the acronym is perfect and I don’t really focus on the open / closed principle, I do think…
Read more…
A Website Without Servers – Using Azure Functions: Part 8
Azure Functions fit a nice slot: for times when you don’t want to deploy much but want a little bit of logic in the cloud. There’s another feature that really gives Azure Functions some legs: you can proxy request to blob storage. This might not seem like a big deal, but it is a game…
Read more…
Whatever Bill Has…The Results
Last week we launched the “Whatever Bill Has” app, which I built as a demonstration of Azure Functions. This app is basically Build-A-Bear, but with Bill Udell. Users had eight possible options: four shirts and two pants. Bill was gracious enough to provide us with some great shirt and pants options. He also chose a…
Read more…
Whatever Bill Has
Those of us who are engineers know we aren’t looked up to for our fashion sense. We tend to be t-shirt and jeans people, or sometimes t-shirt and sweatpants people. Now this isn’t a sign of anything wrong, but I often feel engineers are just focusing a little too much on the function. I think…
Read more…
Don’t Design the Database First
Build bottom-up right? Start with the database schema, then models, then the UI, then ship it, right? Well, I think the majority of new projects would benefit from not focusing on the database until much later. Why not focus on the database from the start? Managing database changes in the early phases of a project…
Read more…
A Website Without Servers – Using Azure Functions: Part 7, Angular Service
If you haven’t been following along in this series, we are building an “Engineer Fashion App” using Azure Functions. I recommend looking back at Parts 1, 2, 3, 4, 5, and 6 to see what we’ve done so far. Let’s assume we have an Azure Function that returns some JSON for our wardrobe and that…
Read more…
A Website Without Servers – Using Azure Functions: Part 6, Some Basic Plumbing
If you haven’t been following along in this series, we are building an “Engineer Fashion App” using Azure Functions. I recommend looking back at Parts 1, 2, 3, 4, and 5 to see what we’ve done so far. At this point, we have an Angular site and we have a backend that can communicate with…
Read more…