github.com
GitHub - edwardclewer/tick_backtest: Deterministic, YAML-driven backtester (Python/Cython) with vectorised data ingestion; per-run manifests, NDJSON logs, and trade-level Parquet output. Snapshots entry-time metrics and signals while computing stratified expectancy. 8m ticks/minute single thread per
Deterministic, YAML-driven backtester (Python/Cython) with vectorised data ingestion; per-run manifests, NDJSON logs, and trade-level Parquet output. Snapshots entry-time metrics and signals while computing stratified expectancy. 8m ticks/minute single thread performance. - edwardclewer/tick_backtest
2
Reposts
3
Likes
4
Replies
have you applied this passion to other fields? graphics? molecular dynamics? servers? machine learning backend?
or are you locked in on quanta?
or are you locked in on quanta?
Reply
Loading replies...
Thanks for the thoughtful post, glad you enjoyed the video and I appreciate your comment with regards to discourses!
It’s awesome that you have that experience and know the space you want to operate in that’s half the battle, especially having the taste of academia and know where you’d want to put forth effort (not grinding pub points etc…)
Building cool (and useful) projects is resume fuel but the pivot to interviewing is not as clear, here’s what I’ve found:
- networking should take priority, building projects is great but TALK to people that can use them or have thoughts on extensions or their place in industry or what else needs to be built or done
- there is a tremendous amount of room in every industry for new and alternative products
- interviewing takes reps just like networking, “when you’re ready” is really about when you want to focus on building it as a skill taking the time to allocate toward progress in that space (the literal act of acquiring a role or project contract)
Hope this is useful happy to elaborate more
It’s awesome that you have that experience and know the space you want to operate in that’s half the battle, especially having the taste of academia and know where you’d want to put forth effort (not grinding pub points etc…)
Building cool (and useful) projects is resume fuel but the pivot to interviewing is not as clear, here’s what I’ve found:
- networking should take priority, building projects is great but TALK to people that can use them or have thoughts on extensions or their place in industry or what else needs to be built or done
- there is a tremendous amount of room in every industry for new and alternative products
- interviewing takes reps just like networking, “when you’re ready” is really about when you want to focus on building it as a skill taking the time to allocate toward progress in that space (the literal act of acquiring a role or project contract)
Hope this is useful happy to elaborate more
Reply
Loading replies...