Analyse files in this repo, and start work. Bootstrap a CLI to manage memory across multiple AI sessions, one that can evolve into a portable semantic and ontological representation of my use of AI across all my projects. Use Zig. Keep it metal! #fable let's go!
Ok! The soundstage got a major upgrade today! After decades of ogling, I’m a proud owner of an Accuphase E-301. Paired it gingerly with Kappa 6.1s. Ran through some Pink Floyd, Bill Evans, Macklemore, Jamiroquai, a whole host of others. Life cannot be better.
Make no mistake: post-Mythos, the United States has a licensing regime for AI. It’s just informal, with no consistent rules or firm boundaries on state power or public transparency. Cobalt mining in the Congo is vastly more institutionalized than frontier AI licensing in the US.
i hooked my whoop to my work calendar to find which coworker gives me the most stress 🚨
thanks to fable, I reverse engineered whoop to pull per minute heart rate. nd matched spikes with cal events and attendees
I now have a leaderboard and I think about it daily.
few info masked for obvious reasons ;)
How much local AI can you squeeze out of a 16GB Mac Mini? Cloud is great, but I wanted to muck with the silicon. I vibe-coded a test harness to benchmark 13 local LLMs. From Llama 3.2's cache speed to the brutal 14B memory swap cliff, here is the data:
https://t.co/SCplrYFSXl
AI that doesn’t know YOUR stuff is annoying. Would you pay $5/mo for one secure vault — your records, books, workouts, notes — that Claude/ChatGPT can read?”
Hello PMs of Vancouver! Here is an opportunity to join the amazing Eventstream team at Microsoft. If you want to know about what we do in this team, or want to dive deeper into my experience joining this team about a year ago, come chat.
https://t.co/S2xl1zhTdB
Most engineering teams screw up messaging because they don’t understand one thing:
Streams hold truth.
Queues do work.
When you get this wrong, your system bleeds.
I’ve seen $10M mistakes from teams who dump everything into queues:
“Just push the order to a queue and process it!”
Most Queues delete messages after work is done.
No history. No replay. No audit.
Just pain and guesswork.
On the other side, some teams fall in love with Kafka:
“We’ll stream EVERYTHING!”
Here’s the rule I wish someone told me early:
If the event changes the business → Stream
If the message is an action to perform → Queue
Streams = OrderPlaced, PaymentAuthorized, InventoryReserved
These are immutable facts.
They must be durable, replayable, ordered, and auditable.
Queues = SendEmail, CapturePayment, GenerateInvoice
These tasks exist temporarily.
They matter NOW, not 6 months from now.
Event enters the stream → workers derive jobs → queues execute tasks
Ledger first.
Assembly line second.
Everything else is technical debt disguised as cleverness.
I’ll share a small part of https://t.co/UQ4RFIKUwO
Back in med school, I became obsessed with augmenting memory and dreamed of a Notion or Obsidian that completes itself. Today, we’ve built something close.
My self-awareness is sharper and everything feels connected. I genuinely believe AI does not replace humans. It amplifies us.
Huge respect to our engineers and designers who made this crazy thing real.
Bubbles are the episodic units of my life that the system interprets from my raw data. Clouds are the system’s questions, its hypotheses about who I am.
When I answer a cloud, it becomes a bubble again.
There is so much personal data that I cannot fully demo it. Wish I could. This system understands me more deeply than anyone.
Want to try it? Retweet and comment “memory.”
I’ll DM you an access code to skip the waitlist.
@ThePrimeagen Have you tried implementing a discriminated union? C is just *chef’s kiss* for this. No other language makes it simple or easy to this. I spent 5 years building a DSL for a router OS, and C over C++, Java (go and rust didn’t exist then), Lua, precisely for this reason.