This week’s post is late. The proximal cause is that because of the Tech Shabbat experiment, I was shutting my computer down for the weekend. Weekends are the most common time I write and prepare to publish my posts. Therefore, an unintended consequence of the Tech Shabbat is that I didn’t have a post ready for Monday.

However, that is a poor excuse when we consider the distal causes of why the post is late, because the Tech Shabbat was a known event in my calendar. It wasn’t something that was unanticipated, and I knew roughly what participating in the Tech Shabbat would entail. I knew, for example, that I had to get my course marking done before the Shabbat if I wanted to give my students their feedback with sufficient time for them to use my feedback in their next assignment. I was able to always get my grading done before the Tech Shabbat began each week of the experiment, so why did I not do the same for the weekly blog posts?

The Tech Shabbat became a convenient excuse to blame, when really the blame lies with a poor writing habit. Maybe I would have finished the posts had I not participated in the Tech Shabbat, but instead of dwelling in a possible else-world, I should focus on fixing the things I have control over, such as my schedule and how I set my priorities.

Proximal causes are easy to fixate on, and are often more expensive to address (it’s why we spend lots of money on shiny new toys that promise to fix our problems). Distal causes can be harder to spot and require longer, steady investment to overcome.

Stay Awesome,

Ryan