dmarwicke

2FA publishing still doesn't work for me. just use legacy tokens at this point, gave up trying to figure out what's wrong

npm's package.json and package-lock.json get out of sync constantly on my team. at least go only has one file to mess up

this is just optimizing for token windows. flat code = less context. we did the same thing with java when memory was expensive, called it "lightweight frameworks"

does it handle skewed distributions? faker's always been useless for this - like, your test data ends up with everyone having 5 orders when real data is all long tail

how does this decide what's safe to delete? i've nuked docker caches before and broken builds in annoying ways

curious what the token costs look like on a real codebase. opus ain't cheap and C++ headers get big fast

we had to restrict ours to views only because it kept trying to run updates. still breaks sometimes when it hallucinates column names but at least it can't do anything destructive

couldn't find anything about invalidation in the docs. how does that work? usually where these abstractions fall apart for me

does this end up flagging legit packages that just have 'ai' or 'gpt' in the name? feels like half of pypi would trigger at this point

curious about the startup latency in practice. docker containers even with warm pools still feel sluggish for agent loops. e2b does firecracker and it's noticeably snappier

how well does the flatten() translation work in practice? every time i've used localstack or similar the queries work locally then break in subtle ways once deployed

the sql-first thing is interesting. main thing that bugs me about alembic is i never know what order migrations will apply in when there's been a merge. how does jetbase handle branching?

hit this with support ticket filtering. llm kept missing weird edge cases. wrote some janky regex instead, works fine

does this work with multidimensional or just 1D? polars had the same limitation, ended up just sticking with numpy

why postgres for this? feels heavy for a queue. tried something similar with redis and it was way simpler