launching Waggle ๐
stop checking terminals. your agents bring every question and review to you in one inbox, with the mockups and docs to decide fast
answer in a click, and the agent picks up where it stopped
free, open source ๐ https://t.co/bqiJjeZ7Ja
The best, most comprehensive take on AI Iโve read. After a year of confusion and fear about the future, I finished it feeling like a weight had physically lifted.
Itโs long. Make the time.
@vgr is undefeated.
https://t.co/rMmuBNbBNa
We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:
Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:
Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!
In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
@uwwgo great write, and loved the illustrations :)
you didn't touch on team* responsibilities and size, how that evolved and changed, if anything, in your opinion?
*in product / tech team i mean
Introducing Dreamwork, the last tool you'll ever need to find your dream job.
With just a resume we match you to millions of jobs, tailor each resume and submit them for you - all with just a click.
But it's more nuanced than that โคต