Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]
1

Cycling Vermont

from Tom MacWright [alt+shift+b] in programming

In October I rode the Green Mountain Gravel Growler route in Vermont with a few close friends. It’s a route curated by bikepacking.com that consists of back roads, dirt roads, and single track trails. It wasn’t as blissfully car-free as the C&O Canal or the loop around Lake Konstanz that I rode earlier this year, but in exchange for sharing the road occasionally, we got loads of variety and beautiful hills to climb up and coast down. As the name implies, the route is structured around breweries. We only did half because vacation time is scarce, but still managed to hit some good ones. The first night’s, in Burlington, was Foam Brewers. I had the “Tally Mark” altbier, which tasted like a cigar, in a good way. We didn’t get much time to explore Burlington. We did see the world’s tallest filing cabinet. The first day of riding was from Burlington to Stowe, with stops at The Bidwell for food, The Tropic for a mid-ride drink, and ending at The Alchemist. About 50 miles, and 3,700 feet of climbing. Places like The Alchemist are impossibly nice: sunshine, babies and puppies crawling in the grass, happy people playing corn hole. The delirious happiness of finishing a long day in the saddle makes it all even more saturated and exuberant. I was feeling pretty good on the bike, most of the ergonomics were working. The only gear tweak that this trip will inspire is sticking to fancy cycling bibs (shorts): Ornot, to be specific, instead of trying to scrape by with the cheap stuff, which for me is The Black Bibs. The Alchemist’s “Heady Topper” is like drinking a flat white made out of hops. .up{display:grid;grid-template-columns:1fr 1fr 1fr;gap:10px;line-height:0} Weather was perfect for almost the entire trip, and the route was pretty clear and empty. We mostly encountered locals riding casually, casually passing us on the way up some big trail. Vermonters are strong riders. The second day would be about 44 miles of riding and well over 4,200 feet of elevation....
3 weeks ago

Stay updated

Get a weekly newsletter with the top 5 articles worth reading every week.

More from Tom MacWright

Recently

September was another big month for my life, mostly for me offline. Another good month for bicycle riding, seeing more of the trails on Randalls and Wards Islands. The New York area has taught me a few things about islands and one of them is that they're very fungible. On a map, Randalls and Wards Islands look one one island because they're "conjoined". They were conjoined on purpose: they used to be two, with a bridge and everything. But then in 1955 the government announced they wanted to join up the islands "by allowing private contractors to dump debris within Little Hell Gate for free" (!) Photo from From City of New York Department of Parks: 28 Years of Progress, scanned by Erica Fischer (!) CC BY SA 2.0 The opposite happened with Fire Island: it was one island for a while until 2012, and Hurricane Sandy broke it back into two. Photo from USGS, PD Dump trash to combine islands, dump water from the sky to divide them. That's just how life is. .two-up{display:grid;grid-template-columns:1fr 1fr;gap:10px} Listening I watched Magnolia this month and finally got the hype around Aimee Mann. It's a little frustrating that the songs from the film aren't on And a throwback: Dusty Springfield's version of When the Love Light Starts Shining Through His Eyes. Originally recorded by the Supremes and forgive me for highlighting the blue-eyed soul version of this song but it's so driving and urgent in a way that most of the other versions aren't, it's such a good slice of that very particular rushing rhythm of the era. Reading On a meta-level: I'm getting pulled back to Instapaper from Readeck, because I rely on offline reading so often and unfortunately the Readeck iOS offline mode is unreliable. It is open source and I should contribute and in all likelihood the issue will get fixed, but in the meantime I need something to look at on the subway. Reading: I enjoyed Spiral's launch post a lot, as well as turbopuffer's post about their refactoring. Database companies in the AI-adjacent space are a nice hybrid kind of reading, still concerned with architecture and a little more grounded than a lot of the "big idea" or marketing-centric stuff that I read from AI labs. I also liked Charles Broskoski's "Personal Business" essay (one of the are.na founders). And I've been really liking reading Work by Bud Smith. Review of that soon. Otherwise The end of October will be even more packed than September for me, so if I don't post, don't worry, I'm not dead, I'm partying.

1st Oct 2026 • 1 votes
Recently

I skipped August's Recently because this summer has been relentless, mostly in the positive sense. July and August were filled with bike rides, 5K races, friends in town, life changes and logistics. For a friend's birthday, we rode the rickety Coney Island Cyclone, which was faster and more intense than I remembered it. But it's been 18 years since the last injury on the coaster, and the rider was partly at fault: good enough for me. .two-up{display:grid;grid-template-columns:1fr 1fr;gap:10px} I rode my first proper randonneuring ride: 200km (124mi) to all of the beaches around Brooklyn. It was pretty challenging, as you'd expect, but I didn't 'find my limit' for endurance, but I did find my limit in terms of how many gels & ride-nutrition packets I could consume before sugar becomes repulsive. I do still heartily endorse maple syrup packets for ride nutrition: compared to the space-age fuels that all taste like fruit or coffee, it's an identifiable substance that tastes like you'd expect. And, not pictured, but I ran a bunch of 5Ks. Haven't hit my goal this year of going sub-20, but got close in the last one - 20:15. I'm not giving up yet, because the weather is getting better and Brooklyn has a lot of 5K options. Listening Hot Creek by Duffy x Uhlmann Duffy x Uhlmann has been in my rotation for a year now and the new album has all the things I like from the combination. This and Shrunken Elvis go along well together and both have been hits at dinner parties. This album from Frances Quinlan, the frontperson of Hop Along, went under the radar, but it's so good. I've also been playing Hop Along's send album Get Disowned. I really like everything that this band has put out. It's a product of Philadelphia but I hear some of the elements that drew me to DC post-punk in the turn-on-a-dime songwriting. Get Disowned by Hop Along Watching This video, 'The surprising truth about what motivates us', is kind of an artifact of the 'Obamaverse', as one of my friends would put it. It's by Daniel Pink, a writer-speaker-self-help kind of guy, and it's accompanied by one of those realtime hand-illustrations. There are lots of reasons to tune it out as YouTube filler. Still, I thought it was pretty cool for two reasons: first, it connected directly with Andrew Kelley's video, which is the next one. And it connects with my feelings about incentives and how most simple incentives are counterproductive. And second, the drawing is real. I'm so used to the artificial version of this visual style that it took a minutes to realize that the it wasn't AI or some 'drawing hand' style of video essay, it was a real person making quite nice illustrations: specifically Andrew Park. Found myself nodding along to every bit of this interview with Andrew Kelley. His values and motivation are so nice to encounter in this current phase of tech. He's kind of a role model, which is something that I used to find trite in my early career but I'm coming around to. As Adam Neely pointed out in his video, a lot of the people heavily using Suno (an AI music tool) could not cite any role models, and defaulted to a sort of enclosed, self-centered stance. I see this with engineering too: it's hard to discern what values or talents the people at 'the forefront of the industry' have that I want. Finding personal qualities as something to imitate instead of desires and possessions (cue the segue into Girard's Memetic theory) seems like a better way to live. Reading What strengthens a relationship? Almost always, it is personal investment. Perhaps an AI agent might be better at predicting what my father will want for his birthday than I am, but it definitionally cannot give him my time and consideration. Love is not just a feeling; it is a way of paying attention. Elizabeth Lopatto in The Verge picks apart Mark Zuckerberg's weird, sad view of humanity. It's worth a read even just for the incredible opening anecdote. Home of the titular 100 foot waves. Which existed when I was a kid of course, but the larger world didn’t know about them yet. They were our secret. My grandfather and I would walk to the lighthouse and watch the waves hitting against the cliffs and he’d tell me that these were the biggest waves in the world. I didn’t believe him, of course. I thought it was standard grandpa hyperbole. But I also didn’t want to believe that I was seeing the biggest of anything. Not yet. I wanted the really great things to be in the future. Something to aim for. Which means I missed out on some great things that were right in front of me. Mike Monteiro's newsletter is always beautiful and melancholy, and this is a really nice edition of it. I read and highlighted a few other articles but they were all saying things about AI, mostly about how it makes the world worse and makes people feel bad. I won't add those to the pile because I don't want that kind of content to dominate what I mention, even if it does dominate what I read. Elsewhere For the Val Town blog, I wrote about our experience with the bug bounty program. It's been a very interesting experience. Val Town has a pretty difficult security surface: in contrast to Mapbox, which was mostly a read-only API, it's a very read-write system with many access controls. At the center of the product is a sandbox that we want to keep secure. And because we're living in the AI age, a single bit of functionality can be exposed via REST API, React Router loaders, tRPC, and MCP. Building a model layer and a shared authorization layer - modeled after Oso - has helped a bit. But the reports still come in. It's pretty wild how AI factors into it: I'd say that 100% of the vulnerability reports used AI to write the report itself. From the best reporters, the vulnerabilities come with screen recordings and evidence, and it's clearly not all-robot. But - I suspect that other people manning help desks & bug bounty programs know this experience - it's jarring to go three replies into an email conversation with someone and they suddenly stop using an LLM to write their emails and the voice completely changes, from hyper-literate to abbreviated and misspelled. I also wrote about our new authentication scheme that makes vals require login and makes it possible to manage permissions to val applications, not just their code. It was pretty fun to implement, and the sixth or seventh time working with HMAC schemes I'm starting to get a natural grasp on them.

1st Sep 2026
Technology optimism hour

Back in 2022, I wrote Web technology optimism hour, highlighting the things I thought were cool about the state of technology. Time flies. Let's do it again. It's still easy to be pessimistic, but it's nice to mine your feelings for the positive ones. The elephant in the room is AI, but I don't feel like throwing another post into the gravity field of that topic. Without further adieu: TypeScript 7 It's here, finally, and it's faster. In the last edition, one of the headings was "Rust and Go based tools are making TypeScript development faster." At that point we had a few upstart projects for minifying, transpiling, and bundling TypeScript. Those tools have become standard-issue. But TypeScript, the actual type-checking of the language and the language tooling in editors, was still a bottleneck. There was exactly one implementation of the TypeScript type checker, and it was implemented in TypeScript, so it ran at JavaScript speeds and had limited ability to become multi-threaded. Unfortunately there's still only one game in town for TypeScript type checkers: it's still just Microsoft. But they rewrote TypeScript in Go for TypeScript 7 and it's much, much faster. This is one of the most noticeable changes to my day-to-day coding in a while. Plus, even better: TypeScript 7 supports the Language Server Protocol! As I wrote about in 2024, Microsoft invented TypeScript and also the Language Server Protocol, but TypeScript never implemented the Language Server Protocol. So there was no standard way for other editors, other than Microsoft's VS Code, to provide language tooling for TypeScript. This was suspicious behavior because of the company's history. But now: it just works. Neovim can support TypeScript 7 with its built-in Language Server support instead of someone wrapping the VSCode extension in an LS-protocol shell. So: a big win. Hooray for the new TypeScript: it's faster, it supports open standards, and now there are two TypeScript implementations. Now all we need is one that's made by someone who doesn't work at Microsoft. The Effect ecosystem is exciting I've been writing little development logs about Effect over the last year or two. I'm excited about Effect. It's a big, all-encompassing system, but I think it has a lot of potential and is arriving at exactly the right time. This is an era of supply-chain risk and I think there is, and should be, a swing away from the tiny module ecosystems in NPM. Software that's composed of hundreds of little modules from hundreds of authors is a lovely idea that doesn't work with malicious actors. The swing is toward larger, buttoned-up libraries, and Effect is really well-positioned for that. It has type validation, observability, state management, fancy data types, and lots of functional programming helpers all under one roof, in one package that's pretty well-maintained and heavily tested. It's also very, very typed, which makes it safer to use at scale. And it makes limits a lot easier: you can just stick an Effect.timeout on anything and prevent network requests or database queries or anything else from taking too long. The same with concurrency, it's very easy to limit concurrency. It's ready for a very uncertain world where you have to validate and be careful about everything. But at the same time, it's fun to use, if you're that kind of person, which I am. Bluesky and Mastodon are successful, meaningfully decentralized systems I use Bluesky and Mastodon all the time and both just work. They don't feel like tech demos, it's not all nerds using them. The uptime is pretty good, the featureset doesn't seem limited by the technology choices. And yet both are legitimately decentralized (in different ways) networks, with really interesting ideas about security, privacy, and community systems. Bluesky is aggressively building out its protocol as an independent technology from the social network, and as I learned at their conference, there are lots of creative people building on the technology. There's a big gap between a cool tech demo and a user-friendly popular service, and both of these have bridged it. It's exciting, and shows that you don't have to accept a bad set of tradeoffs to make tech that's both principled and popular. Signal, WhatsApp, iMessage, and RCS are meaningfully secure messaging platforms I want to just celebrate the end of a technology: SMS. It's so good that people don't use SMS anymore: it was needlessly expensive and extremely insecure. My texts with friends are almost exclusively on Signal & iMessage, and occasionally WhatsApp. Now, WhatsApp is a mixed bag and nothing's perfect, but it's cool that the secure options recommended by the EFF and other sources are also popular options that people use every day. That's also pretty important from a privacy standard: having Signal installed on your phone is normal because it has a wide userbase, but the same would not be true if it was only used by people attending protests and being wary of government surveillance. Hardware update cycles are slowing People are hanging on to their phones and computers for longer. I'm part of this trend - my iPhone hit its fourth birthday, and I have no reason to even think about replacing this computer. With the exception of their batteries, modern laptops and phones are robust: they're water-resistant, made of durable materials, and basically just work. You could read the same data differently: maybe people are upgrading slower because they have less disposable income. I'm not sure that's true. But either way, it's good that upgrade cycles are longer: it means less e-waste, less pollution, less churn overall.

14th Aug 2026 • 1 votes
Recently

June was a big month: I went to Porto & Lisbon, and had a lot of life stuff happen. I'll get into the trip once I get my rolls of film developed. Three rolls at a new photo developing place: fingers crossed! Reading I finished reading Intermezzo (of the bag) and it was fantastic. I've always liked Sally Rooney's books but this was the one where the writing style really clicked. Also, The Vegan. Meh. I read Patricia Lockwood's 'A Tradcath Wedding' via Perfect Sentences but found an additional sentence to be perfect: Whenever they rang the chimes, which seemed to be every four seconds or so, a toddler screamed ‘WOW A BELL!’ to the visible displeasure of the celebrants – though isn’t the entire point of the ritual that you’re supposed to be that awestruck every time? Patricia Lockwood is the funniest writer I've read. You cannot grow a pumpkin, but you can improve the odds. Taylor's 'You Cannot Grow a Pumpkin' is a fantastic little prose poem of sorts. Watching I'm always trying to find a 'romp' when it comes to movies. Something lighthearted, pretty easy to watch, so on. We watched The Pink Panther this month and it is a perfect example of the genre. The inspiration for the watch came from the hamburger scene: But there's so much more of this kind of thing in the movie, little bits and physical comedy. Oh, and I also watched The Departed, which everyone says is good and is good. Elsewhere I wrote Accidental Anonymity on the micro blog, and it stirred up some discussion on Bluesky as well as at least one blog response. It was kind of an angry piece, as I said at the start. I will keep trying to stay out of the trap of writing about that topic all the time. Listening The only album I bought this month was Songs of Her's by Her's, which is fine. I wish I had something more profound to say about it given how the band met an unbelievably tragic end. Maybe more influential than that was Know Your Enemy's recent podcasts, especially this one about the pope's encyclical. I've really grown to love that podcast, and it has been part of me intellectually reconnecting with, but not readopting, Catholicism. Art Here's some art I really liked this month: This Hockney piece called 'Picture Emphasizing Stillness' from 1962 was at the MAC/CCB museum in Lisbon. Via Tim Babb, I enjoyed finding Tomás Sánchez's work.

1st Jul 2026 • 1 votes

More in programming

AI Homelab Part 4: Lowering the floor for Scout

Helping Scout focus and remember

11 hours ago • 2 votes
The Explorer Pattern for product invention and development.

tl;dr: the Explorer Pattern is one individual or team building a functional implementation that minimizes cross-team and cross-functional impacts as much as humanly possible, and then reconciling the details with other teams after that prototype is completed, accepting that this approach can require very substantial rework to that initial development. Why write this? Imprint previously called this the “Tech-led” or “Engineering-led” development model, but it’s pretty unclear to folks what that means. This writeup provides a more defined term, the “Explorer Pattern”, and explains in more detail how this works. Why do we need to adjust the way we work? Before 2026: Code is expensive, and we design process to minimize implementation and rework In and after 2026: Writing software is extremely cheap, but it’s a wider phenomenon: generating output is effectively-free across many dimensions. Code is nearly free — if we have appropriate constraints. Designs are nearly free — if they follow patterns. Analysis is nearly free — if we’ve instrumented things properly Reworking software is extremely cheap. Historically industry has optimized around avoiding engineering rework because engineering was the highest cost / narrowest constraint. In many companies this was interpreted as writing code being the constraint, which was never true, but many common practices were designed as if that were true (e.g. bringing engineering into problem-solving late “to protect their time”) Working on the system is much more effective than historically if we get automated integration and feedback loops right, e.g. not improving a one-off design but improving the design system. Any place where improving the higher-leverage process is slower than solving the one-off is a bug in our process Explorer Pattern: primary-and-replicas metaphor The easiest metaphor to think about the Explorer Pattern is database replication. Databases like MySQL and PostgreSQL have a primary database, where writes are performed. Every write is verified at that point, and once it’s verified, you know that the writes will flow downstream to various secondary replicas. Those downstream replicas can be delayed but they can’t be wrong because writes are verified upstream. (I’ve resisted the desire to talk about the CAP theorem.) A different model for database design is that used by Dynamo or Cassandra (or MongoDB to a certain extent), where you have a replica set, and have to get an acknowledgement from the majority of the replica set for a write to be strongly consistent. This is a very reliable setup, because it means you can tolerate losing a node, but it also introduces inconsistencies, and on a fixed amount of hardware they tend to be much, much slower than running a primary-secondary setup (or rely on bad performance metrics that don’t fsync to disk to create the illusion of throughput). The Explorer Pattern is the former primary-secondary model, where the vast majority of the work is done by the working individual or team. This makes all work internally consistent because it’s passed through the same small group. It doesn’t, however, mean that the work is perfect. For example, you can always insert data that meets the table’s requirements but is still inherently wrong (e.g. 200 is a valid integer, but it doesn’t mean that my credit limit was supposed to be 200, that depends on the surrounding application logic). Other teams become aware of the changes downstream, not synchronously upfront, and it’s instead the working group’s responsibility to both rationalize approach and create visibility into their work for other teams to engage in a non-blocking fashion. Example: Support for Financial Aggregators A concrete example of this practice at Imprint was rolling out financial aggregator support, e.g. allowing folks to connect to their Imprint powered accounts via Plaid. This has always been something folks want, but it’s particularly important in the realm of agentic commerce where more folks’ agents are analyzing their financial state for them. For this project, one of our engineering leaders (Ron), built the first pass of the feature at a low-burn while understanding the shape of the problem in a private alpha. He chatted through some of the details periodically to keep other teams aware, but it was a bit of a side project. However, once he found the full shape of the problem and had implemented a full solution, we cut the replica-lag across teams down to near-zero, identified and ran through the small number of remaining issues, and shipped it. Like many of our projects this year, it was never officially on a roadmap, and shipped a quality feature that our members have wanted for some time. How to follow the Explorer pattern The rough rules for following the Explorer pattern: Know your goal and sponsor: every initiative ultimately has to have a specific outcome it’s pursuing and a sponsor who’s bankrolling that pursuit. This doesn’t always need to be explicit, especially for smaller projects, but once a project goes beyond ~3 weeks of effort, if you can’t very explicitly identify who the stakeholder is sponsoring your project and they would not enthusiastically agree, then you are likely closer to “lost” than “exploring” Small working group is small: at most 5 people, and preferably smaller. Everyone in the group has to keep the entire project in their head for as long as possible to detect problems and opportunities Small working group is flexible: folks in small working groups have to “find a way to yes” rather than “find a way to no”. Exploring is about uncovering the fundamental shape of a problem rather than pretending we know the fundamental shape Publish progress in a public channel: explorers have to report home with the progress they are making so others are aware. This is both a Linear Project and a Slack channel. Make the narrowest viable changes to what already exists: when we introduce unnecessary changes, we invalidate others’ mental models about how the world works. When we haven’t made those changes with care, we’re not only invalidating others’ mental model, we are creating the expectation that we’ve done it very intentionally for a good reason, which has a chilling effect on others improving them later, which is very expensive, whereas the Explorer pattern depends on being as inexpensive as possible Exercise good judgment to identify reasonable hypotheses: discard bad ideas immediately, and then filter the rest by trying to implement them as quickly as possible. Once you see the shape of the implementation, you can figure out which of the remainders are interesting Hold assumptions constant to avoid getting stuck: the only way to navigate complex ambiguous problems is to hold things constant, even when you know they are imperfect. For example, to do headcount planning we have to know our revenue, to know our revenue we have to forecast it, to forecast it we have to know the day that partners will go live next year. We don’t truly know any of those things, so just anchoring on a plausible guess to unblock us is much more valuable than trying to get them accurate. A little prework is useful, but a lot is just artificial precision that’s a distraction from progress Hold space for being totally wrong: when we move fast, with low information, we always find the way out, but often it’s not the way out we anticipated when we got started. Being open to throwing it all away, and starting a second, third, fourth time Ship all the way to production behind a feature flag: features and products move fast when we get the pieces working every step from frontend to backend to data pulls. This is the first step of exploration. Just make sure it’s behind a feature flag that’s only enabled for internal folks!

14 hours ago • 2 votes
Value Creation vs Job Preservation

Comparing two different ways of work and working environments.

yesterday • 2 votes
Making a dumb TV just smart enough

I own an old, cheap TV. It has no Internet connection, no fancy smart features that make you want to install a Pi-hole, and no ask-me-again-later updates. However, it is connected to my own desktop computer through an HDMI cable, so I can watch movies and TV series from the couch. Setting it up used […] The post Making a dumb TV just smart enough appeared first on Quentin Santos.

3 days ago • 1 votes
Bikepacking across Kyushu

Five days and 540km on a bike across Kyushu, without a laptop. Notes on the peace of riding all day, convenience store dinners, and Japan's emptying countryside.

5 days ago • 1 votes
📚 BoredReading

You seem to be enjoying this.

Join free to unlock everything.

Create free account

Already have an account? Sign in