Here I created a UsersRepository to consume all of the methods available for users and declared UsersResponse and a base StackResponse for the paging information that comes back on every request. Then within the UserResponse I get back the StackUser object off of UserResponse.Users

Source. A really nice guide how to create a .NET wrapper in C# for REST services.

Angular came up when discussing a new project early this year, a project that started as a way to make our existing PayLinks tool more flexible, but became a full dashboard re-write.

Our legacy dashboards are stiched together with lots and lots of jQuery selectors on top of Rails. PayLinks was built using Backbone and served from within our legacy dashboards. Maintaining a SPA within server generated views and seperate, often conflicting, jQuery logic had become too painful.

Why do we care what timezone a user is in? Well beause we have to show them dates that are relevant to them where they live. Unfortunately you hit a weird scenario where someone is traveling and they have to update their timezone settings, just because they decided to hop on a plane that week. Fortunately operating systems on laptops and mobile devices all adjust timezones automatically whenever they connect to the internet. So we have the ability to stop asking people what timezone they’re in by relying on the time on the device.