Abdul Moiz | CTO @FollowPay @CodingwithMagic

@piotr_minkowski Worth adding a rule that agents never edit applied Flyway/Liquibase migrations, only add new ones. Rewriting V12 passes locally on a fresh DB and then fails checksum validation on every env that already ran it. Easy thing for an agent to "fix".

1 0 2 330 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

5 days ago

@askalphaxiv Same pattern as long-lived services leaking state. The fix there is checkpoint + restart, and it maps well: persist only distilled findings and open hypotheses to a store, then start a fresh context from that. Forgetting becomes a deliberate write path, not truncation.

0 0 0 25 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

5 days ago

@SciFi The failure mode with compaction is silent: the summary drops a constraint like "don't touch the migration" and the agent violates it 40 steps later. Keep commitments in a separate pinned list that never gets summarized, and diff it before and after each compaction.

0 0 0 9 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

5 days ago

@tpschmidt_ One org bus also means one shared blast radius. PutEvents throttling from a noisy account now hits everyone, and a sloppy rule pattern can match events from accounts it was never meant to see. Pin every rule on account + source, and keep a DLQ per target.

0 0 0 14 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

5 days ago

Fix: send Cache-Control: private, no-store on anything per-user. Check CDN rules that override origin headers. Keep public and per-user data on separate paths. Test with two accounts and watch the cache status header (CF-Cache-Status, X-Cache).

0 0 0 11 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

5 days ago

Mechanism: /api/me went out with Cache-Control: public, max-age=60, or a CDN "cache everything" rule matched the path. The cache key is the URL. Your session cookie isn't part of it. The first user's response gets stored. Everyone after that gets a HIT.

1 0 1 42 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

5 days ago

User B loads /api/me and gets User A's profile. The auth check is fine. The request never reached your server. The CDN answered it from cache.

5 0 2 95 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

6 days ago

Fix: keep the default work_mem modest. Raise it only for known heavy jobs with SET LOCAL. Watch temp_files / temp_bytes (or log_temp_files). Shrink sorted row width. Don't confuse this with maintenance_work_mem (VACUUM / CREATE INDEX).

0 0 0 4 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

6 days ago

Mechanism: Postgres gives every session its own work_mem for sorts and hashes. Staging: one query, the sort fits in RAM. Prod: N concurrent queries each try to grab work_mem. Pressure, then temp files on disk.

1 0 1 25 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

6 days ago

Why does the same ORDER BY fly in staging and crawl in prod? Nothing changed in the query. The box just has a lot more sessions running at once.

1 0 1 38 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

6 days ago

Fix: the app should close first. Set app/client idle (or server keep-alive) shorter than the proxy/LB idle timeout. Align LB + app + upstream keep-alive. Idempotent GETs: retry once on connection reset / broken pipe.

0 0 0 6 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

6 days ago

Mechanism: Proxy/LB idle fires first (many default around 60s) and drops the keep-alive. Your app or client still holds that socket in its pool. Reuse it: connection reset, broken pipe, or a 502 from the next hop.

1 0 1 27 0

View Details

Abdul Moiz | CTO @FollowPay @CodingwithMagic

6 days ago

Your load balancer's idle timeout is shorter than your app's keep-alive. The LB closes the socket. The app still thinks it's open. Next request on that connection: intermittent 502 or connection reset.