HNHacker News
TopNewBestAskShowJobs

mikepurvis

13,612 karma · joined October 27, 2009

Mechatronics engineering grad at University of Waterloo. I've led teams and shipped products— hardware and software. Areas of interest include DevOps and DX, tools, pipelines, and packaging. Experience in Nix and Debian primarily, increasingly GHA, TypeScript, and Docker Buildx Bake. Clearpath Robotics / OTTO Motors alum, now at Simbe Robotics.

All opinions expressed are entirely my own.

https://www.linkedin.com/in/mike-purvis-6166a42/

https://meet.hn/city/ca-Kitchener

submissionscomments
mikepurvis··on How does IKEA come up with names for its products?
Exactly the right amount of chaos, particular given that the Brimnes "series" encompasses a pretty wide range of configurations and form factors:

https://www.ikea.com/ca/en/cat/brimnes-series-700496/

mikepurvis··on Beware Management Consultants
Interestingly the "dark ages" subpage is not linked from the parent page: https://about.iceland.co.uk/our-story/
mikepurvis··on How Bluesky draws its logo on screenshots
I've noticed similar things with off-road biking as well. Hydrocut generally does an okay job of snapping to the trails there since Google knows about them, but I was at Rondeau this weekend, and Google kept insisting I was on the adjacent Lakeshore Rd rather than the Harrison trail [1] that I was actually on. And this had real consequences because my youngest and I had become separated from the rest of our group and were trying to use a "share my location" through Signal, but the Android system-supplied location used was the one that had been unhelpfully snapped to the road.

[1]: https://www.alltrails.com/trail/canada/ontario/harrison-trai...

mikepurvis··on How Bluesky draws its logo on screenshots
I think that's actually a separate issue. What I specifically want from a Google Maps share URL is for it to be something I can send over text that will reproduce for my recipient exactly what I see.

A lat/lon/zoom/start?/dest? is kind of what a Google Maps share currently is, but it's neither an interoperable standard nor a reliable capture of the current state, so really the worst of both worlds.

(Also, hi AB! Nice to see you on here)

mikepurvis··on How Bluesky draws its logo on screenshots
I would happily use the Google Maps "share" feature, but I've yet to encounter any but the simplest of scenarios where it actually preserves the entire context of what I'm trying to share: the viewport, the start and destination, stops along the way, route choice, the time of day, all of it.

If I'm sending a screenshot it's because I want to send exactly what I see on my screen and not have my recipient's gmaps instance happily recompute a route it thinks is better or leave out the routing information I included, or switch from biking to driving directions, or whatever else.

mikepurvis··on How Compaction Works in Pi
I'm very interested in this too. I feel like when my Claude session compacts I immediately have to re-alert it to critical aspects of the task, but it should be possible even to have a secondary low-skill agent crawl over the whole context window semi-continuously and nominate pieces for removal or summarization. Or at a higher level, have something able to decompose, like hey I realised we're actually working on three distinct aspects of this problem, let's split the context into those three and I'll just retain a high level summary of what's in the other ones, enough to know if I should pass off control to one of the others for a particular ask.

I feel like this is kind of subagents, but it doesn't have the clear task -> work -> return result -> die model, rather it's more closely aligned to how I myself multitask, maintaining several long-lived threads of execution, and having to intentionally "forget" about the other ones when it's time to lock in and do real work on the most important one.

mikepurvis··on Gemini 3.7 Flash
I'm curious how much people are manually curating context these days; I'm increasingly feeling for myself that it being auto-managed inside a front-end like claude code is not ideal, and I'd rather have more control over what exact files and pieces of discovery go into a particular prompt, and the ability to more easily "fork" a session and ask asides or make notes/todos in a way that doesn't disrupt or confuse a more focused task going on.

I don't think I want a gastown-style "just yolo everything" approach, in fact I really want more control over how decisions are made and with what info. Does this exist?

mikepurvis··on The Tragedy of the Cognitive Commons
The truly wild situation for me is when I have something self contained enough that I can let the bot manage the entire loop unsupervised. Like, here's the patches from the old version, here's the new version, here's the test suite that's got to pass. I'm going to bed now, see you in the morning.

And in the morning, I have patches for the new version that pass the test suite.

mikepurvis··on The Tragedy of the Cognitive Commons
I think as an existing expert in my field (robot devops) what I feel most strongly is not that I'm losing my skills but rather than I'm losing my nerve.

Like, problems that I would previously dig into on my own, poking at this and that log file to try to understand what happened to get a system into a particular state, now claude is mediating most of those kinds of interactions and it is the one doing the first pass surfacing of "okay I discovered X, Y, and Z things that are hinky, and I'm not totally sure yet what this all means, but let's look together."

Nowadays I feel almost naked looking at a terminal where I'm typing each character myself. A lot of the old instincts around tab completion and grepping through the --help output of every tool, all that stuff has atrophied somewhat. Maybe that is genuine skill decline?

mikepurvis··on Cool URIs Don't Change (1998)
Might have been an overeager packaging designer that printed that and then filed a ticket for someone to set up the redirect and that ticket is still in the person's queue.

Or it's something about your own connection. Maybe an ad blocker? For me, the redirect works:

    $ curl -IL logitech.com/mx 2>/dev/null | grep http
    Location: https://logitech.com:443/mx
    location: https://www.logitech.com:443/mx
    location: https://www.logitech.com/en-ca/mx.html
(I have the Mechanical Mini keyboard and the 3S Anywhere mouse; I like the MX product line.)
mikepurvis··on Cool URIs Don't Change (1998)
Sadly, though:

    $ curl -I https://www.nsf.gov/pubs/1998/nsf9814/nsf9814.htm
    HTTP/2 404 
    content-type: text/html; charset=UTF-8
    content-length: 54737
    date: Sun, 09 Aug 2026 17:58:44 GMT
    strict-transport-security: max-age=31536000; includeSubdomains; preload
    server: Apache
mikepurvis··on My server is a phone now
I like my little jonsbo N2 case, and really I haven't hit actual perf limits yet, so I'm fine for it to chug along as-is for as long as I can get it to.
mikepurvis··on My server is a phone now
This is my situation exactly. Got an i5-4570 with 16GB, no GPU, running Unraid with a bunch of containers for Jellyfin, qBittorrent, Crafty Controller (minecraft), HomeAssistant, etc.

I'm using a PCIe expansion card to get double NVMe drives for the cache disk, and then three (up to five) 3.5" spinning 8TB drives for long term.

I tried really hard to get it on 32GB but sadly the motherboard only has two slots and only supports 8GB DDR3 modules. I literally ordered some of the rare late-generation 16GB ones and it refused to boot, with no firmware updates available from the vendor (Advantech, board is an AIMB-274).

mikepurvis··on The Nixpkgs core team has disbanded
I mean... a big part of that with conventional Linux distros is the idea that you can security-update a low level library and all the stuff linking to it gets the fixes "for free", a dream abandoned both by Nix and also the movement toward distribution via containers/flatpaks/VMs/whatever.
mikepurvis··on The Nixpkgs core team has disbanded
At the time I was there we hadn't made it all the way to NixOS on the targets, so it was an Ubuntu "base" + Nix managing the app workspace as a kind of pseudo container, though able to bring more of its own system configuration with it (https://github.com/numtide/system-manager) than the more typical nuisance setup of container + separate outer config managed by ansible or a deb or whatever.

As a result of that, in "production" we still actually delivered full rootfs images just to be absolutely certain, and the delta upgrades were for smaller test fleets that could updated hourly just via simple push tooling.

If I was building it from scratch though, I'd probably just do NixOS + colmena, and do a push model forever. It's not worth the saved SSH connection to not have those logs and status messages coming back to the central coordinator immediately.

mikepurvis··on The Nixpkgs core team has disbanded
This was a talk geared specifically at a ROS audience so it's lighter from a general infra point of view but there may still be something useful:

https://vimeo.com/767139940

At the time of that talk we threw up a lightly sanitized version of the tooling on github. The basic idea was that there were these two repos:

https://github.com/clearpathrobotics/nix-ros-base

https://github.com/clearpathrobotics/nix-ros

The first was the "toolkit" repo that had all the manual maintained dependencies and functions, while the second was a managed repo which would have tags pushed to it by the pipeline.

So basically all the repos had a push hook attached to them that would run this centralized dispatch workflow (on Jenkins, but it could be anything). The dispatch job would sanitize the branch name like joey-b/fancy-feature and attach it to the most recent "released version" + devel timestamp, so you'd end up with like 2.25+20260808-12345+joey-b-fancy-feature, and that would be pushed as a floating tag to the nix-ros repo with all the sources from the hundreds of participating repos either locked to the versions set in the top level 2.25 devel branches or to the specified feature branch, so that a given build could pull together multiple same-named branches from across repos. That would be sent off to Hydra, and nix2container outputs were also built that went to simulator based validation.

But the end UI was pretty nice, basically a nix configuration mapped the names to the those repos so after the build was done you could just pull it and "enter the workspace" environment like:

    nix build ros/2.25+2026080-12345+joey-b-fancy-feature#setup
    source output/setup.sh
And if you were hacking on the "base" repo itself, it was very easy to pass flags like --override-input base=ros-base#some-ref or path/to/local for quick iteration.

Anyway, as I say, I'm obviously proud of what was achieved, particularly in a pre-LLM world, and the experience of building this has given me many of pg's blub experiences over the years, where I look at the ways that other build and packaging systems solve these problems and think yes, yes I can see how that works, but also, I have experienced a world where in exchange for some relatively minor strictness tradeoffs, the set of problems that that is solving never had to exist in the first place.

mikepurvis··on The Nixpkgs core team has disbanded
In my personal life, I also like Nix for small projects, especially where you're crossing multiple ecosystems so that any one system's tooling/lockfiles aren't really enough to "enclose" the whole thing.

For that work project though, the final closure was thousands of store paths, with hundreds of source repos being brought together across a multiple of languages and build systems. A lot of that was/is essential complexity, just the reality that robotics is hard, the tools aren't as mature as in other domains, and so you have to be able to develop features and bugfixes all over a huge software stack simultaneously. Doing that with conventional tooling basically gets you a rigid world where you have to tag/release intermediate packages all the time just to get changes into testing, or you have to build the world on every push (lol docker).

With input addressing and hermetic building of the intermediate stages, Nix and Bazel are systems that don't make you make that choice.

mikepurvis··on The Nixpkgs core team has disbanded
The way I set it up at my shop was that everything would build on your PR, and so by the time it merged, everything was already cached and no one should see a rebuild... at most a download.
mikepurvis··on The Nixpkgs core team has disbanded
I was lead on a Nix adoption effort for a few years that was kind of like that: it solved real problems, unlocked far faster, smaller, and cheaper builds than would have been possible any other way, and let us ship delta updates over crappy wifi connections to Linux computers on robots. Flakes were a perfect fit for our model, and we were just in time for stuff like up to date versions of cuda and tensorflow to be delivered via nixpkgs.

In my mind, Nix was unstoppable, and I particularly loved how empowered I imagined developers would feel. No mystery-meat CI scripts pushing packages to distant infrastructure that no one understands or even has the permissions to interact with, just the entire build system in one repo, trivially cloneable and hackable... add patches or build steps to anything and it's the same build as always, build it locally or send it to Hydra, it doesn't matter.

A devs "got" it and did leverage those things, used PRs to do safe evaluation of bumps to core dependencies, but I think on the whole it was regarded as cool but not tractable, and a few years after leaving, it sounds like plans are being laid to replace it all with something containers or whatever.

Very frustrating, particularly in a world where it should be trivial to identify the 5-10 typical tasks that people want to do with the nix code, and set up Claude skills to handle those. Given how easy and self-contained the build-test loop is, it feels like an almost perfect fit for agent-led development.

mikepurvis··on Quake – 30th Anniversary Update
I think games that are heavily reliant on online pvp are just always going to struggle with being more niche appeal. Matchmaking is hard to do well and consistently, and managing the skill/progression curve is hard— there's gotta be things in there to master, but also new players will never join if they're just getting stomped every game because they can never catch up.

This tension has arguably been a contributing factor in the collapse of the ARC Raiders playerbase, with a huge population who joined primarily to shoot and loot the robots eventually confronting the realities of a pvpve game, and peacing out for good after getting shot in the back or ambushed too many times.

mikepurvis··on Read this before you buy that TV streaming stick
Indeed. Owning the streaming box lets you loose on whatever network it's on, but it doesn't actually get you inside the content gardens; those are separately managed by teams of people much more motivated to protect their IP.
mikepurvis··on AI's top startups are barely publishing their research
I mostly got it to play Arc Raiders tbh, but I did kind of have in mind that it was worth stretching for 16GB so that local models would be on the table.
mikepurvis··on Turning a dumb AC unit smart (without losing my security deposit)
IR blasters are rough because there's no feedback. You're literally just shouting out commands into the void, and heaven forbid if it's something that's a toggle where you don't know which state you're starting from.
mikepurvis··on AI's top startups are barely publishing their research
Okay interesting, so maybe openclaw does a lot less than I thought it did; really I have no excuse not to be just trying it myself regardless, given that I'm sitting on a 9070 XT.

It doesn't look like you're building directly on openclaw, so is that coming from a place of different goals or philosophy, or what?

mikepurvis··on AI's top startups are barely publishing their research
I'm very interested in this kind of thing as a kind of ADHD brain augment, like it's monitoring my slack, github, email, calendar, active terminals, etc, and helps me prioritize what I should work on as well as weighing whether this or that ping is worth interrupting me for.

I assumed that's what openclaw basically was, but is Orb different from that? And is it fundamentally a different model from the request/response, or is it just request/response in an autonomous loop?

mikepurvis··on LG to ban residential proxies from smart TV apps
I'm mostly very happy with my LG C4 as a home theatre centerpiece, and I did have it online so that I could use the apps for YouTube and Jellyfin. However, the lack of support for modern 4k rips (HEVC+DTS) ended up being a dealbreaker and I finally ditched the built in software for a fire stick instead.

No transcoding, no weird codec issues, just the raw files direct streamed from the underpowered Unraid box, into the back of the AVR where the audio is handled correctly and the video is sent to the screen.

mikepurvis··on FreeInk: Open ecosystem for e-readers
I'm not knocking the devs for the choice to target open hardware, only remarking that that choice signals the project is for hackers, not regular consumers.
mikepurvis··on FreeInk: Open ecosystem for e-readers
I've never heard of any of them; I guess it's geared toward build-it-yourself or kit-type devices? I can't imagine a serious aftermarket FW not supporting a single Kindle or Kobo device.
mikepurvis··on Qwen-Image-3.0: Rich Content, Authentic Details, Deep Knowledge
Wide angle lenses have been a thing in real estate photography since forever, but you would always have the reference of the furniture to ground your perception. Having furniture be slightly downsized is diabolical.
mikepurvis··on Qwen-Image-3.0: Rich Content, Authentic Details, Deep Knowledge
I've started to see this on Etsy and Wayfair too, where there will be a listing that is clearly just MDF flatpack being resold from China, but the AI-generated images wildly exaggerate the proportions of it.

Here's a recent example: https://www.etsy.com/ca/listing/4509158065/corner-wall-shelf...

Ironically, ChatGPT is decently good at ferreting these out. Like I sent it a screenshot of that listing and it not only helped me find where the original item was for sale, but also pointed out how the dimensioned diagram shows it as being just 49" tall, whereas the "in real life" image looks like it's at least six feet, based on it coming up over the top of the picture frame.

I ended up engaging a local woodworker to make me a piece like it instead. Obviously an order of magnitude difference in price, but it will actually be real solid walnut and finished to match my dining table.

← PreviousPage 4 of 34Next →