We tend to recommend folks spend a few hours writing evals after they spend a couple weeks prototyping. Then they get a sense of how valuable evals are for their use-case.
We think about evals a bit like perf monitoring -- it's good to have RUM but also good to have some synthetic stuff in your CI. So if you do find them valuable, useful to do both.
I could see another tier that comes with 1,0000-10,000 included requests included at 1/10 of the cost being a good idea. Might be really hard for a small startup to support those customers out the gate though!
I think if EVERY tool you use at work is in the Office suite, teams is just better. If you have any other tools like one off SaaS or devTools, Muddy could be a fit.
I fear you're right. As a remote worker, I feel that more touchpoints and areas of collaboration can really nurture a better culture. Muddy feels like a good step in that direction. While my day-to-day experience with Office365 isn't horrible, it's this kind of innovation that I want to support.
I think we might have more base interfaces (notes, sheets) but we want to encourage people to keep building first class software. All in one is worst of all
https://www.techeblog.com/google-deepmind-ai-mini-humanoid-r...