@jdxcode
Account based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
I make open source dev tools at https://nitter.cf/t.co/lrm2L4SCse like mise, aube, fnox, hk, mbx, pitchfork. Previously I wrote the heroku cli and oclif. ex-amazon/meta.
Dallas, TX
Joined July 2006
- Tweets1.8K
- Following1.3K
- Followers6.9K
- Likes1.5K
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
thanks @Mend_io for upgrading my OSS plan! mend.io/blog/mend-renovate-c…
a snappy screensaver absolutely makes an operating system better.
preview should be fast. it should use minimal battery. it should close *extremely* quickly.
jdx retweeted
🔴 Live today at 4pm CET with @jdxcode, creator of mise 🛠️
youtube.com/watch?v=aPg44O9i…
one of the problems with rust dev that mr-boxington fixes (or at least mitigates) is a bunch of agents running and hitting OOM while also permitting cargo builds to run in parallel (even in the same worktree). it has a scheduler that hands out permits to keep cpu/memory under control.
it's not perfect and you can definitely still hit OOM issues. one reason for this is it monitors cargo processes but your agents may be running tests or doing other work that is outside of its scheduler.
in the next release I'm adding optional support for `cargo test` executions to run within the scheduler. it does this by running rusage and recording how much cpu/memory the tests take.
anyhow, if you use mr-boxington, definitely send some ideas on how we could continue to improve this.
jdx retweeted
Mr. Boxington by @jdxcode has saved the day.
Before using it my machine was getting CRUSHED having multiple agents writing Rust. I would get alerts constantly of the HDD being full. Problem solved!
jdx retweeted
btw, thank you @jdxcode for mbx, it brought my compile times down ~40%
mise.lock now automatically generates aube/uv lockfiles as external files:
[[tools."pypi:black"]]
version = "24.10.0"
backend = "pypi:black"
uv = { path = ".mise/locks/pypi-black/24.10.0", digest = "sha256:…" }
this not only locks the full dependency tree but i'm using the idiomatic lockfile here so that security scanners don't need to understand some new toml syntax for all the transitives, they can just read aube-lock.yml/uv.lock like normal
(aube-lock.yml is just a renamed pnpm-lock.yml btw)