Testing this hardware LLM (LLAMA 3.1 8B on a chip) I get ~16k tokens per second.
With frontier models plateauing, I’ve been convinced AI will end up like bitcoin mining, and that NVIDIA’s general-purpose GPUs will be replaced by model-specific chips.
Forget everything you know and consider that it might be a misguided and risky negotiation tactic.
Disclaimer: This is not business advice and should be read using Cartman’s voice.
Step 1: Announce publicly that you are not renewing your contract.
Step 2: If the market has viable alternatives or the service you are negotiating isn’t that hard to replicate, other actors will manifest to fill in the gaps, especially if your business is attractive. (E.g., The top comment is building an alternative; other comments point to alternative services.)
Step 3: Congratulations, you now have leverage for a significant discount with your previous provider because they face the real prospect of losing your business entirely to a competitor. If the competitor is private, you can even double dip by investing in their company before attributing them the contract.
All the publicly accessible sources you mentioned have already been scraped or licensed to avoid legal issues. This is why it’s often said, “there’s no public data left to train on.”
For evidence of this, consider observing non-English-speaking young children (ages 2–6) using ChatGPT’s voice mode. The multimodal model frequently interprets a significant portion of their speech as “thank you for watching my video,” reflecting child-like patterns learned from YouTube videos.
Parent is working on scheduling tools for NA meetings.
Yes some things are important and can’t be broken without some serious real world consequences.
MVP is “the first thing that stick”. The method to get there should be meticulously engineered to cut as much iteration time between prototypes as possible. When your ugly prototype shows strong traction by its own and test users are asking you to keep the prototype then you know you have a rough diamond to cut.
Obviously when you have a sizeable user base, know the market very well and your market isn’t that much competitive you are at an advantage.
Beware of market expertise ego and dogfooding as it only reinforce your expertise and biases. Bring industry newcomers to your project for feedback, it’s the only way to make sure your expertise doesn’t make your product only valuable for yourself.
> Beware of market expertise ego and dogfooding as it only reinforce your expertise and biases. Bring industry newcomers to your project for feedback, it’s the only way to make sure your expertise doesn’t make your product only valuable for yourself.
Good point, but this particular demographic has no problem letting me know where the rough bits are.
The thing about the MVP pattern, is that software people seem to think that we get to go by different rules, from everyone else.
Software lets us iterate quickly, and I have found ways to leverage that (I call it "Evolutionary Design"[0]), but that does not give me license to deliberately foist garbage onto end users; especially ones that are quick to anger, and slow to forgive.
Every other craft, engineering discipline, and production system, throughout history, has had to take the risk of going through a design phase, based on expertise, user surveys, need evaluations, etc., then actually get to at least production prototype phase, before determining whether or not to proceed further.
It's a risk, but one that everyone has been taking, for hundreds of years.
For some reason, we software people seem to think that the flexibility of software absolves us of the Responsibility to deliver a high-quality prototype, and that we don't need to take the same risks that everyone else has been taking throughout history.
I totally agree that said flexibility gives us a great opportunity to actually deliver a much more suitable product, than was achievable, with other production methodologies, and ease of iteration is how we get there.
I just don't agree that we start by throwing out some junk, without first doing some real homework.
I'm really tired of seeing junk prototypes becoming the shipped product. Once it is out there, and running in production, it's quite difficult to make the kinds of pivots and changes that are almost certainly required, without turning the app into a disgusting mess. One of the nice things about the last couple of years, is that I have been able to completely nuke the database, several times, as we have pivoted. I'd never be able to do that, if it were a production app. I'd have to devise some kind of horrible kludge, or, more likely, limit the pivot.
« Mui tells TechCrunch that startups must fulfill two criteria in order to automatically invest: first, the co-founder must be a member of the class, and second, they must raise a round of $750,000 or more from a reputable institutional investor »
With frontier models plateauing, I’ve been convinced AI will end up like bitcoin mining, and that NVIDIA’s general-purpose GPUs will be replaced by model-specific chips.
Glad to see someone innovating in this space.