Tag: Late

On Tardiness

For all the lip-service paid on this blog about doing the work, I have been posting late recently. My target is supposed to be going live by 9am on Monday mornings, yet I can’t remember the last time I had a post scheduled to go live on time in a while. I think the last time I was ahead was heading out for my honeymoon in 2019, where I had three weeks lead time while I was away.

Part of why I’m behind continues to be working from home – in the before times, I would procrastinate in the office from real work by writing. But since working from home over the last twenty or so months, all time feels like procrastination time. With no one looking over my shoulder, it doesn’t matter what I am doing on my screen so long as I continue to deliver on the goods.

And as with most procrastination, the longer I go past my deadline (e.g. today), the harder it gets to get to work on the task. It usually results in taking a mulligan for the week, or cobbling together a half-thought into a semi-stream of consciousness post just to have something shipped. You’re welcome.

It feels good to publish, but I shouldn’t consider it a win to get something up for the week for the sake of hitting the metric. At the same time, I should extend myself some measure of kindness and acknowledge that I still did the work.

I still show up to do the work, just not according to what was expected of a professional.

Stay Awesome,

Ryan

Unintended Tech Shabbat Consequences

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

On Late Posts

Despite my promise to do better on the Friday before last, I did not get a post up this past Friday (largely due to a report at work that kept me occupied during the day) AND I had no post ready yesterday (largely due to not keeping a regular writing schedule).

I’ve found sense of pride in not missing a weekly deadline for the last few years, but things have ground to a halt recently. I’ve let my workflow dry up in favour of short dopamine hits (my distraction of choice being YouTube) to take the edge off of the anxiety around not getting work done.

Thankfully, I have some time off of work coming up, which will help with recharging the old creative batteries. I’ll be back next Monday with a real post.

Stay Awesome,

Ryan