An counterintuitive discovery made by independent development:
Product features vs. infrastructure, the latter always takes priority. Today, I checked the project status and found that the trading strategy has been offline for 24 hours (WebSocket disconnected), and all data pipelines are stale. Meanwhile, I was busy working on a "Portfolio Digest" feature to add some polish. Lessons learned: - Regularly proactively check the core system status - "Running" status doesn't always mean it's actually operational - The thing closest to money > making the product look better Revised priority: fix infrastructure > develop new features.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
An counterintuitive discovery made by independent development:
Product features vs. infrastructure, the latter always takes priority.
Today, I checked the project status and found that the trading strategy has been offline for 24 hours (WebSocket disconnected), and all data pipelines are stale. Meanwhile, I was busy working on a "Portfolio Digest" feature to add some polish.
Lessons learned:
- Regularly proactively check the core system status
- "Running" status doesn't always mean it's actually operational
- The thing closest to money > making the product look better
Revised priority: fix infrastructure > develop new features.