JJ, using the squash workflow, is brilliant for working with Claude
The workflow is straightforward: I create a named revision for the work I want to do, then an unnamed revision on top. I prompt Claude, changes land in the unnamed revision, I review those, squash the parts that I'm ready to accept, prompt some more to iterate on the parts that aren't up to par yet. Rinse and repeat until the topmost (unnamed) revision is empty.
I instructed Claude that I use jj with the squash workflow, so it should never touch revisions with a non-empty description (I also needed to tell it to shut up about that check), and the whole thing flows pretty damn smoothly.
I just tell Claude to fold changes in their respective commits when working on a feature branch. No need to do rebase edits or anything else really. I don't really have to think of what gymnastics it has to do to get there.
It's the same basic concept, yes. The details matter, though, and the fact that AoS/SoA is mostly about in-memory layout, whereas row/column store is about on-disk layout means that the performance compromises are very different. E.g. column store databases frequently use RLE for compression, but that's probably _way_ too expensive for SoA.
One thing to add is that databases tend to take it further using compression. For instance, if you have a column that is all either A or B, you can use run-length encoding ("the next thousand entries are B"). Or you can do delta encoding: if you have some very large number that takes a lot of bits to store, but the deltas between them are quite small, you can save a lot of disk space and I/O by just storing the deltas.
You can also combine these two: if you have a numeric id that increases by 1 every row, you can delta-encode that to just get a massive list of 1's, which you can then run-length encode to just be "the delta for the next million rows is 1", saving huge amounts of space.
You generally don't do this with AOS/SOA, because you do want to be able to random-access your entries ("index" them, in database terms) and I/O performance is much less important. Databases have this issue too, which is why indexes tend to either not be available or much slower in column-oriented DBs.
EDIT: ah, read the original commenter a bit too quickly, missed that they mentioned run-length encoding. Apologies.
One of the cool things about Vortex (which is a file format, but in this context can be better thought of as the storage layer of a DBMS) is that we have implemented compression encodings that _do_ support fast random access. For example, FastLanes allows us to bit-pack values extremely effectively while retaining random access, and this can be combined with other encodings such as ALP and FSST.
I believe Vortex is unique in its ability to retain random access while recursively compressing data. And turns out that this is helpful for both in-memory _and_ on-disk (we might write about that in the future)!
I unfortunately didn't have much space to write about that in this blog, but in the compression section I did link to other blogs that we have written that go into much more detail, if you are interested :D
Fun fact, the original Pokemon used both DE and RLE to compress the sprites. It's one of the things that makes missingno screw up sprites (it tries to decode game data as if it's a sprite encoded this way and sometimes causes buffer overruns)
Appreciate you going into more detail about how run-length encoding works in any case. I had an abstract idea it was something like that, but didn't realize it could actually be implemented so 'simply'.
On the one hand, you missed me mentioning RLE. Oh no how dare you.
On the other hand, you added a bunch of extra detail, including stuff I didn't know about.
> While probably harder to find a no-questions asked buyer, the price premium on GPUs is a lot higher than some consoles.
I'd go further than that. A no-questions-asked buyer for a console merely suspects there's shenanigans afoot, and will expect a considerable discount off the sticker price. A no-questions-asked buyer for server GPUs almost certainly knows for a fact there's shenanigans afoot, but is likely to pay a premium over the sticker price anyway.
Another reason why they are cheap is because Xbox will ban the consoles once they know they were stolen. GPUs on the other hand don't have a remote kill switch after being stolen.
Given current market tends, if that becomes more frequent the likelihood of consumers actually getting GPUs goes up, as these will at least end up on various markets
While I appreciate and broadly agree with your bigger point, I'd argue this particular bit is a bit uncharitable. Articles about nerds doing interesting, unusual things do make the front page pretty often.
They do but the point point is that this post made it because of the AI hype. Not the discovery itself which should grant more attention than that of a machine doing archeological "work" that happens to misinform.
In an honest, well-functioning org, those are decisions made by completely different groups that do not (and should not) report to each other. It's actually kind of depressing that we (and I include myself in that) assume otherwise by default.
I have bad news: most large corporations are successful because they know how to make money. Often, the internal operations, are disappointingly bad, just not bad enough to kill the corp fast.
Source: I've worked in and with many successful organizations, and worked at one place with proper internal processes, so I know what's possible
I have observed that also. Though I'm still not sure whether: 1) there are some small pockets where important decisions are made, innovation happens and the needle is moved, and dysfunction I see is just justified bloat of the company 2) it is the entire corporation like that but it somehow works at the end.
The way I would describe large companies is similar to that joke "Mandatory scheduled fun events" just with innovation. Most large organizations cannot innovate, instead they execute well. Look at all the major large organizations, they primarily distinguish themselves on execution, not innovation. A startup that's hobbled together by passionate soft drink makers (or whatever) aren't gonna come close to full business efficiency of Coke Inc. The manufacturing capacity, distribution channels, the logistics, the brand management and awareness, the brand integration and cross promotion, and other things that come from economy of scale. The rigid structure is not a place for innovation to grow.
>I have bad news: most large corporations are successful because they know how to make money.
Who is they? Do you have any idea what its like working at an org the size of GS, that you actually think these two completely different departments discussed the matter with each other?
I'm no longer in that industry, but as I recall there are actually rules imposing independence from investment banking and research arms, for example. Dates back to the Dot Com era where research analysts were touting IPOs for the investment banking division.
Really? You think executives at GS waste their time debating where software should be installed on trading desk computers? They have entire departments dedicated to handling those issues...
ANT was expected to be the largest IPO ever, it may still raise more money than SpaceX, so this is an incredibly consequential deal for GS.
Restricting Ant's primary revenue driver across a broad swath of GS weeks before trading would trigger immediate leadership review. What organizational background and level of experience are you extrapolating?
I think that if this wasn't sanctioned by someone at the top then there would be a round of public hanging, drawings and quarterings in the IT department.
What is the Investment Bank version of "flogging round the fleet"?
> In an honest, well-functioning org, those are decisions made by completely different groups that do not (and should not) report to each other.
I don't agree at all. Different groups should be supporting each other and the overall bottom line instead of their parochial, narrow self-interests - the latter is a poorly functioning org.
If by group A delaying its $100M cost-cutting, group B can add $1B to the bottom line, it would be a corporate and group management failure for group A not to cooperate.
Well functioning by what metrics? To make money? No doubt Goldman sachs does that. But making money often has the incentive of ignoring ethics .. which is what this thread was about. Would they ignore ethics to make more money?
So here, would they synchronize announcing big things in relation to the hottest and most risky investment there is right now?
"what motivated them to announce this a few weeks before trading starts?"
Also what’s your point? Goldman Sachs shouldn’t pull Claude Code because there’s no point in trying in this world and we should all give up on everything?
To me the second response reads more like PR-speak, like somebody who's been over-coached on how to talk to customers.
I find it strange that they'd have an AI-driven followup email days after the survey. If you're automating it, why the delay? "Delay the response so it seems more human" is way too cynical.
It's worth noting that OP is talking about Ocado, too. I've been a client of theirs for over ten years, and the number one reason why I keep buying from them is that their delivery drivers never feel super-hurried. They have lower quotas than drivers for other services, and they always have time for a little bit of banter. Compare that e.g. to Amazon Fresh drivers, who'll always just leave the groceries at the door and knock. They're already gone by the time I open the door.
I find it unlikely that they'd automate this sort of second-level customer support response while not squeezing the everliving shit out of their drivers.
The "top 20 of 2026" table in the article puts Amazon at $776B, but only 3.75% of that ($29B) attributed to B2C revenue. I don't know whether that number is correct, but AWS is clearly a massive chunk of non-B2C revenue for Amazon.
> It's clear he brought a gravitas to the role that inspired a team of young/new actors around him
That's a lesson everybody on this site should learn — Every senior is a leader, even if they don't think they are. People (mostly the more junior sorts) look up to you as a role model whether you (or they) know it or not, and that's very real power that you must learn how to wield.
I've given negative reviews to technically excellent candidates in the past because just about everybody in the org would look up to them if they got hired, and they would be a terrible role model.
The workflow is straightforward: I create a named revision for the work I want to do, then an unnamed revision on top. I prompt Claude, changes land in the unnamed revision, I review those, squash the parts that I'm ready to accept, prompt some more to iterate on the parts that aren't up to par yet. Rinse and repeat until the topmost (unnamed) revision is empty.
I instructed Claude that I use jj with the squash workflow, so it should never touch revisions with a non-empty description (I also needed to tell it to shut up about that check), and the whole thing flows pretty damn smoothly.
reply