islewis
Joined 3 years ago
Joined 3 years ago
I cannot speak to the other accents, but my experience has been that American south accents are really poorly represented in mainstream Speach-To-Text models. If your STT model is pointed at end users, this can cause quite a quality drift when looking at eval vs prod performance depending on who your user base is.
I am not sure what terms you have collected the speach data on, but I am sure there are lots of people working with voice models that would be very interested in this as an eval set.
If the 1:1 ratio was purely for I/O (big assumption, very likely wrong), I am curious why they did not just go with ConnectX-8? Other hyperscalers have been shipping NVL72 clusters with ConnectX-8 on roughly the same timeline, and it offers the same 800Gb/s of throughput.
Managing a custom Ariel variant (which seems to be a Meta-only build) is not insignificant complexity, I wonder if they had another need for that 2x CPU-GPU ratio in their workloads relative to the stock GB200s.
EDIT: I looked, the gb200s NVL72s never have shipped with CX-8s, I made this up. This decision could have totally been due to compute availability and timing
Given OpenAI already did its mask-off moment with their un-nonprofiting, which did not appear to damage them much after the media cycle blew over, I am a bit surprised Anthropic is deciding to continue with this lip service.
does anyone know if the employees who didnt get poached got their equity paid out?
The usecase for small models like this is making on-device STT/TTS more accessable. This is important if your usecase is sensitive to either privacy or latency, but this comes at the cost of quality.
My experience has been that these small TTS models are unexpectedly good if your audio is in distribution (western accents, higher quality audio, common vocabulary), but pretty quickly degrade as you move outside of that. They often dont support more complex features such as diarization, multilingual, or realtime streaming either.
You can slide these numbers around however you want and the point still stands, even if you disagree with it for other reasons
> Parker Conrad's redemption arc after Zenefits hit a plot twist when Rippling sued competitor Deel for planting an undercover spy inside Rippling who was paid €5,000/month by Deel's CEO to steal trade secrets . The DOJ opened a criminal investigation. Deel allegedly ran the same playbook at crypto HR startup Toku. YC uses Rippling for their own HR — awkward.
I am curious what the motivation for creating this was
this overlap has been widening incredibly quickly. lots of designers are now writing code with the help of cursor, claude code, etc.
even if you believe "real designers" wont ever use this product, it's not hard to see how a low barrier-of-entry tool could affect Figams bottom line. slowing down Figma's adoption from the new wave of entry-level designers who dont already have muscle memory would not at all surprise me at all.
So... practically no one? My experience has been that almost everyone testing these cutting edge AI tools as they come out are more interested in new tool shinyness than safety or security.
Will this still be an exit event for employees or do they get screwed here?
It feels pretty intuitive to me that the ability for an LLM to break a complex problem down into smaller, more easily solvable pieces will unlock the next level of complexity.
This pattern feels like a technique often taught to junior engineers- how to break up a multi-week project into bitesized tasks. This model is obviously math focused, but I see no reason why this wouldn't be incredibly powerful for code based problem solving.