research Yep, We Should (Almost) Always Build An API Last week I published a post entitled Opinion Time: Should Developers ALWAYS Build an API?. I got quite a bit of useful feedback on that post, and so I decided that I needed
architecture Opinion Time: Should Developers ALWAYS Build an API? There's been some talk in my office lately about the practicality of always building API (Application Programming Interfaces) backends for our apps. Some of my teammates argue that it ensures portability, that we
web-api A Simple Organization for ASP.NET Web API Producer/Consumer Apps My team regularly writes ASP.NET Web API projects which have multiple consumers, and oftentimes we also write at least one of said consumers. To accomplish this, we often invoke a project layout
musings "Simpler" Is Subjective: How Bad Assumptions About Architecture Kicked My Ass I'm doing some heavy refactoring on a project that I've recently joined but that has been underway for months. The code is a mishmash of different styles and an uncertain architecture, so my
