I had a meeting with a customer (let's call her Kate) last week, and she wanted some changes to a web-based messaging application that my group owns and manages. That meeting didn't exactly go as planned. Blame Tennis Here's how the conversation between myself and Kate went: > Matthew: OK, so
I've been writing this blog for about a year and a half now, and I firmly believe that every software professional should write a blog. It's an invaluable tool for connecting with other professionals, for getting your ideas out there, for making bad jokes making good jokes. I've told this
One of the commenters on my blog posed an interesting question on my article about serializing enumerations in Web API [https://www.exceptionnotfound.net/serializing-enumerations-in-asp-net-web-api/] : He wanted to know how someone who is querying a Web API might know what possible values a given enumeration has. I didn't answer that
Danny Shadows flank me as I march down Jamestown Avenue toward the short, squat building in the distance. The sun's last few rays are off in the distance, casting a lavender twilight into the sky that would be beautiful if I had the time to admire it. Night will soon
NOTE: This is the final part of a five-part series in which I detail how a real-world ASP.NET Web API app using the Command-Query Responsibility Segregation and Event Sourcing (CQRS/ES) [https://www.exceptionnotfound.net/pattern-overview-command-query-responsibility-segregation-and-event-sourcing/] patterns and the Redis [http://redis.io/] database might look. Here's Part 1