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 can move to newer technologies more readily. Others agree, but say the primary reason is to provide
We've been having an ongoing debate in our team about what archicture to use to implement our new enterprise-level application. There are two possible solutions, one familiar, one fast, but we can't seem to reach a conclusion as to which to use. A lack of applicable data is forcing us
> There are only two hard things [http://martinfowler.com/bliki/TwoHardThings.html] in Computer Science: cache invalidation and naming things. > -- Phil Karlton Naming things is hard. Image taken from [How to Name Things](http://slidedeck.io/hoontw/naming-things), used under [license](https://creativecommons.org/licenses/by/4.0/)As
I've written before about the idea that code needs to have a reason to exist [http://www.exceptionnotfound.net/code-must-have-a-reason-to-exist-even-if-we-dont-like-the-reason/] . Right alongside that idea is another I frequently find myself having to be reminded of: code must have a clear, explicit meaning. Let me clarify what I mean by that
Let's use the POST-REDIRECT-GET (PRG) pattern to get rid of pesky warning popups in ASP.NET MVC.