No one's happy
If I've learned one thing over the last year of my directorship, it is that everyone will me when I am "doing it wrong". A point of criticism that I've heard from a few team members is the democratic style of decision making has slowed us down, and potentially hurts us in the long run. The counter style of leading, is I . . .
Times they are a changing
In 2011, I bought my first Apple machine. A supercharged 27-inch iMac with a gorgeous display, one that is still breathtakingly vibrant to this day. In addition to the amazing display, the iMac has some amazing speakers, internal microphone, and a 720p camera. That made it perfect for me, your neighborhood friendly remote consultant. I did my . . .
Update (May 14th 2015): Fixed the solution, please read further down.
Swashbuckle is a great library for automagically creating a Swagger documentation page, but it doesn't play nice with the thunderdome principle, also known as the one model in, one model out approach.
Let's take a look at an example of what I am . . .
"Follow your nose! It always knows!"
ASP.NET MVC is a great framework, dare I say that I love it. While my fondness for the framework goes deep, it is not without its flaws. One of those flaws, is the implementation of the AuthorizeAttribute. The implementation of the AuthorizeAttribute encompasses both authentication and authorization responsibilities, violating the single . . .
We are currently working on a new WebAPI filtering library that will allow consumers of our API to pass in expressive strings to denote ranges. We modeled it after the versioning behavior found in Nuget. You can see the range defining string on the left, where the right side is the expected behavior.
1.0 = 1.0 x (,1.0] = x 1.0 . . .
Not for the squeamish
Every bit is crucial when returning a response to an API consumer. Reviewing our current API, I noticed that some of our data was loaded incorrectly with invisible whitespace trailing some columns. This is a simple oversight, seeing that our data is imported from other sources. It is easy enough to fix via a database update, but could crop up . . .
Is it a good idea to simply store a single Following (per your example, 37 million documents for Bieber alone)? Another approach could be to store followers in a single document per user, but I . . .