Sticking with the Old or Trying New Things

Reading Time: 4 minutes
Yesterday I went for a half hour drive to do a favour, but in arriving where I had to do the favour I found that people were deeply focused and did not want to be interrupted so I went for a walk. I didn't swap to the hiking shoes that were waiting patiently in the car. I wore my "recycled" shoes instead. I eventually regretted this because the ground that was frosty, also had deep puddles of water and I had to walk through them. Two or three times my feet got wet. While getting my feet wet I was also listening to a Linux Podcast, episode 56 of Linux After Dark and they were discussing whether people like to adopt a system and stick with it, or whether they like to experiment and try new things constantly.

I feel that way about watches at the moment. For plenty of people watches are like televisions. "I haven't owned either for decades, my laptop and ipad are enough." For years I was without a watch, and without a TV. As a student I never felt the need. It's only because people had spare televisions that I ended up with one. I never bought one for myself.

Since I bought myself one or more raspberry pies I have been experimenting with various instances, to see how to set them up quickly, and experiment with implementation and more. In the process I am learning skills that I had not experimented with in years. One of these is to flash a USB key with a version of Linux and rebooting a PC from the USB key to run linux. It worked so well that now I am fighting the desire to install Linux over Windows and have the windows machine become a Linux machine.

Watches

Suunto, Casio, Apple and Garmin make watches, and each one tries to quantify the wearer, so it feels as though the wearer must wear all three or four brands to get complete data for all four platforms. but to do this makes us eccentric. The simplest workaround is to track with one device, and manually update all the others.

Whether you wear a Casio, Garmin, Apple Watch or Suunto is also about something else. User Interface. The Garmin Instinct and Casio g-shock watches look tough/solid, while the Apple Watch and Suunto Peak 5 look more fragile, more elegant. The other difference is that the Garmin watch is solar powered and can last for weeks in summer, whereas the Apple Watch and Suunto Peak five can last for a day, or several. The Garmin watches can last for years, by default, because they use mobile phones to do the hard work. They just count steps and time.

Personal Technical Debt

I like the idea of Personal Technical Debt. The concept exists for IT and programming. Writing code is one thing, but updating it later on is a challenge. To give a simple example, if you write a static website by hand then every page that navigates to other pages, needs to updated every time a new page is added. If you use Hugo or another static website generator you see this with every build. My blog is both on wordpress, and as a static site. As a wordpress blog it's slow and clunky to update because of all the bloat wordpress has added over the two and a half decades that it has been around.

In contrast with Hugo you write you page in markdown, add the categories and tags, run "hugo" and fifteen seconds later the site is ready to publish via GIT FTP. I spent months updating my static site to PHP before being sidetracked by Hugo and blogging.

The New Machine Routine

A while ago if you started to use a new machine you would need to log into all your sites, across several browsers. When I did this once or twice a year it felt slow and uncomfortable. Now that I slide between web browsers fluidly the time it takes to be up and running in Chrome, Firefox or other, is a few minutes. This is because my personal technical debt is low, and because it has become routine to slide between browsers, whether different versions of Chrome, Firefox or other.

With the Raspberry Pi Imager app you can instantiate a new server on an SD card within minutes, and it will be ready for you to log in via SSH whilst connecting to wifi with no user intervention. This is great because you can setup a headless system in a location with no monitor or keyboard.

Devops

When I started following courses on JavaScript, Ruby, Ruby On Rails and more I would get instructions on how to setup an environment and I wasn't familiar with the process so I had to follow the instructions attentively. By trial and error, as well as repetition the process became relaxed.

I find that, as I become more comfortable with doing things from the command line, I find docker walk throughs more frustrating than helpful. This is because I want to get instructions on how to setup the environment fully, without the overhead of docker running in the background. On a 2016 mac book pro docker slows down the computer.

And Finally

When we do something two or three times we need to follow the instructions when we get stuck. If we set the time on a casio watch several times then it becomes habit. If we implement Linux instances on SD cards and experiment until we break things, then we know how to do things, without breaking them, in a production environment. If we change web browser once every few months or years it can take a while. If we do it several times a month it becomes second nature. That's what experimenting is about.