Hacker Newsnew | past | comments | ask | show | jobs | submit | htrp's commentslogin

How are you different from all the other quant funds?

there is no human in the loop, there is no high frequency trading. We're trying to have AI mimic what fund managers do:

- lots of research - longer time horizons - zero humans in the loop, but explain every single thing you do.


> They've obviously had a go at being a first-party model company to address this, but that didn't work.

I thought there was an entire initiative to build their own coding model and the fine tunes of in Composer 1.5 and Composer 2 were just buying them time and training data


what kind of tps slowdown would you realistically on an npu vs gpu?

Microsoft requires a 40 TOPS NPU for Copilot co-branding, which a RTX 3050 can beat.

fine tune an oss model and call it a groundbreaking innovation -- 20 points

isn't this basically prophet?

No. Prophet is based on curve-fitting.

Attackers only have to be successful once while defenders have to be successful all the time?

Yes and no. Good defence is layered and an attacker needs to find a hole in each layer. Even if it is not layered intentionally a locally exploitable vulnerability gives little if you have no access to a remote system. But some asymmetry does exist.

I thought the expectation was cleaning up the balance sheet in preparation for IPO.... along with a pivot towards codegen revenue.

> But the last few weeks Opus 4.6 seems to have got dumb again. Now it is making way more mistakes and forgetting useful things and recent context it used to manage.

are you logging access patterns and times to see when the degradation occurs?


If the model "improves" every 5 hours, how do you have any guarantee of model consistency across long coding sessions?

Yeah, this feels tricky

If the model changes every few hours, we’re basically debugging against a moving target - and that gets expensive fast.


What do you need consistency for

The actual paper from April 2025

TurboQuant: Online Vector Quantization with Near-optimal Distortion Rate

https://arxiv.org/abs/2504.19874


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: