The 30 Day Health Reboot was about getting focus on the various health metrics that I track each day and grade myself on. While I’ve been very consistent in measuring these things going back to 2017 when I came up with the concept, I haven’t been very good at holding myself accountable to them. That makes the whole “goal accountability” part of this exercise a misnomer most of the time. It hasn’t been a total waste though. I probably would have gotten my act together for even less time than I did over the years without it. But I want to keep doing better. Having a closeout and kick off of each of the “phases” was something I always intended to do but never did. This is my attempt to bring that in line too.

Week #4 (plus two days) of my 30 day Health Reboot challenge is now in the books. With that the 30 day challenge is also completed. My final week had its rough points, as I predicted it would, but had lots of success too.

Week #3 of my 30 day Health Reboot challenge is now in the books. I’m pleased to report that I finished it even stronger than I did the previous weeks.

Yesterday I wrapped up the end of the second week of this 30 day Health Reboot challenge . The “challenge” is really just a question of if I can actually get good grades on each day of my daily metrics with the slight twist of needing to be at least 20 minutes of cardio every day. Week 2 was pretty solid on everything except diet.

I’ve really been dogging it on the health front. Metrics, self graded, have been in the toilet since middle of last year. To be honest, they were only good for a total of three months last year. Diet and exercise, captured by those metrics, was shit and it is reflected in my cardio fitness, strength fitness, body weight, and body composition all being in the toilet. When I had my comprehensive annual physical and blood work I figured my middle-aged body was probably going to show signs of being worse for the wear. Thankfully everything was still in line. That’s a dodged bullet not a sign that the status quo is okay though. So here I am one week into my 30 Day Health Reboot.

I just recently pushed an update to my Dart Result Monad Library bumping the version from 2.0.2 to 2.1.0. For this version I added a feature that I’ve kept running into with my development of Relatica: wanting to do something non-transformative with a result and then just pass it on to the next stage. For full details on Result Monads and my initial implementation check out my original blog post and/or this post on the Dart Result Monad 2.0 release updates .

My first computer was an Apple //c. I have been an off again/on again fanboy of Apple several times through my life. They are my go-to mobile device manufacturer right now. In the past couple decades though I learned to take their advertising claims with great skeptecism though. I’m reading through this 1978 Byte Magazine special Pascal issue . One of the things I love doing while reading this old magazines is look at the ads. When I ran across this ad from Apple Is was admittedly taken aback by how brazen their claims as market leader were. It seems that exaggerating beyond the usual marketing schtick and outright lying goes back to Apple’s earliest days.

A big part of the Dart Snake project was so that I could evaluate the experiences of using Dart for server side development. A year ago I looked at the REST server landscape with this post and how Dart compared to Go in that respect . The Dart Snake project instead let me look at how well Dart worked for the front end by doing three different implementations for the web: Flutter Web, Jaspr, and plain old Dart Web Standard Libraries. In this post I compare these technologies with respect to the development experience and performance. If you’d like to play any of these versions to compare directly you can find the links below:

• Dart Web Snake
• Jaspr Web Snake
• Flutter Web Snake

For the final segment in the The Dart Snake Project we will create a web implementation using the Jaspr Framework . Jaspr is a web app framework that works for building both server side rendered and client side rendered code. This will allow us to write the app with some of the niceties we had with Flutter while using actual HTML/CSS constructs not the “rendered in a browser” style web technology that Flutter Web provides. The code for this project, as well as screenshots, and other details can be found at the dart-snake GitLab project page . This is open sourced under an Apache 2.0 License.