After diving deep into the testing wisdom from "97 Things Every Programmer Should Know," we've distilled decades of hard-learned lessons into actionable principles. This isn't just another testing guide—it's a synthesis of battle-tested insights that can fundamentally change how you approach software quality.
Critical Finding: Bybit demo and live trading use IDENTICAL API endpoints and IDENTICAL trading rules. The ONLY difference is the domain:
https://api.bybit.comhttps://api-demo.bybit.comThis is not an accident - it's intentional design for seamless transition.
After deep architectural analysis, we've discovered the true competitive advantage of Mercury's instance system:
Key Insight: Shadow portfolio's value isn't simulation—it's complete data capture for strategy optimization that demo trading cannot provide.
This is a monorepo-wide architectural problem, not specific to Mercury. Across multiple domains, we've evolved complex optional nested structures that force developers to bypass TypeScript's type safety. The Mercury tournament configurations are just one example of this systemic issue.
"Внимание, говорит Москва! Передаем важное правительственное сообщение. Граждане и гражданки Советского Союза! Сегодня 22 июня, без объявления войны, type cast войска атаковали границы kaido-monorepo. Началась Великая Отечественная война советского народа против немецко-фашистских захватчиков кода хуевыми паттернами. Наше дело правое. Враг будет разбит. Победа будет за нами."
In an industry obsessed with fleeting frameworks and hype-driven development, some wisdom is timeless. "97 Things Every Programmer Should Know" is a collection of such wisdom. It's not about a specific language or technology, but about the fundamental principles of crafting good software.
But principles are useless without practice. Here's how we're turning these lessons into tangible, enforceable rules in our monorepo.
Modern codebases are complex beasts that require constant vigilance to maintain quality. While linters catch syntax issues, code smell detection tools go deeper - identifying maintainability problems, architectural issues, and technical debt before they become expensive to fix.
For weeks, our Docker builds were a nightmare:
The error was always the same: dist directories missing, library dependencies not found, Nx claiming projects didn't exist that clearly existed.
After months of architectural development, Mercury reached a critical milestone: all core components were implemented and operational. We transitioned from building the foundation to the fine-tuning phase—optimizing our AI-powered trading system for maximum profitability. However, this phase revealed significant challenges in our experimental framework that ultimately hindered progress rather than accelerating it.