Human-Cabbage

8 ms·

1.
by Human-Cabbage 24d ago
Seems to be back up now, I've had a couple messages go through successfully in the past ~5min.
2.
by Human-Cabbage 2mo ago
Huh, that’s what happened. Good thing my company has Bedrock as a backstop for situations like this.
3.
by Human-Cabbage 2mo ago
Is ChatGPT's interface always this atrociously jittery? Or is it just because this page is getting an HN hug-of-death right now? Every time I try to scroll the whole page goes blank for a few seconds and then re-renders.
4.
by Human-Cabbage 2mo ago
Is this the GTA 4 trailer?! /s It’s too bad that ssh doesn’t carry sound. A MIDI-style rendition of the song would really tie it all together.
5.
by Human-Cabbage 2mo ago
Surprised nobody here nor on the reddit thread caught this one: https://github.com/nahla-nee/wfqueue/blob/main/src/lib.rs#L3... unsafe impl<T, const N: usize> Sync for WFQueue<T, N&gt
6.
by Human-Cabbage 3mo ago
Yes, just like New Coke back in the 80s. Genius 4D marketing strategy.
7.
by Human-Cabbage 6mo ago
This is correct at the firm level and breaks down at the aggregate level, which is where it gets interesting. At the firm level, automating away labor costs is obviously rational. But capital in aggregate can't actually rid itself of
8.
by Human-Cabbage 6mo ago
China and/or Russia might have a collection of zero-days they've been sitting on, which they could surreptitiously provide to Iran. Of course, there's attribution risk there, and the opportunity cost of not saving those zero-
9.
by Human-Cabbage 7mo ago
Containers here, though I don't run Claude Code within containers, nor do I pass `--dangerously-skip-permissions`. Instead, I provide a way for agents to run commands within containers. These containers only have the worker agent'
10.
by Human-Cabbage 7mo ago
Julia is aimed at scientific computing. It competes against Python with numpy/scipy, R, etc.
11.
by Human-Cabbage 7mo ago
Use the exoskeleton at the warehouse to reduce stress and injury; just keep lifting weights at home to not let yourself atrophy.
12.
by Human-Cabbage 7mo ago
> the “art” part of it is writing sound, scalable, performant code that can adapt and stand the test of time. Sure, and it's possible to use LLM tools to aid in writing such code.
13.
by Human-Cabbage 7mo ago
The optimistic case is that instead of a team of 10 people working on one project, you could have those 10 people using AI assistants to work on 10 independent projects. That, of course, assumes that there are 9 other projects that are both
14.
by Human-Cabbage 10mo ago
This conflates use-value and exchange-value. Water to someone dying of thirst has extremely high use-value, while a diamond would in that same moment have nearly no use-value, except for the fact that, as a commodity, the diamond has an exc
15.
by Human-Cabbage 1y ago
It'd be more helpful if you explained what exactly is wrong, and what you suggest to do instead.
16.
by Human-Cabbage 1y ago
There are a couple main ways to achieve a workflow similar to Git's staging area. #1: Squashing Create a revision for the feature, then create another revision atop that. $ jj new main -m 'feature' $ jj new $ jj @
17.
by Human-Cabbage 1y ago
Jujutsu distinguishes between "revisions" and "commits." Revision IDs like "rzouzmyw" stay stable, whereas commit IDs of course change with the content. You can see in my example how the commits associated with
18.
by Human-Cabbage 1y ago
To reinforce the sibling reply with a concrete example: Let's say you've got a few feature branches, all based of the trunk branch. $ jj @ ozywpwxm samfredrickson@gmail.com 2025-08-31 13:21:59 b2f1364d │ (empty) (no desc
19.
by Human-Cabbage 3y ago
This is the second time I've seen $7T referenced without a clear citation. Is this just rhetorical or did Sam Altman actually say it somewhere?