Geekist / About
About Geekist.
An NGINX book. A Garmin tool born from an argument with a treadmill. Music, writing, open-source code and a frankly unreasonable interest in coffee. Welcome to Geekist.
Choose your rabbit hole.
Come for the engineering and you might leave arguing about music, poetry or how much cream belongs in coffee. Pick a direction. We have plenty of interesting detours. Code, architecture and experiments that occasionally get gloriously out of hand. We once moved five terabytes a day on an M2. That was fun. A small thought experiment. When does the output start moving? Chunks can move downstream before the entire input completes. From Promises vs Streams. Music, culture, unusual ideas and the connections between them. We follow questions that don’t fit neatly into any one discipline. In 4/4, one bar lasts 2 seconds. A 4-second slide fits two bars. A taste of the Timing Lab. Recipes and stories from the kitchen, with enough experimentation to keep things interesting. Occasionally the coffee becomes a matter of principle. A modest contribution to the Grospel. For the full calculations and theological proceedings, visit the Croffee meter. Poetry, essays, lyrics and experiments with language. Some pieces are mischievous, others uncompromising; none demands a single reading. Some pieces insist on being written. Start with Chaos Cohere, then wander into Cadence or As If. There isn’t a prescribed route. That’s rather the point.Tame the Tech
Peek inside
The Geekery
Peek inside
Fables for Food
Peek inside
The WordSmith’s Forge
Peek inside
The trouble with being a geek.
I’m J. I’ve spent more than two decades writing software, leading engineering teams, making music and finding new things to get curious about. I’ve also written a book about NGINX. Apparently, I have trouble leaving well enough alone.
Geekist began because I wanted somewhere to write about all of it. I had no interest in deciding whether a story about Node.js belonged beside one about music. They’re both part of the same life. Why should the website pretend otherwise?
Geekist is what grew when you garnish grief with grit and github
There was one problem. I’m an engineer. I kept building websites to make publishing easier, then spent so much time on the machinery that the writing had to wait. I told that story in The Editorial Engine. It’s a rather embarrassing pilgrimage for somebody who only wanted to write.
Well, the machinery is still here. So are the articles, experiments, code, music and food. The difference is that we finally have somewhere for all of them to live together.
We also make things.
Writing about a problem is one thing. Having a go at fixing it is considerably more entertaining. That explains a fair bit of what we make. Years of working with NGINX left me with configurations worth explaining properly. The book puts them to work, and the GitHub repository lets you get your hands on the examples. I ran two personal bests. Garmin recorded something else. After an absurd amount of experimentation with watches and treadmills, we built a free tool that lets you work with Garmin data through ChatGPT. At last, I could correct the bloody run. We keep finding useful software on GitHub. Rather than lose it in a pile of bookmarks, we organise the good finds into lists you can explore for yourself.
Nginx by Example

Garmin by Geekist
Geeky’s Lists
Follow the code.
Yes, there are two GitHub accounts. One is Geekist’s organisation. The other is my personal account, pipewrk. They serve different purposes, and both are very much alive. The organisation behind Geekist’s open-source products and tools. This is where the NGINX examples, Garmin work and the code associated with the site belong. My personal GitHub account. There’s years of engineering here, from Meteor and packages to the architecture rules that shape the way I build systems today.
theGeekist

pipewrk