Mechanical watches

Every now and again, I decide to look into a field of interest — like home networking, or mechanical keyboards, or meditation — and after the first web search or two, I discover communities far larger and more deeply devoted to the pursuit of the subject than I would have thought possible. I stumble into the subreddits with their jargon, their memes, their local "zeitgeists"; I discover the YouTube influencers I’d never heard of before but which have 3 million subscribers each; I see the uncountable listicles of "Top 10 X’s in some subspeciality Y (2025 edition)". I’m always surprised at the scale and depth of activity, and often a bit scared, but at the same time a little bit awed.

This has happened most recently for me for the topic of mechanical watches. It occurred to me that my practice of using my mobile phone as a timepiece was getting under my skin — because it meant that I often got distracted by notifications when all I wanted to do was see the time — and that wearing a watch would eliminate my single most frequent reason for pulling my phone out of my pocket. This is somewhat of a reversal of my previous position that concentrating the maximum number of functions into the smallest possible number of devices was an embodiment of minimalism and simplicity. It turns out that it’s perhaps not that easy. I began to wonder if maybe consolidation isn’t always the answer, and that simplicity might sometimes best be found in simple objects that do one thing alone. Not so much the "Internet of Things" as "Things Without Internet".

So I innocently typed "mechanical watch for men 2025", expecting to get to the bottom of the matter after an hour or two’s investigation. Sweet summer child. Little did I know that when I peeked behind that door I’d find one of those larger-than-I-could-have-imagined internet communities with all of the hallmarks of one of those communities of belonging in which people take the hobby to an extreme, constructing an identity around being "watch nerds" and collectors, and shelling out gobsmacking amounts of cash to acquire these intricate machines, sometimes in a multiplicity that no two-wristed mammal could realistically expect to make sufficient use of in any reasonable way.

The first thing I discovered was that there aren’t just "mechanical watches", but "field watches", "dive watches", "tool watches", "pilot watches", "engineer watches", "racing watches", "dress watches", and countless other genres. There are titans, luxury brands, value brands, micro brands. Every possible axis of decision-making is populated by a range of options from the obscure to the mainstream, from the traditional to the avant garde, and from the economical to the ostentatious. Even after my relatively elementary excursions into the subject, I could probably already put together many thousands of words talking about all the choices one has to make to whittle it down to the watch type, feature set, price range, brand, and so on, to the point where you can actually pull the trigger and make a selection.

But that’s not my goal here. I just wanted to say that after all this, I don’t think there is a perfect watch. All there is is a series of compromises that can eventually lead you to a choice that feels right enough. At this point, after about 5 or so hours of research, I have looked at hundreds of watches and developed enough of a sensibility for things I like and do not like to know what I want.

In short:

  • Given that this is all partly motivated as an act of rebellion against our big tech overlords, I was initially thinking that I just wanted a simple mechanical watch (ie. a watch you wind manually), not an automatic (self-winding) one. I figured the ritual of winding the watch every day or two might make we feel some kind of edifying sense of connection with the real, tactile, non-digital world; that it would be a kind of meditative act. But I found that as I searched for watches that matched my desiderata (below) I simply found way more automatic options than mechanical ones. Out of sheer pragmatism then, I decided to fish where the schools were swimming, and I opened my mind to buying an automatic watch if that was the one that best checked all my other boxes.
  • I want what folks call a "one and one" and a "daily driver". Those are actually two subtly different things, albeit closely related ones, so let’s talk about them separately. First, by "one and done", I mean I only want one watch. I don’t want to start a collection. I want to buy something good enough that I won’t find myself angling for an upgrade soon after buying it. But neither do I want to break the bank buying something extravagant before I’m even sure that I’ll truly commit to wearing the thing every day (after not having worn a watch for most of my adult life). I need it to be versatile enough that I can use it for everything. This is where the objective starts to blend with that of "daily driver". Versatility means something casual enough to wear with a pair of shorts or jeans, but also compatible with an office environment or a formal one (relatively rare for me, but I do sometimes need to dress up). That in turn means a bunch of other things, like not being too bulky (or too small — it has to be in the "Goldilocks" zone), not being too heavy, but also being robust.
  • I don’t want something ostentatious or luxurious; both of those just sound like recipes for spending more money than you need to. I’m not drawn to big brands — in fact, I feel somewhat of a revulsion to them — although I do appreciate quality. I have no interest in owning a Rolex, nor indeed any of the even-more-expensive brands that you could describe as "something that rich people buy, not because it’s better quality or more functional, but because it signifies that the buyer is rich". When I look at those, I don’t think "I wish I could afford that", but rather, "Yuck!". So, my goal is to find something that is good value for money, but keeping the price down isn’t my primary motivation; it something to be balanced against other objectives.
  • So, to recap a theme that is developing over the last few points, I want a watch that I can use all the time without having to worry about it getting damaged or stolen; it should be durable and not too expensive. I want this thing to be good enough to last a lifetime or at least a sizeable chunk of it, but it need not become a family heirloom.
  • I don’t want it to have any "bling" too it (ie. no shiny metals), I prefer it to have a matte finish or a brushed metal look (it really has to be metal so that it can straddle the divide between casual and formal). I prefer a black face because that is going to pair well with more contexts (clothing, environment etc). I’m not really interested in having a "dress watch", but I want something that looks respectable enough to use in dressy situations. I like watches that look a bit masculine, but not absurdly so (chunky things that look undecided about whether they’re timepieces or tanks).
  • Aesthetically, I value simple, utilitarian design. I don’t need bells and whistles. I don’t need a diving bezel, I don’t need UTC or word clocks, nor a chronometer. About the farthest I’d go in the direction of "complications" if you can even call it that, would be a date window. My eyes aren’t getting any better, so I want a simple face without anything "busy" on it. And in terms of branding I want something that doesn’t scream out the name of its manufacturer; I want something subtle and discreet.
  • These requirements push me into the realm of "field watches" and their neighbors. The watches that have resonated the most with me so far tend to be described as "tool watches", sometimes "field watches", or "pilot watches". There are some watches that inhabit spaces near enough to multiple categories that they wind up making it into more than one "top list" for different categories.
  • As much as one might want to come up with a mathematical formula for ranking all the options against one another, there is a huge subjective element to this. Once I’ve ruled out a bunch of watches because they clearly don’t meet requirements, I am left with many (dozens) that come close (albeit none perfectly hit the bullseye). So, the rest comes down to intuition and subjective preference. Many you can drop down the list because they don’t "spark joy". It might be a question of proportions, or a curve, or the font used in a logo or a numeral. Conversely, something else is going to rise to the top of the list simply because it "feels" somehow right.
  • I love watches which show off the movement via a transparent back cover, but I recognize that’s just a whimsical and emotional thing, and I know that my other criteria (about ruggedness and simplicity etc) bring me into territory where many of the options I’m looking at don’t have this feature; it’s definitely a "nice to have" and nothing more. If I choose a watch that doesn’t have it because it’s the way to obtain all the other things I’m looking for, then so be it. Similar to the "wanted mechanical, but will end up with automatic" situation I described above, what we have here is "would have loved a visible movement, but am not going to get one" scenario.
  • How much to spend? Given that you can find watches for anywhere between, say, 50€ and 50,000€ (or even more, but I’m talking about the kinds of watches you can at least see in online stores, not the kinds of limited edition or rare specimens that you can only find at auction) you need to have some way of setting a budget. The fact that I want a "one and done" watch tends to exercise an upwards pressure on the price I’d need to pay, because I don’t want to buy something cheap only to regret it soon after. But my level of inexperience must exercise a countervailing, downwards pressure; I don’t want to blow a wad of cash on something only to experience buyers remorse. This is very context dependent, but as a rule of thumb, say that you’re living below you means (ie. not living paycheck-to-paycheck, but able to save some percentage of your earnings every month), then you should be able to define a threshold in terms of your income. For example, if you are living modestly with no debt and rarely spend on "discretionary" material goods, then you might be a able to set a guideline like "half a month’s salary" (as of 2025, the average monthly net salary in Spain is about 1,800€, so that would be 900€). Depending on your psychology and your personal circumstances you might be able to push higher, or need to go lower. Me personally, where I am right now, I feel at peace with the idea of spending about a quarter of my monthly salary (ie. one week) to get this watch. That’s enough to get something nice, but it keeps me far away from anything which might be considered extravagant.
  • Finally, I’ll say that I’m not interested in "microbrands". I don’t care about being the only guy in the office to have some rare thing from a startup that only other watch nerds have heard of. It just doesn’t matter how cool it is. I’d much rather buy something from a company that operates in many countries all over the world, so I can get this thing repaired or serviced when it needs it, and ideally a company that has been established for many decades, so that I can be relatively confident that it will still be around when both me and my watch are old and need some extra love and care.

So, I think I’ve engaged in enough research now, commensurate with the level of outlay I’m going to incur. Once I’ve actually followed through and gotten the watch I may have more to say here about exactly what I choose and whether I stand by the decision process outlined above.

Rate my setup

For the first time since forever I’m actually happy with my current desk setup, so I thought I’d go back and look for some photos of older setups and rate them.

2010 edition

On display we have an iMac "Core i5" 2.66 27" (Late 2009), some Harman Kardon SoundSticks, an Apple keyboard, and a LaCie external drive sitting on a glass IKEA desktop and a crappy plastic chair. Amusingly, the LaCie is sitting on a foam block to dampen the noise caused by the vibrations from the spinning HDD platters. A Blue Snowball mic can be spotted sitting up on a shelf above the desk.

2011 edition

Start-up life, part 1. The Apple keyboard is now accompanied by a "Magic" Trackpad, and we see a MacBook Air next to a decidedly-not-4K Dell monitor (to which is taped a picture of a US keyboard layout because my brain was trying to recover after being rewired when using Spanish layout keyboards). In a minor concession to ergonomics, the monitor is raised close to a suitable height by sitting on a ream of paper, but it’s not centered in front of the keyboard, something I’d never tolerate now.

Part 2. The start-up life intensifies, with an Aeron chair and a crankable standing desk (horridly unsafe, BTW, with a bespoke mechanism). The LaCie has again joined me on the desk, but this time without the foam dampening block. In typical VC-funded bubble fashion, I’ve gone from a single ream of paper to six whole reams, significantly improving the ergonomics of the setup by center-aligning the monitor and elevating the laptop (that’s what the two reams on the right are for).

2015 edition

Fast-forward to 2015 and I just moved into this fancy building at FB along with the rest of Product Infrastructure. You get a standing desk! And you get a standing desk! You get a standing desk! Also, an "ergo consult" where they give you a real laptop stand and make sure your keyboard (now a Realforce) and display are at the right height. Some kind of Apple Monitor — I don’t remember exactly which — but at that time it wasn’t a 4K or Retina one. Some fun details in there, if you look closely, like a React logo leant casually against a desk, a glimpse of the corner of Zuck’s "Acquarium" office in the background, and Joe Savona intently ripping through some some god-level-hard problem, as is his wont.

2020 edition

One pandemic later, working from home — at the kitchen table, no less — in another country. The keyboard is the same, but everything else is different. A new employer, new headphones, a shitty 5€ mouse (not even cordless), and an unfortunate new era of Apple laptops without ports (see the dongle) but with horrible butterfly switch keyboards and useless "Touch Bars".

2021 edition

Still working from home, but now from the living room, and another employer. We’re still afflicted with a cursed Touch Bar, but we have awesome Apple Silicon now. Note that the "upgrade"[1] from the kitchen table to a dedicated but non-adjustable standing desk requires an ingenious new laptop stand[2] while I send my intermittently faulty monitor away for warranty repair or replacement.

2023 edition

Better view of the same desk. Ignore the cardboard boxes (this was a moving day). Not too much has changed at this point, but I have acquired a few accessories, like a "Blue Yeti" mic and mount, and an Elgato ring light: both of those were principally chosen on the not-so-sound basis of being actually available (things got scarce in the pandemic), and I wanted to put my employer’s "home office" budget to use. Also visible: new headphones, better in many ways, and my trusty Linux desktop.

2025 edition

I’m not quite ready to show this yet, but I think I’m actually happy with my setup for the first time since basically forever. I’ve still got the ridiculous ring light, but that’s about the only thing that’s out of place any more. I now have an adjustable desk! I actually have a chair! I got rid of the rather mediocre Blue mic and upgraded to a nicer Røde one. I replaced my 4K monitor with a 5K one (a Retina-ish external display, finally). New headphones[3], courtesy of my employer. I even have a desk mat now to put the keyboard and trackpad. Not sharing a photo at this time because of one small problem: it’s in the corner of the living room and I don’t really have a good angle on it.


  1. "Upgrade" in quotes because it was a horrible, low quality thing made out of the cheapest, warped wood. I got it because it was the just pleasing enough, aesthetically speaking, that I could hope to put in the living room without becoming the most unpopular member of the household. In the end, I think I did become the most unpopular member anyway, but that’s all water under the bridge now. ↩︎

  2. Don’t judge me for my taste in books. My then-employer gave me a learning budget every year, and I ended up buying a ton of books. The ones in the photo were just the ones that happened to be the right height for my needs. ↩︎

  3. To be honest, I am not sure which QuietComfort model I’ve got, but whichever one it is, the sound is great and the UX is good too. ↩︎

Git forges

GitHub’s CEO just announced his resignation and the internet is roiling with lamentations of how GitHub is going to turn to AI-infested shit now that Microsoft has fully taken over (they won’t be backfilling the CEO position[1] but will rather have leadership report directly to MSFT execs). Don’t labor under that misapprehension. Lore has it that Dohmke came to MSFT via an acquisition, as did the previous CEO, Nat Friedman. When Nat took over, he managed to evince some of the hipster vibes from the early days when GitHub was cool[2], but Dohmke charted another course, very much channeling MSFT leadership from the moment he took over, enthusiastically taking it upon himself to — and I quote from his personal mission statement — "boost the actual fuck out of all things AI". If his farewell post and recent other writings are anything to go by, nothing is going to change about that.

Might Microsoft end up doing a Skype here and shutting down its multi-billion dollar acquisition scant years after the purchase? I don’t think so. Microsoft’s lifeblood is developer goodwill: they want to be seen as a developer platform, and it’s going to take a lot more than an AI singularity to change that. So, I’m not worried about GitHub getting shut down. At least, not for the foreseeable future (where "foreseeable" is defined as "during the next 2 to 3 years").

I am, nevertheless, worried that GitHub is going to continue going all-in on AI, and I think that’s a mistake. By all means, they should integrate with AI from other vendors, and even from within MSFT itself, but not to the exclusion of building something that is actually a useful Git forge. AI is not GitHub’s core competency. They are uniquely positioned, however, to build the best code hosting and code review platform for all the worlds’ developers: at least, they would be if they were interested in doing so. Historical evidence suggests that they aren’t.

I’m not the only person who thinks this way, and that’s why you’re now hearing rumblings of discontent. If you’ve been listening, the rumblings have been going on for a while now, most noticeably beginning when MS acquired GitHub in the first place. Here’s a representative example from 2024: well after the MS acquisition, but before Dohmke’s resignation.

I myself only have a presence on GitHub for two reasons. Firstly, because it’s where all the eyeballs are. This fact corresponds to a network effect that has driven a huge amount of developer tooling and practices to be created around the assumption that all code that matters is available on GitHub. The second reason is that, as a distributed VCS, Git makes it easier to push to any given Git forge without having to fully align with an evil corporation: you can very easily push your source code to multiple Git hosts. For me, the only real "vendor lock-in" I have to worry about is the set-up I’ve added to some of my repos for running CI using GitHub actions. By definition, this is nice-to-have functionality that I could live without if forced to do so, and there are alternatives out there if push comes to shove and I have to move.

So, for me, for quite a few years now, I’ve thought of GitHub as but one mirror among several, albeit it happens to be the defacto standard location that people are going to go to first if they’re looking for something; so, in my project READMEs, I end up listing GitHub first.

But I keep my eye on the competition. GitLab, sadly, seems to be nothing more than a GitHub clone. Codeberg is based on Forgejo, itself a fork of Gitea, which pretty unashamedly sets out to copy everything about GitHub right down to the look and feel. Sourchut is a refreshing minimalist and anti-AI take on what a code forge should look like, eschewing forks and pull requests in favor of email-based workflows (which unfortunately raises the barrier to participation a little bit compared to the lowest common denominator approach of GitHub).

I used Phabricator[3] when I worked at Facebook, and I sorely miss its stack-based review flow, even though I hated using Mercurial. I also rolled out and used Gerrit[4] at a previous job, and it was powerful but not as full-featured as Phabricator (or GitHub, for that matter); that is, it was designed to make code review great, but if you needed anything like an integrated issue tracker or repo browser you were out of luck. Graphite probably deserves a mention here: hopefully not too uncharitably, I’d describe it as an attempt to graft Phabricator features onto a GitHub-centered workflow made by ex-FB/ex-Meta engineers who missed being able to use Phab and were tired of waiting for GitHub to implement stacked-based review flows; it’s a VC-funded startup, though, which means they are of course trying to cram in AI features, and the fact that it’s built to work on top of GitHub means that it will always be hampered by the limitations of the underlying platform. Fun fact: Dohmke invested in Graphite[5] when he was GitHub CEO, ironically doing what he never saw fit to do with the company he was actually running (that is, invest in building good code review tooling).

Here’s a little story I don’t think I’ve told publicly before, although I think I’ve probably alluded to it on Twitter, but when I joined GitHub one of my principal motivations was to bring great, Phabricator-quality code review to Pull Requests. I spent a couple of years trying to do that, and failed.

I spilled veritable rivers of ink trying to explain to people what made Phabricator great. I made presentations. I collected testimonials. I demonstrated workflows. I was careful to not make it all about Phabricator though. Having seen amazing code review on the Git mailing list, and having used Gerrit extensively before that, I drew on examples from different sources trying to pull together the common elements that showed how different code review could be when done well. I recruited the assistance of ex-Googler’s who had used Google’s internal code review platform (called Critique), to argue the virtues of stacked workflows.

I was fortunate to have the support of my immediate manager, who carved out the space we needed to do a week-long "Hack House" where a small strike team assembled to sort out the details of what this could look like and build a demo. When we shared the demo, I was told by a Senior Director that it was the best demo he had ever seen at GitHub. This bought me the space I needed to produce a series of design documents, tallying to several tens of thousands of words, explaining how this could all work and how we would get there. When I said "rivers of ink", I wasn’t exaggerating.

And the end result? Well, you can[6] see it when you go to GitHub today. Most of the engineering team is trying to cram AI features into the platform, and the rest of it is working to keep the site up, and only mostly succeeding[7]. On the fringes, you have teams rebuilding things in React in the name of replacing legacy technology, giving them a fresh chance to build something with better accessibility and performance; sometimes they actually achieve these accessibility goals, but the performance ones are a bit harder to come by, and there’s the constant dance with the subtleties of reinventing wheels[8] that the browser supported just fine on its own when pages were mostly server-rendered HTML.

In the end, I had to desist. I got pulled into the swathe of the engineering org that was engaged in permanent availability work, stumbling from crisis to crisis trying to get ahead of the next outage before it happened. Meanwhile I continued to update my code review design documents with supporting evidence whenever it appeared, but I could tell that there wasn’t the will within the leadership chain to take on any big bets in the product roadmap unless they had "Copilot" in the name.

So, it’s on my bucket list to build the code review tool that I would want GitHub to be. I wouldn’t actually want to displace GitHub in the market, of course, because if I did, I would immediately have to change my job title to "Chief Scaling Officer"[9] and forget about building the thing that I actually care about, which is a code review tool: a code review tool for humans. (Yeah, I’m old-fashioned in that way, and I’m willingly giving in to nostalgia: I still care about giving tools for humans to do this particular job, and I find the idea of delegating both the writing and reading of code to LLMs to be one of the least inspiring things in the world[10].) But yeah, I’d love to build a Git forge, even though it might have to wait until my retirement because I’m rather busy right now[11]. I don’t know if anybody but me would use it, but it sure would feel good just using it myself.


  1. A harsher soul than I might note that this qualifies the outgoing CEO as literally the opposite of "indispensable". ↩︎

  2. Which in turn was because it was built with Rails, and Rails was cool. ↩︎

  3. See also this Wikipedia article about Phabricator as well, in case the Phabricator site ever goes away, which is a distinct possibility now that the project is no longer actively developed (although a fork in the form of Phorge does exist). ↩︎

  4. To see it in action, look at Gerrit’s own Gerrit instance. ↩︎

  5. You can see him listed among Graphite’s "angel investors" here. Noticeable on the list are a fair few ex-FB/ex-Meta folks. ↩︎

  6. That is, you can’t see it, because we never built any of it. ↩︎

  7. GitHub has long been a victim of its own success in this regard: when you’re the most popular Git host, you have no choice but to build a massive team whose sole purpose is to scale Git storage. ↩︎

  8. Things like scrolling, and find-in-page. ↩︎

  9. The hard part about being the most popular Git forge isn’t the horizontal scaling you have to do to support lots of users; it’s the extreme engineering you have to do to support the outlier customers in the 99.9th percentile. These customers aren’t just going to have large monorepos with millions of files and even more commits, but they’re going to do things like have 100,000 open PRs (all of which need to be rechecked — even if only lazily — for mergeability when the target branch updates), or a million branches, and they might be merging and rebasing hundreds or even thousands of PRs per hour. People working on or adjacent to infrastructure at GitHub knew the database IDs of these p99.9 repos by heart because they’d seen them come up so many times when doing incident response or performance degradation analysis. ↩︎

  10. Although, as a pragmatist, I try and extract as much value from LLMs as I can in my daily work. It’s just that I don’t enjoy doing it. ↩︎

  11. Another fun fact: I actually already did build a repository browser once, back when my website used to be a Rails app. The repo browser is the easy bit, of course, but still. If you’re curious, the simplest way to see what it contained would be to look at the commit where I deleted it. The grand irony here is that GitHub’s React-based repo browser struggles a bit to render that commit, because it changes 75 files and a few thousand lines… The old version which was just server-rendered (Rails-rendered) HTML did it better. ↩︎