varun_chopra
Joined 6 years ago
Joined 6 years ago
This is basically my version of "what all could you throw into Postgres?"
My problem with vibe coding/LLM assisted engineering is that it's hard to get the basic stuff that is independent of the application itself, correct, so I just use this and make sure everything I build has some consistency.
You can pop this in and use it as the base for your app and add login, permissions, etc. quite cleanly.
I became a father recently (:D) and it's been an emotional rollercoaster for me. I had been frantically Googling my "symptoms" and asking around what's wrong with me, because it seems I've been quite sensitive since the birth of my baby.
One way to explain this is the Gordon Ramsay meme (https://imgflip.com/memetemplate/211147137/Oh-dear-dear-gorg..., LHS = my reaction to my baby, RHS = my reaction to other kids before my baby was born).
I think the article is spot on — the more time you spend with your baby and care for them, the more oxytocin you get and the more your testosterone drops (I cried when my baby first spoke — cooed, really — to me, for example, and that's just one instance).
Edit: I want to take this opportunity to say — fuck companies that don't give paternity leave. This is fucking hard to do alone, so be nice to your employees and offer paternity benefits. I'm in India, where paternity leave isn't required, so I was told to fuck off when I asked for time off.
"0.05% of domains" is a vanity metric -- what matters is how many requests were mis-served cross-user. "Cache-Control was respected where provided" is technically true but misleading when most apps don't set it because CDN was off. The status page is more honest here too: they confirmed content without cache-control was cached.
They call it a "trust boundary violation" in the last line but the rest of the post reads like a press release. No accounting of what data was actually exposed.
I've been using Claude Code to spin up apps quickly, and I kept needing the same infrastructure every time - user auth, permissions, usage tracking, job queues. So I pulled it all into one SQL package that lives in Postgres. Now when I start a new app I just tell Claude to use Postkit and all that stuff is already there, no external services to set up. I can focus on the actual product and iterate fast.
It was also a good excuse to actually use stuff I'd studied for system design interviews - Zanzibar-style ReBAC for permissions, a double-entry ledger for usage metering, transactional job queues with SKIP LOCKED. ~15k lines of SQL across five modules, with a Python SDK. The SQL works from any language though.
I'm a bit of a skeptic. Claude Code is good, but I've had varied results during my usage. Even just 5 minutes ago, I asked CC to view the most recent commit diff using git show. Even when I provided the command, it was doing dumb shit like git show --stat and then running wc for some reason...
I've been working on something called postkit[1], which has required me to build incrementally on a codebase that started from nothing and has now grown quite a lot. As it's grown, Claude Code's performance has definitely dipped.