A friend forwarded me an article from Runner’s World (written by editors at Men’s Health) titled “8 True Tests of Your Overall Fitness”. The article describes the test, drones on about the author’s experiences, and then gives some helpful tips on how to meet the test objectives. I wanted a quick chart that I could easily reference, so I’ll just post it here. The 30 pound dumbbells and 315 pound deadlift assumes 200 pound body weight.
I have found that it is better to put structure in place around a project before going hog wild on implementation. While I recognize that some practices grow organically, a healthy amount of structure up-front can save a project from technical bankruptcy down the line. The two tools that I use early and often are interfaces and contract classes.
All of my other marathon posts seem to have the “three parts” theme going, so it probably fits for this writing. On the second of May, I ran the Wisconsin Marathon in Kenosha. It is combined with a half-marathon, and a delayed start 5k. I had a terrible experience, but I came away with some fantastic personal post-race analysis.
Two key library decisions needed to be made this week: choosing the object-relational Mapping (ORM) framework, and choosing a membership provider. To cut right to the end, Entity Framework and ASP.NET Identity were the solutions that I have chosen to utilize throughout the software. This week’s commit has been getting the initial implementation created, customized, and tested.
There are many posts out there for how to configure a database schema to handle scheduling events. The part that I found difficult to find was an algorithm for calculating future dates for each type of recurring schedule. I have started this series on Recurring Gifts as a way to document the process I went through to build the current system. Some features include: