80 karma · joined June 14, 2012
I have built humans in the loop feedback models before and they are always very targeted to a specific task. This approach modular and intuitive. I think the scope is too small though.
I spent the weekend starting a project to use this approach using a GPT model and FlumeJs (https://github.com/chrisjpatty/flume) but now that I see noFlo i am excited to try it
- Planets are sentient
- Alien Robots outlive Aliens
- Photon life makes more sense
- Carbon based life is fragile
Any GPT model is just one component inside of a chatbot, not a chatbot itself.
It's not, if a client is in trail with your service and they miss a message you risk losing that client. It's only "Okay" to not deliver on non-client facing services. Anything else is an unmeasurable risk
Miami is investing in mediating current and future floods. I feel the fact that flood prevention is a significant part of your budget and planning that says something https://www.youtube.com/watch?v=c1dnlHPzhQA
I've seen questions about - Required tech specs - Potential upgrades - Trial periods - Varying pricing schemes - General support
These things are handled differently with SaaS. Its easier to address with continued income too.
That's a lifetime of job security