Community and product builder. Organizando la comunidad y conferencia @9punto5_
Joined May 2009
- Tweets28.7K
- Following562
- Followers2.3K
- Likes18.4K
Fabián Acuña H. retweeted
Las series y películas pobres y monocordes de Netflix le cuestan el cargo a la directora de contenido principal, Bela Bajaria. Será reemplazada por Peter Rice, ex presidente de entretenimiento en Disney.
El jefe de cine de Netflix, Dan Lin, también sería despedido.
Esta es de las cosas que más me da miedo hacer: automatizar correos
Siento que todo puede salir tan mal XD
Fabián Acuña H. retweeted
This was love at first sight when I saw it. So I got impatient, and instead of waiting for Jason's version, I made my own for macOS. Meet github.com/klipstack/underte…
I plan to add a few more improvements over time—especially around AI helping with the blank page syndrome, suggesting titles for the whole piece once it's done, etc. But always with the human writer in control.
Looking forward to writing even more from now on.
For years, maybe a decade, I've wanted to build a writing tool that just did a few things I couldn't find anywhere else.
A system that mimicked how I think when I write. A system that provided clear affordances, features, and places to do the things I wanted to do. A way to play with my writing as I'm writing it. A way to settle into just the right way to say something.
It never made sense to make it a 37signals product because it's not commercially viable, nor would it be worth pulling people off their other work to hack on this. Plus, it would have taken months the old way.
So this weekend I just made it myself, with Claude's help.
It's called Write_On and the short video walks you through it.
Essentially it's "alternative control" at the word, sentence, and paragraph level, plus a way to dim stuff back, and stash stuff near by. Not version control, but alternative control. You'll see what I mean when you watch the video below.
So here it is. Write_On.
how's the ASD-STE100-ing going, folks?
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.
