I keep the context concise by linking from claude.md to markdown files with the hardware architecture, the network architecture, the processing tech stack. Concise and specific. And a current project md. I mix in the parts that are relevant. I don't have a roadmap and session log though. Good idea.

Very nice that there's a coding cli finally. I have a Mistral Pro account. I hope that it will be included. It's the main reason to have a Pro account tbh.

This 2003 interview with Anders Hejlsberg gives considerations why he didn't add checked exceptions to C#. https://www.artima.com/articles/the-trouble-with-checked-exc...

I was excited at the idea of ShapeRank. A modern APL successor aimed at tensors, vectors, arrays of unbounded length.

Unfortunately work on it seems to have stopped two years ago. https://github.com/f5devcentral/shapeRank

For those who speak Dutch: here's a higher, more readable, resolution at the Rijksmuseum. https://www.rijksmuseum.nl/en/collection/RP-P-OB-76.978

I wonder if MS is aiming to use the conversations about software that employees are having in Teams meetings as training data for AI. To automate them away.

I think Americans pronounce names like Weinstein as 'winesteen'. So perhaps the pronunciation of the latter syllable makes German origin diphthongs confusing.

We do know how to pronounce Einstein though!

I’m sure you personally do, but I’ve noticed that many English speakers pronounce it without the “sh” sound in the middle.

Good point, in fact I retract my statement because of it. I was only thinking of the vowels.

Or the Steven Soderbergh movie 'Kafka'

It's an interesting idea; not having to stash messages in the actor implementation when doing an async call. I did a little experiment what that could look like using Akka and kotlin suspend functions https://github.com/joost-de-vries/akka-kotlin

The need for flags in itself may be a sign of the wrong approach. You create a shared module. But for some cases the handling should be different. Let's pass in a flag or configuration. So somewhere in the shared component it will handle things differently. Oh wait, there's another case. Another flag. Which combinations of flags are meaningful and which aren't? The nearest improvement is to put all the cases in an enumeration. But wait it's not one 'dimension'. Let's have two enumerations. And the extreme end point is that your shared module has a full blown DSL for the parameters it receives. Or even an interpreter. The other solution that is often more understandable and debuggable in the long run is to not have the shared module call specific code for cases. But to have specific code pull in shared commonalities. No need for flags.