Nathan Grigg

Well done Bruce Springsteen. I’m touched by the designation “Winter of ‘26.” Some events are too momentous for a descriptive label. Here’s hoping we remember it as a turning point, a wake-up call to the complacent.


Taking a Stand

US politics are more about identity and power than principles, even though we like to pretend otherwise. In my high school in conservative, rural Idaho, we would debate the virtues of small, limited government, second amendment freedoms, family values candidates, and I was duped into thinking the choice was between Platform A or Platform B, when it was really a choice between giving power to a “friend” or an “enemy.”

It took me an embarrassingly long time to realize that my principles were more aligned with the Democrats, even though I felt “more at home” among the Republicans. But I have also changed, trading Idaho for Seattle, then Los Angeles, to the point where today I feel more at home in a city coffee shop than a county fair or a church service.

While I have always voted against Trump, I have supported some candiates that I now strongly regret. And I try my best to see the humanity in those who did vote for him, because everyone has their own journey.

But today, everyone must oppose the Trump administration, with its calculated, provocative, performative violence, including but not limited to the killing of Renee Good and Alex Pretti. We cannot accept the lies, obstruction, and cover-ups that have followed. Anybody involved in or responsible for these violent acts or their cover-ups should be impeached, removed from office, and/or put in jail for their crimes. Every person in power who refuses to hold these offenders to account should be voted out of office and remembered as the cowards that they are.

We cannot wait until the next election to take power away from these monsters. Speak up today, set the record straight if you’ve had a change of heart. Call your representatives and tell them to defend us and enforce our laws.

ICE is not our friend; Trump and his enablers are our enemy.


A GMT Watch

I got a new watch.

I’ve almost exclusively worn an Apple Watch for the past several years. I still wear one when exercising and sleeping, and I plan to still wear it on some other occasions, but I wanted to see what it was like to go back, shall we say, to a simpler time.

My initial feelings are a happy dose of nostalgia. Back before all of our phones and watches and cars were synchronized to NIST time, I would carefully synchronize my Timex digital watch to the school bell time. It was satisfying to know exactly how much time was left in class (or passing period) while most of my classmates just had to wait and wonder when freedom would come (or end).

With a “dumb” watch, there is this same sense of satisfaction, that I know the precise time not through the wonders of the internet, but because I made the effort to accurately set my watch.

A GMT Complication

My new watch is a GMT watch, which is a popular watch style over the last century or so, because it makes it easy to know the time in a second or even third location, and can make it easier to change the time as well.

There are many different styles of GMT watch, but they are usually distinguished by a separate “GMT hand” that makes one revolution per 24 hours, compared to a traditional hour hand that revolves once per 12 hours. A GMT watch typically has the traditional hour hand as well, which most people call the “local hour hand,” because it tracks the time of your current location. Both of these hands are typically aligned to the same minute hand.

Being non-smart watches, they are relatively simple to configure. A true GMT or flyer GMT lets you adjust the time (minutes and hours) on all three hands simultaneously, and then jump the local hour hand forward or backwards an hour at a time. On a caller GMT or office GMT, the jump function moves the GMT hand forward or backwards an hour at a time. Either way, you can track both the local time and a separate reference time, but the caller GMT is more cumbersome to travel with, because if you change time zones, you have to reset the watch the same way you would any watch, and then also fix the GMT hand to point back to whatever reference time you want to track. A flyer GMT lets you quickly adjust the local time without messing up the GMT hand at all.

Many GMT watches also feature a rotating bezel labeled on a 24-hour scale. This gives you a way to quickly change the meaning of the GMT hand by shifting the labels instead of the hand. Hence you have the ability to track a potentially third time zone. I say potentially because on most GMT watches with a bezel, the bezel is the only set of 24-hour labels, so if you rotate it, you might not know exactly where the GMT hand is pointing on the “natural” set of labels.

Here are some examples of tracking two or three time zones on a GMT watch:

It is 10:11 a.m. in Central European Summer Time, and the GMT hand is showing 08:11 UTC.

It is 10:11 a.m. in Central European Summer Time, and the GMT hand is showing 08:11 UTC.

By rotating the dial four 15-degree clicks, we can read the New York Daylight Saving Time (UTC−4) as 04:11.

By rotating the dial four 15-degree clicks, we can read the New York Daylight Saving Time (UTC−4) as 04:11.

In these examples, note that the twelve o’clock position represents midnight UTC, and in the second example, the 20 (which is −4 modulo 24) lines up with this slot so that we can read UTC−4. And even with the bezel rotated, you get a sense of the UTC time because you will at least remember where 0, 6, 12, and 18 would be on the unrotated bezel.

Open to interpretation

Although a GMT watch only has a few configurable parts (minutes, local hour, GMT hour, and bezel rotation), you get to choose what the configuration should be. If you really wanted to, you could have the “local time” always be your home time and the “GMT hand” be your current local time.

I knew I wanted to use the local hour hand the normal way, with the local time of wherever I happen to be (usually in Los Angeles). At first, I thought that I would use the GMT hand for UTC, and then rotate the bezel to whatever second time zone I was actually interested in. But I was quickly annoyed that the direction of the GMT hand didn’t really have any meaning to me.

At 9:29 p.m. Los Angeles winter time, it is 05:29 UTC

At 9:29 p.m. Los Angeles winter time, it is 05:29 UTC

Next, I decided to use my home time (or at least UTC−8, more on that in a bit) for the GMT hand. This way, no matter where I am in the world, the GMT hand in the upper half means it is night in Los Angeles, and in the lower half means it is daytime.

Still 9:29 p.m. in Los Angeles, with the local 24-hour time of 21:29 shown on the GMT hand

Still 9:29 p.m. in Los Angeles, with the local 24-hour time of 21:29 shown on the GMT hand

Then I realized that, because my watch doesn’t have a fixed set of labels, I could orient the “natural” 24-hour scale with midnight at the bottom and noon at the top, imitating the path of the sun. I decided to keep the bezel oriented with the zero marker at 6:00, so that I can read the Los Angeles 24-hour time off the bezel, if I want.

Again 9:29 p.m. in Los Angeles, with the local 24-hour time of 21:29 shown and the bezel rotated so that noon is at the top and midnight at the bottom.

Again 9:29 p.m. in Los Angeles, with the local 24-hour time of 21:29 shown and the bezel rotated so that noon is at the top and midnight at the bottom.

Then when traveling, I can intuitively read my home time off the GMT hand.

Jumping the local time to 2:29 p.m. (Tokyo time), the GMT hand and bezel still pointing to Los Angeles time of 21:29.

Jumping the local time to 2:29 p.m. (Tokyo time), the GMT hand and bezel still pointing to Los Angeles time of 21:29.

And in this configuration, midnight UTC happens when the GMT is at the two o’clock position, which means I can easily spin the bezel to read a third time zone, for example, putting the 1 at two o’clock to read UTC+1.

Still 2:29 p.m. in Tokyo, and 06:29 in UTC+1. Evening in Los Angeles.

Still 2:29 p.m. in Tokyo, and 06:29 in UTC+1. Evening in Los Angeles.

Los Angeles time zone vs UTC−8

Here is where things get a little speculative because I’ve only had the watch for a month, and haven’t had to transition to summer time. So I have plans but maybe I will change my mind after some experience.

The Los Angeles time zone is only UTC−8 on winter time. For the rest of the year, we observe Daylight Saving Time, which puts us at UTC−7.

There are a lot of reasons to leave the GMT hand at (noon-on-top) UTC−8. First of all, it makes adjusting for Daylight Saving Time a simple jump of the local hour hand. It also preserves the two o’clock UTC reference point year round, making a third time zone a bit easier. It is also somewhat convenient because I can still track (approximate) astronomical noon and midnight.

But it also means that during the summer, if I want the 24-hour bezel to track Los Angeles 24-hour time by default, then it has to be one 15-degree rotation askew.

Local Los Angeles summer time of 6:48 p.m., the bezel rotated to show UTC−7 time of almost 19:00, but the GMT hand also shows the natural solar time of almost 18:00.

Local Los Angeles summer time of 6:48 p.m., the bezel rotated to show UTC−7 time of almost 19:00, but the GMT hand also shows the natural solar time of almost 18:00.

Quick spin of the bezel, aligning the 9 with the two o’clock marker, to check UTC+9 Tokyo time, where it is nearly 11 a.m.

Quick spin of the bezel, aligning the 9 with the two o’clock marker, to check UTC+9 Tokyo time, where it is nearly 11 a.m.

The Apple Watch GMT Face

Many years ago, I tried to use the Apple Watch GMT Face and didn’t last long. I looked at it again to remind myself why I don’t like it.

First of all, you have no choice about any orientations. The local hand has to match your local time (but at least it automatically adjusts when you travel). And of course, up has to be midnight because the programmers might die if they had to add that level of complexity.

The GMT hand also has to match your local time as well. As I mentioned, I don’t like how this messes with my intuition in the admittedly rare case when I’m in a different time zone.

You track a second time zone with a software spin of the bezel. Making use of the flexibility of a digital screen, the bezel is two-toned with the colors representing night and day, based on the current sunrise and sunset in the second time zone. Analog GMT watches often have two-toned bezels, with transitions fixed at 6 and 18. (You could argue that 6 a.m. and 6 p.m. are more useful markers than sunrise and sunset in a time zone where you aren’t currently located.)

Unfortunately, the Apple Watch bezel isn’t actually labeled except for the index closest to the hand, because otherwise the digital face gets too cluttered. Even worse, if you have your watch set to show 12-hour time, the index gets labeled with the 12-hour time, with no indication of a.m. vs p.m. except for the color of the bezel.

Apple Watch showing 2:44 p.m. in Los Angeles, 10:44 p.m. in London. You infer that pink is night because it is so long, or from the triangle that still marks midnight. Note that the GMT hand tracks Los Angeles time (currently UTC−8), but with midnight on top, so UTC midnight is at the eight o’clock marker.

Apple Watch showing 2:44 p.m. in Los Angeles, 10:44 p.m. in London. You infer that pink is night because it is so long, or from the triangle that still marks midnight. Note that the GMT hand tracks Los Angeles time (currently UTC−8), but with midnight on top, so UTC midnight is at the eight o’clock marker.

Finally, and this is an ongoing gripe I have against Apple, by default the time zone label in the middle of the face says CUP for Cupertino (just like in iPhone Settings). If that annoys you, you can change it to SF for San Francisco. Neither of those is the correct name of the time zone. Twenty years ago it was cute to label the Pacific time zone as Cupertino in honor of your headquarters. It’s not cute anymore.


Many years after starting The Wheel of Time series (I took a few years’ hiatus between the first 7 and final 7 books), I finished it. Great world, great characters, overall lots of fun.

Hard to do the series justice, but I guess I would say the first few books are the most exciting, the middle books make for some interesting world building, and Robert Jordan started to pick up steam again before his life was cut short. I don’t believe he ever would have ended the series, too many ideas and too many stories.


On a single ten-minute ride from the bus stop to my house, two middle-school-aged kids and one preschooler complimented my bike.

My red Brompton foldable bike

The backyard of my childhood home, Pocatello, Idaho. When I was a kid it was potatoes on the other side of the fence.


Proud of my kiddo who raised $200 for the Trevor Project by selling crocheted frogs at a “marketplace” event put on by the high school.


Many years after starting, I finally finished Robert Jordan’s Wheel of Time series. I think I did the whole thing by audiobook, which by my calculations (assuming my typical 1.4x speed) is 321 hours of audio. Great series!


I’m slowly moving to Jujutsu for my version control needs. For years, I’ve been using Mercurial-based interface to Piper at work and Git at home, and switching challenges my muscle memory. Jujutsu provides a common interface that can handle a central repo in either format. I find it easier to work with than Git or Mercurial, but there is a learning curve.


Roberto Clemente Bridge and Downtown Pittsburgh


Mellon Square, Pittsburgh. I love how much seating there is at this park, even if no one was taking advantage.


It is long past time for a screenshot file type. Pixel-based image format with selectable text and clickable links, annotations, and a context link to view the original source.

(Most of this you could do with pdf, but you could also do it more simply. Either way, phones and computers should be able to create them properly from apps and web pages.)


I feel very powerless to stop the intentional harm and destruction caused by Trump and Republicans in power, but I have absolutely no time for anyone or any organization that is happy about the way things are going, who sees Trump as a means to get something they want, or who sees Republicans as the lesser of two evils.


I installed the iPad beta to try the new windowing and I mostly love it. My main complaint is that I sometimes, maybe even always, want a window to go away and come back full screen next time, so much that I find myself maximizing a window before closing it. I would probably be fine if closing a window made it forget its size, and just minimize when you want to preserve the size.


Safari Web Apps and Composable Tools

I have two or three web pages that I tend to keep open on my desktop Mac. From time to time I have experimented with turning these into web apps, which makes it possible for me to hide them independently of my other web browser windows, helps them remember the appropriate window size, and helps me to not accidentally change them to a different page.

I was happy to discover that Safari makes it easier than ever to convert a page into a web app. Just select “Add to Dock” in the File menu (or share sheet). It puts an icon in the Dock, but you don’t have to leave it there because it also puts an application in ~/Applications.

But one of my pages is an HTML dashboard that is just a local file on my computer. I originally made it this way because it syncs via iCloud Drive, so that I can also view it on my phone or iPad if necessary. For some reason, you can’t make a web app to view a local file.

Simple HTTP server

The good thing about the Mac is that you can work around almost anything, building exactly what you want out of smaller pieces. And in this case, all you need is a little program that responds to HTTP requests with the content of the file.

There are many ways to accomplish this. I think MacOS still comes with Apache installed by default. It is running on my machine, at least. But I don’t like configuring Apache, so I didn’t use this method.

Python can make an HTTP server easily, just run

python -m http.server -b localhost -d /path/to/directory 8203

The -m flag runs the http.server module as if it were a Python script (that is, with __name__ == "__main__"). In this case, it starts up a server with the given options. The -b flag tells it to listen on localhost, so that other computers on your network can’t access the page. Then you give it a directory and a port number. After this you can visit http://localhost:8203/file.html and view the file.

But Python technically serves the entire directory, not just the file. You could write a custom Python script that imported http.server, and probably build exactly what you wanted. But when I want a tiny program, I always seem to gravitate towards Go, even though I tend to hate it for larger programs. I probably like it because you can compile a binary that has no dependencies, which reminds me of Turbo Pascal.

Here is a simple Go program that serves a single file at the port, and redirects any other requests to the base URL:

package main

import (
	"flag"
	"log"
	"net/http"
	"os"
)

func main() {
	bind := flag.String("bind", "127.0.0.1:8011", "The address to listen on.")
	filename := flag.String("file", "", "The file to serve")
	flag.Parse()

	if *filename == "" {
		flag.Usage()
		os.Exit(1)
	}

	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		if r.URL.Path == "/" {
			http.ServeFile(w, r, *filename)
		} else {
			http.Redirect(w, r, "/", http.StatusMovedPermanently)
		}
	})

	log.Printf("Starting server at %s", *bind)
	log.Fatal(http.ListenAndServe(*bind, nil))
}

I called it servefile.go, then you just run go build servefile.go and it creates a binary named servefile.

Keep the server alive in the background

If you go the Apache route, MacOS will already keep the server alive for you. If you go the Python or Go route, you need to tell the system to always run your server.

The easiest way is to buy LaunchControl and create a new agent to run your command, checking “Run at load” and “Keep alive no matter what.”

For more information, check out this 13-year-old article on scheduling with launchd.