Jamie Thingelstad

Tesla pushed my Model 3 reservation to “Late 2018”. In “Musk-speak” that reads “Mid 2019” to me.

The video of these Falcon boosters landing today is amazing. I have to remind myself repeatedly that it’s not a movie. 🚀

Using Super Bowl ads as an opportunity to highlight for my kids how brands attempt to manipulate their emotions in ways that benefit them. 🤓

Snowy trail from today’s bike ride. Went down once.

As our environment gets more complex we need to be better educated to navigate it. For example, I think that people would be more protective of their privacy, if they learned all the ways the data is used to manipulate them. I have been considering lately that we need to better identify other patterns that are intentionally used to create addictive behavior in applications and websites. Knowing these patterns may allow us to understand certain features for what they are and avoid them.

Pull to Refresh

Bucket this in with any refresh mechanism that gives you that rewards when there is occasionally something new to see. Open your email and pull to refresh? Is there anything new? It is reward seeking behavior. It is well established that having a random award (new email!) appear after an action is an addictive pattern.

Infinite Scroll

This pattern ties into our desire to “finish” a set of activities. When we have read through all of the items, we get that reward of completion. Infinite scroll tricks us into reading more and more, waiting to get to the end. Eventually we realize that we will never get to the end and have to give up. Instead of the reward of being done, we have the shame of giving up.

Feedback Loops

These come in two flavors, public and private. How many likes did that post get? That is a direct feedback loop to reinforce some pattern of desired behavior. This is an obvious one to see and is present in all social feedback loops.

There is also Analytics as Addiction. Exposing the activity based on your content is on the surface a good intent to inform you on how effective your content is to some goal, whatever that may be. But it also reinforces a desire to check repeatedly and insidiously alter behavior to steer to more engagement.

I have also noted that some of these patterns show up in other places that I don’t think of as intentionally addictive. They become user paradigms that people adopt as best practices. Pull to refresh for example appears in nearly all email clients. There is no commercial benefit to us getting a reward for obsessively checking our email, but its presence can encourage it.

Did a very short ride on my Fat Bike in the snow. It’s so much fun to ride around in the snow. I need to do that more, and dress warmer for it too!

I’m reading 📚 Why Buddhism Is True and the references to “modules” of the mind keep reminding me of the characters in Inside Out! 😁

I have been happy having my blog hosted in Jekyll and built as a static site with Netlify. There is a wonderful calm to knowing you just have a bunch of HTML pages. It’s light and airy. But, and this is a big one, I’ve found authoring to be simply too hard. Writing using a source code workflow adds too much friction.

Tonight I’m trying out Forestry.io and I’m very impressed. 👍 There are a number of content management tools for static sites, but I’ve found most of them fail immediately since I have more than 1,700 blog posts and I put them in :year: folders inside of _posts and that simple part causes most of them to fail. Similar issues exist with where you host images. I was very happy to see that Forestry.io worked right out of the box with that. It even built nice front matter templates based on the content it found inside of my site!

I’m putting this post together to share how impressed I am, and also as a test of the posting interface. If you are using Jekyll or Hugo I would highly recommend you look at Forestry.io!

Snowshoes. ❄️

Winter fire. ❄️🔥

First run with the Sous Vide. Making beef tenderloin.

Sunday morning project: Figured out how to connect Workflow and Pythonista and rewrote the links section of the Weekly Thing in Python so I can structure it better.

Ticket to Ride!

I win! 😊

I have an irrational enthusiasm for updating firmware. 🤩😎🤞🏻