ok, so im "vibe-" building out my company's lab notebook in elixir ahead of the first funding check coming in.

im doing some heavy duty shit, almost everything is routed through a custom CQRS-style events table before rollup into the db tables (the events are sequentially hashed for lab notebook integrity). editing is done through a custom implementation of quill js's delta OT. 100% of my tests are async.

I've never once run into the ecto issues mentioned.

I haven't had issues with genservers (but i have none* in my project).

claude knows oban really well. Honestly I was always afraid to use oban until claude just suggesting "let's use oban" gave me the courage. I'll be sending Parker and Shannon a first check when the startup's check comes in.

article is absolutely spot on on everything else. I think at this point what I've built in a month-ish would have taken me years to build out by myself.

biggest annoyance is the over-defensiveness mentioned, and that Claude keeps trying to use Jason instead of JSON. Also, Claude has some bad habits around aliases that it does even though it's pretty explicitly mentioned in CLAUDE.md, other annoying things like doing `case functioncall() do nil -> ... end` instead of `if var = functioncall() do else`

*none that are written, except liveviews, and one ETS table cache.

[0] CQRS library: https://hexdocs.pm/spector/Spector.html

[1] Quill impl: https://hexdocs.pm/otzel/Otzel.html