Today we are announcing Genie 3, a general purpose world model by @GoogleDeepMind that can generate dynamic, interactive environments with a single text prompt.
World models are AI that understand facets of the world (like Veo's knowledge of intuitive physics or Genie's mastery of new environments), and serve as a key stepping stone on the path to AGI.
Genie 3 is our first world model to allow interaction in real-time, while also improving consistency and realism compared to Genie 2.
Learn more ➡️ https://t.co/dbvPn9paZm
Had a play with Google's experiment Opal and made a kid's bedtime story generator. Looks eerily similar to tldraw in the editor.
Video sped up (2x) https://t.co/sOUxPhS3jL
2/ Improve consistency in multi-turn conversations. Caching isn’t just a developer trick—it’s essential for scale!
Have you built with prompt caching? How much latency did you cut? #LLM#LangChain#AI#PromptEngineering
https://t.co/CPa9c3VV8g
1/ ⚡️ Prompt caching is the unsung hero of LLM-powered apps! Instead of paying and waiting for new responses every time, cache past completions and instantly serve repeat results.
This IBM tutorial walks you through SQLiteCache:
Save on costs & Speed up your LLM App
1/ 📈 Want next-level retail demand prediction? This tutorial takes you through using a model from IBM's Time Series Foundation Model Family (TinyTimeMixer)
It's open-source, really tiny (<1M params) and performs well—no billion-parameter beast needed
https://t.co/jjkErgKnXG
This is wild! @tldraw has blown my mind with how far down the rabbit hole their infinite canvas has got. @steveruizok gives a great demo here
https://t.co/FE7awl7zY5
Stories have nothing to do with requirements. Zero. Zip. Nada. Requirements specify the desired behavior of a computer program. Stories describe the user performing a domain-level task that leads to a valuable outcome. Stories do not describe any aspect of a computer program.
@allenholub No it was a retweet of your original with a provoking question for others. I agree with you. Teams that I lead go out and talk to users. Meet them where they are, look at what they are trying to do, then prototype and validate their understanding
@allenholub And how do you find out what the valuable outcome is without measuring and testing? Rather than stories or requirements, why not hypothesis?