주제: Trading Bot

홈으로

  • A Beginner Trading Bot UI: Clear Stop Intent and Order Outcomes

    한국어로 읽기 TECH INSIGHT / EXPLAINED A beginner needs three answers from a trading panel: is the information current, what will this action change, and where can its outcome be checked? A screen answering those questions makes mistakes easier to notice than one simply displaying more numbers.

  • GAS PropertiesService: Scope, Validation, and Recovery for Small State

    한국어로 읽기 TECH INSIGHT / EXPLAINED A few dozen settings do not require operating a database. PropertiesService is convenient for small string-based state. Its storage contract still needs to define execution identity, input types, concurrent changes, and size limits.

  • Minute Triggers in GAS: Runtime Budgets and Overlap Prevention

    한국어로 읽기 TECH INSIGHT / EXPLAINED A 54-second loop inside a minute trigger can look almost continuous. Its practical constraints are daily runtime and overlapping executions, more than the six-minute per-run limit. Decide the required observation frequency before filling the available time.

  • Monthly-Distribution ETF Rotation: Separate Dates, Returns, and Order State

    한국어로 읽기 TECH INSIGHT / EXPLAINED Writing “rotate from the mid-month ETF to the month-end ETF” on a calendar is different from specifying executable orders. Dates, distribution eligibility, fills, and total return need separate representations. This article turns a two-instrument idea into testable states and calculations, without recommending a product or claiming profitability.

  • A Chrome Extension Bot Panel: Permissions, State, and Stop Controls

    한국어로 읽기 TECH INSIGHT / EXPLAINED Putting every bot metric in a tiny popup makes the stop control harder to find. Treat the extension as a remote control: show current state, its freshness, explicit start and stop actions, and the result of saving settings.

  • Google Apps Script Backend: Execution Budgets and Operating Boundaries

    한국어로 읽기 TECH INSIGHT / EXPLAINED Before building an order engine, build a small backend that reads prices periodically and keeps configuration. Google Apps Script lowers the cost of that experiment. A scheduled job, however, has a different operating model from a continuously running server.

  • Evaluating Crypto Bot Profits: Fees, Open Inventory and Evidence

    한국어로 읽기 TECH INSIGHT / EXPLAINED A bot-profit claim needs records: the test period, deposits and withdrawals, trades, fees and open inventory. Without them, a smooth backtest curve cannot establish realized account performance.

  • Python vs Go for Trading Bots: Compare Workloads, Not Slogans

    한국어로 읽기 TECH INSIGHT / EXPLAINED Choose a language by the workload you can measure and the code you can maintain. Research notebooks, CPU-heavy calculations and long-running network services ask different questions.