Abdul Moiz | CTO @FollowPay

I ship backends with agents. I post what I still won’t let them touch.

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@NotionHQ You are not firing? 🌝🌝😂😂

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@girlxid where to go?

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

Me: Claude, can you fix one small bug for me?

Claude: Done! I also redesigned your entire codebase.

Me: 💀 WHO ASKED YOU TO TOUCH EVERYTHING?

The App: #̢̛ͥ̀̽̽ͨ̌̓͆̇̀̽ͦͨͫͯ̏̎̇̈̚͜҉̕͢͏͡҉̸̶̛͢͡҉̵̨̭̳̘̹̫͔͖̜̠͖̫̲̖̱̤̻̖͉͢͞͡ͅͅ͏̸̷̢͑̊̀̐ͣͭͭ̉͂ͨ̽͒̊̎͛ͪ̊̎ͩͧ̀͝͠͠͏̸̵̵̷̵

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@FlokiBull_ @twxpicker Thank you so much ☺️

[Crypto Whale 🐋 @FlokiBull_]

Drop your #SOL address 👇

I will send you $820 in 24h❤
(Yes for real )

RT and Follow🔥

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@FlokiBull_ 8XXf3AYcvq9baQkqbH6DEgm2DLtoJ3a3xsg6Qe1dppBW

[Crypto Whale 🐋 @FlokiBull_]

quick 60min giveaway

3 x $10 each

🎁 RT + Stake ID

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@FlokiBull_ Stake : Itxmoizdev

[Crypto Whale 🐋 @FlokiBull_]

Send your Solana (SOL) wallet address below 👇

Repost ♻️

I’m giving away FREE $SOL

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@FlokiBull_ 7JPdbykrvA36SWddMzLMpXVNwU25gSZVASDco3oiNvP4

[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".

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@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.

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@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.

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

@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.

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

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).

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

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.

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

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.

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

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).

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

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.

[Abdul Moiz | CTO @FollowPay @CodingwithMagic]

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.