README doesn't mention anything about how transactions work across the shards.

I see this https://github.com/schapman1974/briskdb/pull/260 but it says shard-local.

On top of all that I'd add perhaps having a side hobby in learning about AI research/developments and harnesses (Claude Code/Pi/OpenClaw/NanoClaw/Hermes/etc) and auxiliary systems like vector databases and graph databases. Being an AI wrangler could be the equivalent skill that 'big data' processing was previously. Even just being able to speak competently on these could be an edge.

Exceptions include video games where the author is instilling emotion into their creation for the player to experience--not utilities.

I would have preferred it was created by a natural human.

> That Node choice wasn’t a close call for us, and it’s worth being direct about why. Most of the graph tools in this space, including code-review-graph, are written in Python. We considered it, and we’re not doing it ever.

So AI generated marketing text for an AI generated product (probably) based on AI generated whitepapers?

Welcome to Web 3.0 I guess.

Knowing a lot about my personal computer (Atari 400 and later Atari ST) made it so easy to do work on embedded systems as a student intern. Without internet, learning about your hardware/ROM was paramount from magazines and word-of-mouth.

Another thing that I learned from that time is how to make designs fast and small. This is a skill that's not really taught, shared, or practiced much and makes a huge positive impact on a codebase keeping it light on abstraction depth and high on flexible capability. Huge improvement to maintainability and extension into unforeseen directions too.

[0] https://en.wikipedia.org/wiki/Mahalanobis_distance

I had friends that had Ataris of course, but also some that had C64s and even a TI-99/4A. The thing in my circle was that the C64 and TI folk were more users and the Atari kids were more hackers, not that there were very many of each at the time. I learned BASIC, machine/assembly, and got into coding and engineering. (One of our pastimes was cracking games just to see how it was protected and see if we could. We'd show off any success amongst ourselves but never distributed as that wasn't the fun part.) I get the feeling that I probably worked for some C64 kids as adults that always seemed to have more of a product or business sense about them than the Atari kids.

Ratios (count / total) and percentages:

    PG: 0.00047%
    TK: 0.00046%
    KK: 0.00045%
    HQ: 0.00042%
    FN: 0.00042%

Well anyway when the 520ST came out I was to get one but had to choose between the color or monochrome monitor. For some reason this felt like a crucial choice and it was: med/low color or hires monochrome. Surprising to myself I picked monochrome. It was fun learning to program a new computer but it wasn't exciting the same way as on the 8-bit. There wasn't any low-level hardware tweaking, it was more about CP/M 68k, GEM, etc. One thing I did do was try some C compilers with Megamax being the most usable (for floppies). I missed the 8-bit's support chip programming which was lacking in the ST and living in the Amiga. Getting interested in MIDI (with Amiga dropped but the ST picked up) would have been great but I wasn't musically inclined. Well that was largely my cross-over from dreaming of becoming a great video game developer into more of a business professional programmer. Later at a co-op job I did use it again to prototype fast line joint computations for the 68k without an FPU to be used in PostScript firmware in EiconScript[0]. I also wrote the PCL 5 (most not all of 5e) compatible firmware (all except the macros) for their EiconJet (first with a hardware blitter then without). Turned out well in the end, with my interests shifting to OS/2 and multi-threading rather than only games.

Edit: Forgot to mention that I started out incessantly wanting the Timex Sinclair 1000 kit. My father flatly refused and eventually I got the Atari 8-bit. Which I thought was way cooler than the C64. I learned so much programming on that machine--with no way to save my programs for the first year.

There's some info for AnythingLLM[0] which supports RAG. AnythingLLM has LanceDB out of the box but also supports others including pgvector.

[0] https://docs.anythingllm.com/features/embedding-models