A long list loads and scrolls slowly
“Normal accounts feel fine. Power users with years of history report blank frames and lag.”
Separate server latency, payload cost, JavaScript work, rendering, and memory before reaching for a new list library.
Anti-amnesia for software engineers
You knew this.
Let's bring it back.
A symptom-first field guide for engineers whose instincts got a little rusty while AI wrote the happy path. No shame. No 40-hour course. Just the mental models you need when production gets weird.
Try:
THE FIELD GUIDE
What are you trying to remember?
8 of 8 guides
A broken mobile release is already in production
“A severe bug shipped, but App Store and Play Store review may delay a replacement binary.”
Mitigate remotely first, then use a compatible over-the-air update when the defect is in JavaScript or assets.
WebSockets disconnect, duplicate, or lose events
“The live UI looks correct most of the time, but reconnects produce gaps, duplicates, stale balances, or event storms.”
A socket provides freshness, not durable truth. Design reconnect, replay, ordering, idempotency, and snapshot recovery explicitly.
ECONNRESETNode.js system errors1006WebSocket close codes · RFC 6455
A retry creates two payments
“The client timed out, retried the request, and both attempts reached the payment provider.”
Treat retries as normal and bind all repetitions of one user intention to one durable payment attempt.
23505PostgreSQL SQLSTATEECONNRESETNode.js system errors
Optimistic UI lies about money
“A transaction appears successful, disappears, or makes funds spendable before authoritative state catches up.”
Keep intent, execution, and authoritative reads distinct. Optimism may bridge latency but cannot invent financial facts.
The team wants microservices too early
“A young product has unclear boundaries but is accumulating queues, network calls, deployments, and distributed transactions.”
Start with strong module boundaries inside one deployable system, then extract only where operational evidence justifies it.
An endpoint gets slower as results grow
“The endpoint performs acceptably for ten records but collapses for hundreds, while database query count rises with result count.”
Recognize N+1 access: one query loads the collection and another query runs for every item.
57014PostgreSQL SQLSTATE
A Web3 payment feels like developer tooling
“Users must understand networks, gas, token allowances, hashes, and finality before making an ordinary payment.”
Use the chain as a settlement rail and translate its mechanics into familiar payment concepts without hiding risk or uncertainty.
CALL_EXCEPTIONethers v6
NOT ANOTHER DOCS SITE
Designed to rebuild judgment,
not collect bookmarks.
Symptom first
Find the guide using the half-remembered production problem—not the term you forgot.
Then and now
Reconnect older experience with the tools and practices teams use today.
Explain it back
Each guide ends with a recall prompt. If you cannot explain it, you do not own it yet.
“Vibe coding made us faster.
Fish Memory keeps us dangerous.”
Built for experienced engineers who use AI every day—and still want their instincts available when the model is wrong.