| ▲ | gejose 5 hours ago | |||||||
> just need to be good enough and fast as fuck Hard disagree. There are very few scenarios where I'd pick speed (quantity) over intelligence (quality) for anything remotely to do with building systems. | ||||||||
| ▲ | ssivark 2 hours ago | parent | next [-] | |||||||
If you thought a human working on something will benefit from being "agile" (building fast, shipping quickly, iterating, getting feedback, improving), why should it be any different from AI models? Implicit in your claim are specific assumptions about how expensive/untenable it is to build systemic guardrails and human feedback, and specific cost/benefit ratio of approximate goal attainment instead of perfect goal attainment. Rest assured that there is a whole portfolio of situations where different design points make most sense. | ||||||||
| ||||||||
| ▲ | jameshush 5 hours ago | parent | prev | next [-] | |||||||
I agree with you for many use cases, but for the use case I'm focused on (Voice AI) speed is absolutely everything. Every millisecond counts for voice, and most voice use cases don't require anything close to "deep thinking. E.g., for inbound customer support use cases, we really just want the voice agent to be fast and follow the SOP. | ||||||||
| ||||||||
| ▲ | gessha 3 hours ago | parent | prev [-] | |||||||
As long as the faster tech is reliable and I understand its quirks, I can work with it. | ||||||||