Measure before opinion
No architectural or modelling claim leaves this team without evidence behind it. Intuition sets the hypothesis; the data decides.
About
Statistics and systems, same team.
Shadows Technologies started from one combination: systems engineering and the mathematical modelling of financial markets. Every member brings 10+ years of developing high-performing, data-intensive applications across a wide range of industries, including the financial sector, logistics and manufacturing.
We construct new software, and we audit and improve the systems companies already depend on. Quantitative work sets the target and engineering meets it, which is why our estimates arrive with error bars and our services arrive with benchmarks.
Practice profileLive
- Founded on
- systems engineering + market modelling
- Team
- senior analyst-engineers only
- Disciplines
- statistics · modelling · systems · audits
- Sectors
- finance · logistics · manufacturing · accounting
- Working language
- yours, 9 languages in production
- Contact
- engineering@shadowstech.io
Principles
Four rules we don't bend.
Senior only, on the tools
The person in the kick-off call is the person writing the code. No pyramid, no handover, no discovery phase billed as delivery.
Repair before rewrite
Rewrites are a last resort with a price tag. We would rather return 70% of the cost inside the code you already trust.
Leave capability behind
Benchmarks, gates and written design records stay in your repository. The improvement should outlive the engagement.
Quantitative foundation
Half of this practice is statistics.
The founding pairing was systems engineering and mathematical modelling of financial markets. In practice that means we treat every production system as a measured process: expectation, variance, and a rule for when reality has left the model.
Modelled expectation vs observed behaviour observed model ±2σ
- σ of residuals
- 1.40
- flagged points
- 2
- window
- 24 intervals
Excursions beyond two sigma are flagged and investigated. Most turn out to be infrastructure, which is precisely why the two disciplines belong together.
Toolbox
The languages we take responsibility for.
LanguageDepth
C++ (17/20/23)Hot paths, lock-free structures, SIMD
RustGateways, parsers, safe systems services
Java / JVMPlatforms, GC and JIT tuning
C#/.NETBack-ends, allocation reduction
GoDistributed services, ingest
PythonTooling, research, native bindings
TypeScriptReal-time UI, operator consoles
SQL / PL-pgSQLPlans, indexing, partitioning
CEmbedded and kernel-adjacent work