Much more recently I heard on QI about how medieval people, not knowing about migration, believed, through a lot of leaps, that it was ok to eat barnacle geese at lent. Worth investigating if you are curious :)

This is the kind of buzz I search out in my own programming :)

Have fun and keep challenged :)

I’m not a parallels kind of user but I can appreciate your craft and know how rewarding these odysseys can be :)

What was the biggest “aha” moment when you worked how things interlock or you needed to make both change an and b at the same time, as either on their own slowed it down? Etc. And what is the single biggest impacting design choice?

And if you’re objective, what could be done to other tools to make them competitive?

But the last few weeks Opus 4.6 seems to have got dumb again. Now it is making way more mistakes and forgetting useful things and recent context it used to manage.

I am guessing this is just Anthropic quietly dialling down the real effort as they either downsize or free up compute for someone or something else.

But I imagine even these rooms are cammed, and lip reading is a thing

https://gwern.net/doc/cs/2005-09-30-smith-whyihateframeworks...

And aside from algorithms, it usually comes down to avoiding memory allocations.

I have my go-to zero-alloc grpc and parquet and json and time libs etc and they make everything fast.

It’s mostly how idiomatic Java uses objects for everything that makes it slow overall.

But eventually after making a JVM app that keeps data in something like data frames etc and feels a long way from J2EE beans you can finally bump up against the limits that only c/c++/rust/etc can get you past.

Is there a sort order? Would be so nice to understand the threads of evolutions and revolution in the progression. A bit of a family tree and influence layout? It would also be nice to have a scaled view so you can sense the difference in sizes over time.