I make open source dev tools at entire.io like mise, aube, fnox, hk, mbx, pitchfork. Previously I wrote the heroku cli and oclif. ex-amazon/meta.

Dallas, TX
Pinned Tweet
this was awesome @dhh
Here's my conversation with @DHH. He is back for round 2! It was an epic fun 5 hour conversation about the future of programming, AI, Linux, and human civilization. It's here on X in full and is up everywhere else (see comment). Timestamps: 0:00 - Episode highlight 1:27 - Introduction 2:56 - Programming with AI agents 18:14 - How software will change 27:30 - AI impact on open source 37:21 - Building Omarchy Linux distro 47:05 - Vibe coding vs agentic engineering 1:00:06 - The end of manual programming 1:10:24 - Advice for programmers 1:22:30 - Surviving Internet Hate 1:31:46 - Programming setup for AI Agents 1:44:11 - Obsessing about speed 2:07:06 - Voice prompting vs typing 2:21:05 - Best AI coding models 2:37:55 - Best AI coding harnesses 2:50:57 - AI video generation and filmmaking 3:10:28 - Fatherhood 3:38:35 - Linux will win the desktop 3:49:51 - PewDiePie 3:59:24 - Future of programming 4:22:17 - Politics and immigration 4:53:54 - Longevity, over-optimization, and fear of death 5:05:38 - Eternal recurrence and future of human civization
13
20
502
48,571
2
1
23
1,092
the anthem for everyone struggling with cargo's 100gb+ target/ directories from rust git worktrees: pray silence for mr-boxington 📦🍓 github.com/jdx/mr-boxington
3
6
38
2,725
jdx retweeted
Created "btop for io", inspired by "why the hell is cargo so slow on btrfs" Top: all volumes showing bytes/s, iops and r + w latencies, diamond marks p99 Bottom: reads and writes detail view for a single volume github.com/jbellis/iodyne
3
5
64
3,495
i am planning to change the install directory layout in mise. there are good sec hardening/perf/functionality reasons for doing this. if you think this might affect you please have a look: github.com/jdx/mise/issues/1… this will be done with a slow rollout and it should be backwards compatible but it's also a pretty fundamental change. sorry if the issue is a bit slop, i will be working to fix that today. i would encourage you to have your agent look at it and compare it to your mise setup to see what it thinks rather than just reading it.
5
1
19
2,217
it's true. i built hk at lastjob for this reason—saved loads on CI usage by having pre-commit hooks that are fast enough engineers don't skip them.
Replying to @p_ch
Pre-commit hooks could also help catching faulty runs.
1
20
2,425
every page in the hk.jdx.dev docs is now translated into pirate for "Sea shanty mode"
1
17
1,347
🎶 I got my miiiiiiise 🎶 piped.video/_k-tLPga-Yg?is=FyJC…
1
3
549
and yes when i was tufting i accidentally grabbed the wrong shade of red yarn
1
291
Your target/ dirs are eating your disk, especially with coding agents in git worktrees. mr-boxington (mbx) is a Cargo build cache that cleans up after itself: 3.9 TiB pruned on my dev box in 3 weeks. New in 1.21: cargo clippy + cargo build side by side, zero config 👇
4
11
131
11,050
Builds share one CPU and memory budget, so several agents running cargo at once don't bury the machine. You get a live hit/miss view with time saved, and there's no daemon or server to run.
1
2
775
Try it with mise (2026.9.2+): mise use --tool-option mr_boxington=true rust mr-boxington Plain cargo commands then go through mbx. mr-boxington.jdx.dev
1
6
594
now that's a switch worth flipping
3
2
53
3,076
i made a sea shanty version of my hk video
2
3
25
1,908
11
5
47
3,812
one of the reasons i changed the name of mise from "rtx" was that I was concerned nvidia might tell me i had to. though in hindsight, rtx was just a terrible name anyhow and renaming was definitely the right call.
Idk if it infringes on ours or not, but I do know there are a variety of sentry names and the trademark area is very sus At the minimum it’s pretty unprofessional from nvidia
3
26
5,043