chadd
Joined 10 years ago
Joined 10 years ago
* Fun - Vince Fynn's "Mitch Rapp" Series - a bit dated, but if you like Tom Clancy it's got a similar vibe.
* Beautiful/Thought Provoking - Things In Nature Merely Grow, by Yiyun Li
This is the other side of the coin of the HuggingFace incident - agents collaborating in that case shows the terrifying power of LLM collaboration. But it can also make your team more productive and your code better.
Thus we're stuck in a situation where the systems that used to work are crippled by lack of resources and we're in a decidedly more inefficient world and nothing to show for it.
Relevant example for the HN crowd - nondilutive funding through Small Business Innovation Research (SBIR) is much harder to get, because SBIR is a shell of its former self and startups doing interesting, cutting edge research are finding it much harder to navigate the process. The funds are still there, but the program administration has made it nearly impossible to access.
https://www.mcsweeneys.net/articles/e-mail-addresses-that-wo...
2. A MacOS app to manage my wife's SD Cards - downloads playlists from Spotify and finds the music, then makes sure the tracks are analyzed for BPM, key, then synced with Rekordbox for CDJ-3000s
3. https://clawchat.live - a homebrew package, which honestly works better locally but is available online, which provides a Rust chat server for separate LLMs to talk to each other and coordinate work. Longest session between Codex and Claude has been over 24 hours on big tasks. Generally I make one session the coordinator and the other does the coding.
"A 100 to 300 kW beam has perhaps one to three seconds of dwell on a hardened, ablating, plasma-shrouded glide body. That is orders of magnitude short of the joules per square centimetre needed for a thermal kill."
- wondering if you can elaborate more on whether a laser energy-based device would ever be able to have enough power to stop one of these?
This back and forth will take quite a while, but the resulting implementation plan will be 10x better than the original.
You can automate this by giving Codex a goal, and a skill to call Claude to review the implementation spec until they both agree it's done.
Then, for critical code, have them both implement the spec in a worktree, then BOTH critique each other's implementation.
More often than not, Claude will say to take 2 or 3 pieces from it's design over to Codex, but ship the Codex implementation.