Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Deciding whether speed matters for your strategy
Cutting latency from 50 microseconds to 5 costs real money in hardware, colocation and engineering time, and it only pays when the strategy's edge decays within that window. Measuring how quickly your signal's value fades after a market event tells you whether to chase nanoseconds, settle for a well-tuned ordinary host, or spend the effort on research instead.
First tasks
- Pick one strategy and list the market events its signal reacts to
- Re-run its simulation with reaction delays from 1 microsecond to 10 milliseconds
- Estimate the yearly cost of each latency tier you could reach
- Write the one-page speed decision and share it with the strategy owner
End-to-end latency budget for the trading path
Without a budget, every engineer tunes the part they know best and nobody notices the 30 microseconds lost in a logging call. Splitting the target tick-to-trade time into allowances for the wire, the NIC, the feed handler, the strategy, risk checks and the order gateway makes each component's owner answerable for a number.
First tasks
- Write the median and 99th percentile tick-to-trade targets at the top of a budget page
- List every stage between packet arrival and order on the wire
- Give each stage an allowance and an owner
- Commit the budget to the repository beside the trading code
Inventory of the tick-to-trade path
Few teams can draw their own critical path from memory, and the forgotten hop, a spare switch, a bonding driver, a shared logging thread, is usually where latency hides. A diagram of every cable, device, process and thread a packet touches, with versions, is the map every later measurement and change depends on.
First tasks
- Sketch the path from exchange handoff to outbound order in one diagram
- List every thread on the path with its pinned core
- Record firmware, driver and kernel versions for each device
- Assign an owner to each unknown hop on the diagram