It’s been far too long since my second child was born, but we finally booked the tattoo appointment. As I did with my first, I got a tattoo with the latitude, longitude, date, and time of his birth. Finding the right font is hard - I wanted something that doesn’t completely contrast with the existing tattoo, but was still distinct. Eventually, this is what I ended up putting together.
Marathon Training: Day -79; right foot still sore, likely from being barefoot all day; right hips still clicks while walking; back still sore overnight. 30x ankle raises, 30x dips, 2 minute plank rotation; need to get better about doing full exercise rotation. Whole30 has proceeded along, but the drain of not meal planning gets harder and harder each time we block out thirty days for this limited diet. We’ve had potatoes for every meal (either russet or sweet) to keep the carbs up. I am trying to find ways to pre-cook carbohydrates. This could include acron squash (Katie’s favorite winter squash), carrots, or even different flavoring on potatoes. In terms of stable meals, I’ve brought it down to a handful of decisions that can pull together a meal.
The last time we tried to start a Whole 30, it all just fell apart rather quickly – twice. However, this time, we have a much better plan for getting it kicked off. My wife started by creating a list of Reasons For Doing a Whole 30. She hopes that this will keep her focused on why she wants to stop reaching for the slice of cake, the can of Diet Code, or the bag of potato chips; she wants to be in the healthiest position possible when we start trying for another child; and she wants to have better productivity at work that the tiger blood brings on for her. For me, this is Marathon Training: Day -83.
Tomorrow, we start another Whole30 eating plan. The last two times I did this, it was both wonderful and horrible. In order to be able to look back on this experience one day and (hopefully) remember it fondly, I am going to attempt to put together a day-by-day activities list of how I
survived thrived during what will be my third trip. As with both of the other adventures, this started with a massive shopping trip to Costco and a bunch of food prep.
These are some notes that I typed up during an Azure Machine Learning - Data Camp that I attended at the Microsoft learning center in the Aon building. It was entertaining, informative, and all around a great session; unfortunately, it was entirely useless for my job, since this really has nothing to do with the work that I perform. On the plus side - I was able to recommend to my co-workers on the Analytics team that they should attend it.
Command Query Responsibility Segregation (CQRS) was not something that I easily understood. Martin Fowler did a thorough job of explaining it in often-linked post from 2011. However, I still did not quite grasp it at the time. I also wasn’t working on any project large enough or complex enough that it made sense to use a pattern with that level of depth. When I came back to the concept many years later while working on a significantly more complex project, I could put together all of the puzzle pieces but I still couldn’t quite see the whole picture. While researching the topic, I stumbled on a blog post by Cesar de la Torre from Microsoft - CQRS BUS and Windows Azure technologies. His picture was well worth the thousands of words that I had already read.
I may have gone down a long and twisted rabbit hole trying to figure out this problem, but I learned a lot about how model binding along the way, so I consider the whole experiment a productive use of my time, even if I end up ripping it all out in a few weeks. However, since I thought this would be a good idea, I figure others might find a good use for this knowledge. Thus, this is how I am using an explicity constructor when the input is in a
JSON format and parameter is bound using the request body.