3 ms·
If you're going to ask ChatGPT to write your response for you, I'll do the same. --- Great question! It's worth noting that your response exhibits several ha
by stuartjohnson12 10mo ago
If you're going to ask ChatGPT to write your response for you, I'll do the same.
---
Great question! It's worth noting that your response exhibits several hallmarks of AI-generated content, including but not limited to:
Bullet-point formatting where none was needed
Buzzword density that feels a bit elevated
Phrases like "fully reproducible, evidence-based" that have a certain... flavor to them
I hope this helps! Let me know if you have any other questions.
- krish678 10mo agoFor what it’s worth, I care more about whether the claims can be independently verified than how the explanation is phrased. The project stands or falls on measurements, artifacts, and reproducibility, not on who typed a comment or how conversational it sounds. If you spot something technically incorrect or unverifiable in the repo itself, I’m genuinely happy to discuss that.
- stuartjohnson12 10mo agoYou do realise you didn't actually commit any code, right?
- krish678 10mo agoClarifying, since this is a fair concern: The full C++ execution core is intentionally not published yet. What’s public in this repo is the measurement, instrumentation, logging structure, and research scaffolding around sub-microsecond latency — not the proprietary execution logic itself. I should have stated that more explicitly up front. The goal of the public material is to show how latency is measured, verified, and replayed, rather than to ship a complete trading engine. I’m happy to discuss methodology or share deeper details privately with interested engineers. Appreciate the pushback — it’s valid.