AgharaShyam
Joined 10 years ago
Joined 10 years ago
for some reason I had 11 separate codex and codex-code-mode-host binaries in mine. each weighing about ~300 MB.
https://allume.com/memos/2026-07-allume-v4/
Seems like they changed names internally from "Hatch" (some UI still uses hatch instead of muse)
However, I really miss the content posted by the KuzuDB team on their YouTube channel.
Customers need it to build custom reports, archive data into a warehouse, drive downstream systems (notifications, audits, compliance), and answer edge-case questions you didn’t anticipate.
Because of that, I generally prefer these patterns over a half-baked built-in analytics UI or an opinionated REST API:
Provide a read replica or CDC stream. Let sophisticated customers handle authz, modelling, and queries themselves. This gets harder with multi-tenant DBs.
Optionally offer a hosted Data API, using something like -- PostgREST / Hasura / Microsoft DAB. You handle permissions and safety, but stay largely un-opinionated about access patterns.
Any built-in metrics or analytics layer will always miss edge cases.
With AI agents becoming first-class consumers of enterprise data, direct read access is going to be non-negotiable.
Also, I predict the days of charging customers to access their own goddamn data, behind rate-limited + metered REST APIs are behind us.
Does WhatsApp charge money for this? If not, why would a business use their API? They could simply create an app to directly talk to their customers, or am I missing something?
It is going to be incredibly difficult to bill outrageous amounts for armies of consultant to implement or customise the product when agents can do the same for much less, or at-least a 5-10x reduction in headcount for similar complexity of changeset.
If anyone is in the industry, please feel free to chime in as to what you are seeing on the ground.