After buying a 16” MacBook Pro the other month, I’ve been using a Thunderbolt 3 hub to connect it to my periphery devices. Luckily, in addition to the macbook, I am able to use the hub with my my work laptop when working from home. Normally, it works fine. However, last week I reformatted the work laptop with the KDE Plasma spin of Fedora Workstation 31… and my TB3 hub stopped playing nicely with it. Here’s why.
In my previous post, I mentioned that I had purchased a new 2019 16” Macbook Pro by the end of my macOS challenge. I have had the laptop for over a month now, but I made sure to take notes on some of my initial thoughts during the first few days. Here are those thoughts.
I have used many operating systems on my computers over the years, including decades worth of Windows versions, tons of Linux distros, several BSDs, iOS, Android, and even chromeOS. While I am familiar with using macOS (I often used the school Macs in college, and my wife had a Macbook Air throughout medical school), it is the one OS I have never tried as my personal daily driver. After switching to an iPhone and getting an iPad this year… I decided to give macOS a spin.
While working on a post a couple of weeks ago, I noticed that for some unknown
reason, my website wasn’t rendering correctly. After some back-tracking, I
remembered that I had updated the container I work in to a Fedora 31 base
image, which has a newer version of
hugo. So, I filed the problem as issue
finished my post in a Fedora 30 container for the time being. Here is a quick
explanation of how I eventually came back and resolved issue #26.
Since builing my desktop, whenever I work
on another machine, I usually end up ssh’ing back to it to work remotely. It
has my files, more power, and much of my work flow is done from a terminal
window anyway, so why not? The only issue I have with
ssh is that if I have
a spotty internet connection, or if I sleep/suspend my laptop while moving
ssh session will occasionally time out. Tmux
and tmuxinator make this less of an issue,
since I can re-attach my session, but I still wish my remote sessions were a
bit more seamless. They can be… using
Two weeks ago, I attended All Things Open (2019) for the second year in a row. ATO is an annual conference that explores and celebrates… well, all things open. Open source, open tech, and open government are all main topics at the conference. Best of all, it’s right here in the triangle (Raleigh NC). Here are some of my overall take-aways from this year.
About a year ago, I switched to the LG ud4379b, a 42.5” 4k IPS monitor. My initial motivation for upgrading was to convert to an IPS panel. However, my selection of monitor was an attempt to simplify my hardware, by pairing down my dual 1080p setup. While I wanted a single monitor, I didn’t want to drop my total resolution because everyone knows that multiple monitors are required to get any real work done, especially programming. Although, after a year of using my massive display, I started to tire from the large display paradox.
I play around with CI/CD pipelines quite a bit, both at home and at work. I have mostly used Jenkins, but I wanted to see how Gitlab’s CI/CD tooling has progressed over the last year. So, I decided to try to use Gitlab to manage the automated build and deployments of a personal project I’ve been working on. The first step of the process was to setup a runner my Gitlab instance could use for the builds.
Last month, I wrote about my switch to Joplin
for both my personal and work notes. While I enjoyed many features in Joplin, I
also had a few concerns about using the system long-term for all my notes.
As of last week, I am still using Joplin for all of my personal notes, but have switched
org-mode for my notes at work. Why?