Published on 12 August 2025
Nomad as Fuck is a project I ran, highlighting awesome nomads and talking about some of their stories. By nomads, I mean people with enough privilege to travel around the world and work remotely – somewhere between expats and tourists. This was the term I used ambiguously in the mid-2010s, pre-Covid and without a serious lens on what nomadism might entail.
The porject was born out of my desire to talk about all of the cool people I was meeting through Hacker Paradise, a remote coworker community I was a part of. Hacker Paradise changed me irrefutably; I learned a ton about different places, and made new and life-long friends. For all of the ills of remote work in third world countries, it was one of the first times in my life that I felt like I was experiencing abundance, instead of scarcity. Want to go climb that mountain then work? Sure! Want to travel to this country next week? Yeah! Want to see if you can put something on the front page of Hacker News? Why not.
I’ve been lucky and privileged enough to meet a lot of people, and to travel a lot, so Nomad As Fuck was my way of highlighting the ecosystem and talking about nomadism more. At the same time I ran it, I ran Antinomadic, which was the antithesis of this project – a series of letters between me and a friend about how hard it was to move all of the time. It didn’t last as long. It wasn’t as easy to write. It was more thoughtful.
Tomorrow, I am letting the domain nomadasfuck.com go. It’s not important for me to keep renting the project. But, for reals, I’ve just matured as a person. I would never make Nomad As Fuck now. I find it a bit nauseating, a bit naïve, and a bit silly. But I’m glad I had fun when I was younger. I don’t have regrets – just learning experiences.
I’ve now archived it and am hosting it only on Netlify. You can see the archive, here.
Published on 16 May 2025
A couple of years ago, I was reading about differentiating subspecies of swans when I came across a paper that used a term that made me stop and stare. The paper was from Britain in the 1960s, describing how individual Tundra Swans could be differentiated by the pattern of black and yellow on their bills. Some birds were called “Nobbly”, some “Pennywise”, some “Shieldy”… and some “darky”.
I’ll grant that the original author was writing in the 60s, and that they may not have had the same cultural background that I do. But that term is invariably offensive in my own dialect. I kept reading, and I found that the term had unfortunately percolated through the literature since. Their paper had been cited as recently as 2018.
So, I wrote a short abstract and submitted it to AFO, the American Field Ornithologist conference. The conference was in Plymouth, near my uncle’s house and near my father, so I drove down, saw family, presented the poster, and made some connections. I think some of the people at the conference were confused why I was there – I didn’t have an agenda except to have something in the literature that said, “Hey, we shouldn’t use this term, let’s use another one.” After I drove home, I thought about how to make this more permanent. I worried that people wouldn’t find the poster online, hidden in my Google Scholar or my website.
So, I turned it into a short communications piece, and submitted it to Wilson’s Journal of Ornithology. Today, it was published:
Renaming a bill type for Tundra Swan (Cygnus columbianus)
The paper is really short. It’s hopefully easy to read.
Now that it is published, future scholars working on Tundra Swans should see it. Wilson’s demands that users translate papers into other languages; based on one of the papers that cited the original work, I asked some of my Dutch-speaking friends to help translate it. I don’t expect there to be a lot of Dutch authors who can’t read English, but it doesn’t hurt.
One of the considerations I had to think about during this paper was whether doing this would increase my risk of having liberal terminology on my résumé and website. That isn’t necessarily a good thing right now. Part of the reason I published this anyway is the open question: if I don’t publish anyway, why should others? I’m a very small target thanks to my privilege. It’s on me to do more, not less.
This paper is part of a much larger movement to rename bird names, moving away from eponyms. This has also moved over into taxonomy, with the recommendation that scientific names that are offensive should also be changed. I’m in support of those movements - I don’t think stability is as important as people say it is, as all human works ultimately change and we need to think on longer scales of time. Bill typing terms are not even remotely at the same scale as a name change for, say, the Cooper’s Hawk, but it’s all part of the same work.
I added a land acknowledgment to the piece, too, as I presented it in Plymouth. Across the street from the venue and a short walk south, there’s a small statue of my ancestor, William Bradford, a racist, genocidal colonizer. I’ve benefited tremendously from his and the state’s actions since the 1600s. The land acknowledgment is the least, almost literally, I can do. The work will never end, and every little bit helps.
Published on 11 May 2025
Sometimes, I want to me able to write a note in LaTeX, and not just in a comment, which I can have in the finished PDF and then come back to later. I think comments can be a bit too hidden, and when you have a lot of them, it’s tough to remember which ones were urgent. Highlights can do that.
Right now, I’m using this method to do highlights:
% TODO Remove this during final editing
\usepackage{soul}
\sethlcolor{yellow}
\newcommand{\highlight}[1]{\hl{#1}}
The comment helps me remember to remove it before I publish.
Published on 11 May 2025
I often need to grab the title of a web page. For instance, this comes in handy when I am creating a new Wikipedia Page, like this one for Raoulia grandiflora, where I needed to grab the title of web pages for the references.
To do this, I used to manually write out the titles, or guess at them. Then, I figured out that I could load up the sourcepage for the page using Firefox, and find the <title> tag. It wasn’t long after that that I realized I could use the Firefox Developer Console to type document.title, and then copy that to my clipboard and use it.
Today, I realized I could automate that, too. So, I made this Alfred Workflow. It uses osascript to copy the title:
tell application "Firefox"
set winTitle to name of front window
end tell
set the clipboard to winTitle
return winTitle
This is great, because I can now type ‘copytitle’ in Alfred, and then have the title right on my clipboard.
To make it easier to put these titles into BibTex, I also made this TextExpander template:
@misc{,
author={},
title={},
howpublished={},
url={},
note={Accessed: <insert date>
},
urldate={Accessed: <insert date>
}
}
The date is automatically inserted.
This saves me a good amount of time. Great.
Published on 09 May 2025
I often want to read books that I haven’t read yet. I want to have a better way to keep track of those books.
Here it is. This list will update as I go.
- Malintzin’s Choices: An Indian Woman in the Conquest of Mexico (New Mexico, 2006); translated Malintzin: Una mujer indígena en la Conquista de México (Ediciones Era, Mexico, 2015) by Camilla Townsend. Recommended by Federico Mena Quintero on 9 May 2025.
- James by Percival Everetter. Recommended by Federico Mena Quintero on 9 May 2025.