HuggingFace has been extremely responsive when an issue is raised. I found issues in their infrastructure this year as well as cache confusion in Chrome, and HF fixed their CDN in a day and I didn’t hear back from Google for a week or two and could no longer show how to exploit Chrome as I figured HF infrastructure issues would drag on possibly forever.
Once hired a DBA that reworked backup scripts. He got real annoyed at the idea of testing the backups with real restores and clearly never did on the real databases (only on his smaller samples).
Turns out the backups took 30 hours. The daily backups. That then overwrote each other on the assumption that the backups would not take that long.
No, that misses the whole point of content negotiation (for language, et al). In the age of search engines though, different urls are often perferable.
It’s terrible and depressing work to take vibe coded garbage and make it a real product. There will be demand, but good engineers won’t want to touch it. And people paying will think they did the hard work so why pay a good rate?
You can write a skill (many have) to lead it in how to use different models and efforts for subtasks. For searching the code base, for example, I have it use Haiku, which is fast.