⭐ 𝗣𝗔𝗥𝗧 𝟯 — 𝗪𝗵𝗲𝗿𝗲 𝗔𝗜 𝗦𝘁𝗿𝘂𝗴𝗴𝗹𝗲𝘀 (𝗮𝗻𝗱 𝗪𝗵𝘆 𝗦𝗲𝗻𝗶𝗼𝗿 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗠𝗮𝘁𝘁𝗲𝗿)

𝗔𝗜 𝗮𝗰𝗰𝗲𝗹𝗲𝗿𝗮𝘁𝗲𝘀 — 𝗯𝘂𝘁 𝗶𝘁 𝗱𝗼𝗲𝘀𝗻’𝘁 𝘂𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻.
𝐈𝐭 𝐡𝐞𝐥𝐩𝐞𝐝 𝐚 𝐥𝐨𝐭 — 𝐛𝐮𝐭 𝐢𝐭 𝐚𝐥𝐬𝐨 𝐦𝐢𝐬𝐬𝐞𝐝 𝐭𝐡𝐢𝐧𝐠𝐬 𝐭𝐡𝐚𝐭 𝐨𝐧𝐥𝐲 𝐞𝐱𝐩𝐞𝐫𝐢𝐞𝐧𝐜𝐞 𝐜𝐚𝐭𝐜𝐡𝐞𝐬.

𝗘𝗱𝗴𝗲 𝗰𝗮𝘀𝗲𝘀
AI suggested basic heartbeat handling but missed a key nuance: stale detection must be per‑channel, not global.

My initial implementation cleared all stale flags when any message arrived.
That keeps the UI green — but it hides channel‑specific failures.

Bitfinex channels can fail independently, so each subscription needs its own stale timer.

That’s the kind of detail you only learn by shipping real systems.

𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝘁𝗿𝗮𝗱𝗲‑𝗼𝗳𝗳𝘀
AI defaulted to slice() everywhere.
I knew splice() was better for high‑frequency, in‑place updates.

𝗔𝗣𝗜 𝗾𝘂𝗶𝗿𝗸𝘀
Bitfinex sends different formats for snapshots vs updates.

AI understood the idea, but not the exact formats — for example:

• Snapshot: [channelId, [trade1, trade2]]
• Update: [channelId, 'te', trade]

These quirks matter. They break your parser if you don’t know them.

𝐌𝐞𝐦𝐨𝐫𝐲 𝐦𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭
AI didn’t understand memory‑bounded arrays.

Without limits, 8 hours of trading data becomes:
288,000 updates × 10 pairs = a multi‑GB memory leak.

The app enforces:

• MAX_TRADES = 1000
• MAX_CANDLES = 5000

This keeps memory stable at ~60MB instead of creeping past 2GB and crashing.

𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻 𝗰𝗼𝗻𝗰𝗲𝗿𝗻𝘀 𝐀𝐈 𝐝𝐢𝐝𝐧’𝐭 𝐜𝐨𝐧𝐬𝐢𝐝𝐞𝐫

• Handler‑based architecture (trades, tickers, candles, book)
• 90‑second stale timeouts with 30‑second monitoring intervals
• Exponential backoff (5 attempts, increasing delays)
• Performance tracking via performanceTracker.updateLatency()
• Environment‑configurable limits (VITE_MAX_TRADES)

These aren’t “nice to haves” — they’re what keep real‑time systems alive.

𝐓𝐡𝐞 𝐫𝐞𝐚𝐥𝐢𝐭𝐲
Building a crypto trading dashboard made one thing clear:

AI is incredible at scaffolding — but production‑grade real‑time systems require architectural judgment that only comes from experience.

AI accelerates — but it doesn’t understand production.
That’s where senior engineers still make the difference

𝗪𝗿𝗶𝘁𝘁𝗲𝗻 𝗯𝘆 𝗥𝗶𝗰𝗮𝗿𝗱𝗼 𝗦𝗮𝘂𝗺𝗲𝘁𝗵
𝗦𝗲𝗻𝗶𝗼𝗿 𝗙𝗿𝗼𝗻𝘁‑𝗘𝗻𝗱 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 | 𝗥𝗲𝗮𝗹‑𝗧𝗶𝗺𝗲 𝗨𝗜 𝗦𝗽𝗲𝗰𝗶𝗮𝗹𝗶𝘀𝘁