SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Developer Fixes Three Stop-Loss Bugs That Caused Trading Bot to Lose Money on Short Trades

0
·1 views

A developer building an open-source algorithmic trading engine called Rook discovered three separate bugs that caused the system to place stop-losses below entry prices on short trades, offering no capital protection. All three bugs shared the same root cause: the short-trade logic had been incorrectly written as if it were handling long trades. The errors went undetected because the engine had been primarily tested on long trades, and only surfaced during a live short trade on S10 at $75,359, which was immediately stopped out. The fixes involved correcting the type of Fair Value Gap being targeted, inverting a flawed validation guard, and adding a directional check to ensure stop anchoring logic accounts for trade direction. The patch was released as commit 6207318 in the Rook Engine's open-source repository.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Developer builds open-source lab to benchmark SSG, SSR, and ISR on real WordPress sites

A developer has released astro-wp-seo-lab, an open-source test environment that builds the same WordPress content using four rendering strategies in Astro 5.1.1 and serves them simultaneously for direct comparison. The project covers static site generation, server-side rendering, CDN-cached SSR, route caching, and an islands architecture, each running on a separate local port. A visible timestamp on every page acts as a practical instrument to observe whether content was rendered at build time or per request. Testing revealed that static pages delivered identical timestamps across reloads while SSR pages regenerated on every request, and the islands arm showed lower SEO parity due to deferred JavaScript fragments missing from raw HTML. The lab also highlights crawlability risks, noting that JS-only content may be indexed days late or missed entirely by non-Google crawlers, including most AI-driven bots.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Engineering Team Cuts RAG Pipeline Latency 40% Using Bayesian Search and Hybrid Retrieval

A development team rebuilt their Retrieval-Augmented Generation (RAG) pipeline from scratch after standard 512-token chunking and basic vector search proved inadequate in production environments. The team adopted document-specific chunking strategies — including recursive, semantic, and agentic methods — tailored to content types such as legal contracts, API docs, and support tickets. They replaced pure vector search with a hybrid retrieval system combining vector search, BM25, and cross-encoder reranking, achieving up to 97% recall@10 across document categories. A query transformation layer was also introduced to handle poorly formed user queries before retrieval. The combined optimizations resulted in a 40% reduction in query latency and significantly more reliable retrieval at scale.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Why 'App Readiness' Means Different Things to Founders, CTOs, and Investors

As AI accelerates software development, the harder challenge is no longer building applications but determining whether they are truly ready for their intended business purpose. Different stakeholders — founders, CTOs, engineering leaders, acquirers, and investors — each define readiness through the lens of their own responsibilities and risks. Traditional code assessments focus on architecture, security, and technical debt, but these metrics alone do not capture whether software is fit for its specific business context. An internal tool serving dozens of employees, for instance, warrants a very different evaluation than a SaaS platform targeting thousands of users. The author argues that application readiness should be measured against business objectives, scalability needs, and operational risks — not just code quality.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

How to Run Separate Personal and Work Claude Code Accounts on One Machine

A developer has shared a simple method for isolating two Claude Code accounts on the same machine, keeping personal and work environments completely separate. The approach relies on Claude Code's built-in support for the CLAUDE_CONFIG_DIR environment variable, which redirects the app to a different config directory. By defining two shell functions in .zshrc, each pointing to its own config folder, the user ensures credentials, MCP servers, hooks, and session history never mix between accounts. The developer notes this avoids risks like work tokens leaking into personal sessions or internal MCP server hooks firing in the wrong context. While the trade-off is that settings must be updated in both accounts independently, the author considers this a minor inconvenience compared to the security and clarity gained.

0 comments Read more at DEV Community