[jchw]

Until I actually went to read the code, I thought this was just a kinda lame overplayed joke, but the number of lines they listed made me really curious: how did they manage to beef up the SLOC that much? After reading a bit of the source code, I take it back. That's definitely venturing into the territory of art.

[godelski]

  // Custom crab-grade allocator with quantum optimization
  #[derive(Debug)]
  struct QuantumEnhancedBlazinglyFastAllocator;

I can't wait until they develop the QuantumMachineLearningEnchancedBlockChainBlazinglyFastAllocator.

I heard Google is giving them a $1bn seed round!

[nasretdinov]

It does have blockchain though, you can search for a substring in the code

[vram22]

yes

to mass-produce this app, using the Rust equivalent of Java's FactoryBuildingFactories.

[22c]

Someone better versed with parsing crab-grade enterprise-ready Rust could probably give more insight but I think it boils down to a lot of

    assert 1 != 0;

kind of lines...

[Syzygies]

Yes, art!

I've been in a constant struggle with Claude Code over variable names. I've picked up speed by just getting the code working, fixing names later.

The variable names are what first jumped out at me, looking at this code. It spoke to my pain.