Qm

Topic · Quant Development & Systems

← All topics

Data Engineering

27 articles · 4 checkpoints · 17 deeper reads · 6 reference notes

Every article, in reading order

plant a flag as you finish each

Read these first

  1. Tick data records every individual trade or quote update as it happens; bar data compresses a time window into open/high/low/close summary numbers. The choice between them is a bandwidth-versus-information tradeoff that shapes what a strategy can even see.

  2. Columnar formats like Parquet store all values of one column together instead of one row at a time, which makes 'scan a billion timestamps and one price column' fast and compressible in a way row-oriented storage never can be.

  3. Splits, dividends and other corporate actions create artificial jumps in a raw price series. A price feed engineer applies backward-looking adjustment factors so that a return computed across the jump reflects what an investor actually earned, not a data artifact.

  4. A point-in-time database can answer not just 'what is true now' but 'what did we believe was true as of last Tuesday,' which is the only honest way to backtest a strategy that would have used data as it looked in the past, restatements and all.

Then the rest

Reference notes6 short entries