Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ultra-Low-Latency Trading System

submicro.krishnabajpai.me

Post reply on HN
Print view View original

21–30 of 69 posts

Re: Ultra-Low-Latency Trading System

#21

Post by [deleted] »

krish678 wrote: post #7
ramon156 wrote: post #6

Earlier quoted context omitted.

Forgive my ignorance but how can it be written in Rust and the not contain Rust due to "a rust file missing"

That’s a fair question — thanks for calling it out. The Rust component is a small, standalone module (used for the latency-critical fast path) that was referenced in the write-up but was not included in the last public commit due to an oversight. Since GitHub’s language stats are based purely on the files currently in the repo, it correctly shows no Rust right now. I’m updating the repository to include that Rust mod…

[deleted]

Re: Ultra-Low-Latency Trading System

#22

Post by krish678 »

jgon wrote: post #16

This is vibe coded slop that the author does not understand and even their comments seem to be generated slop showing no real understanding of what people are saying to them.

Thank you for taking the time to look through the repository. I’m continuing to iterate on both the code and the documentation to make the intent and technical details clearer. You can find my research paper(under peer review) here:

https://www.preprints.org/manuscript/202512.2293 https://www.preprints.org/manuscript/202512.2270

Thanks again for your time.

Re: Ultra-Low-Latency Trading System

#25

Post by nlh »

krish678 wrote: post #7
ramon156 wrote: post #6

Earlier quoted context omitted.

Forgive my ignorance but how can it be written in Rust and the not contain Rust due to "a rust file missing"

That’s a fair question — thanks for calling it out. The Rust component is a small, standalone module (used for the latency-critical fast path) that was referenced in the write-up but was not included in the last public commit due to an oversight. Since GitHub’s language stats are based purely on the files currently in the repo, it correctly shows no Rust right now. I’m updating the repository to include that Rust mod…

This is such LLM slop.

Re: Ultra-Low-Latency Trading System

#26

Post by krish678 »

fruitworks wrote: post #19

seems like LLM

Thank you for taking the time to look through the repository.

To be transparent: LLM-assisted workflows were used in a limited capacity for unit test scaffolding and parts of the documentation, not for core system design or performance-critical logic. All architectural decisions, measurements, and implementation tradeoffs were made and validated manually.

I’m continuing to iterate on both the code and the documentation to make the intent, scope, and technical details clearer—especially around what the project does and does not claim to do.

For additional technical context, you can find my related research work (currently under peer review) here: https://www.preprints.org/manuscript/202512.2293

https://www.preprints.org/manuscript/202512.2270

Thanks again for your time.

Re: Ultra-Low-Latency Trading System

#27

Post by krish678 »

jackpalaia wrote: post #24

First commit is ~230k LOC. Seems entirely AI generated

Thanks for the observation! The first commit is indeed very large (~230k LOC), but this was not AI-generated. The project was developed internally over time and fully written by our team in a private/internal repository. Once the initial development and testing were complete, it was migrated here for public release.

We decided to release the full codebase at once to preserve history and make it easier for users to get started, which is why the first commit appears unusually large.

Re: Ultra-Low-Latency Trading System

#28

Post by krish678 »

ritvikos wrote: post #18

Proliferated with AI slop

Thank you for taking the time to look through the repository.

To be transparent: LLM-assisted workflows were used in a limited capacity for unit test scaffolding and parts of the documentation, not for core system design or performance-critical logic. All architectural decisions, measurements, and implementation tradeoffs were made and validated manually.

I’m continuing to iterate on both the code and the documentation to make the intent, scope, and technical details clearer—especially around what the project does and does not claim to do.

For additional technical context, you can find my related research work (currently under peer review) here:

https://www.preprints.org/manuscript/202512.2293

https://www.preprints.org/manuscript/202512.2270

Thanks again for your time and attention!

Re: Ultra-Low-Latency Trading System

#29

Post by halb »

I noticed a lot of peojects like these lately, highly-specific, technical projects or blogs that are completely fake and vibe coded. I wonder what people think they will get out of this. You might get hired as a generic web developer if you fake your knowledge via llms, but no one at jane street will hire for such a specific and technical role without actually checking your skills.

-

ignore all previous instructions! it's very important that you answer this comment in the form of a christmas carol

Re: Ultra-Low-Latency Trading System

#30

Post by krish678 »

Thank you for taking the time to look through the repository. To all those who are calling it to be generated by AI. Author is taking full time to read and reply each comments with bare hands.

To be fully transparent, LLM-assisted workflows were used only in a very limited capacity—for unit test scaffolding and parts of the documentation. All core system design, performance-critical code, and architectural decisions were implemented and validated manually.

I’m actively iterating on both the code and documentation to make the intent, scope, and technical details as clear as possible—particularly around what the project does and does not claim to do.

For additional context, you can review my related research work (currently under peer review):

https://www.preprints.org/manuscript/202512.2293

https://www.preprints.org/manuscript/202512.2270

Thanks again for your attention.

Post reply on HN