Hey folks, been tinkering with Sudowrite for some blog posts and documentation, and I think the 'First Draft' button is a bit misunderstood. It's not an auto-writer, it's more like a CI/CD pipeline for your initial ideas.
Think of it this way:
* **Writing yourself** is like manually provisioning a server. You choose every package, set every config line, and understand the entire state. It's slow, but you have perfect control and knowledge.
* **Hitting 'First Draft'** is like running a Terraform module. You give it some parameters (your notes/outline), and it builds a functional, baseline structure for you. It gets you to a running state fast, but you'll absolutely need to review and adjust the output—just like you'd review a Terraform plan.
For example, I fed it a rough outline for a post on setting up a Grafana Loki cluster. The draft gave me a coherent structure and basic explanations I could work with. But it missed crucial nuances about persistent volumes and retention policies that I, as the human with the context, needed to go in and engineer.
So it’s a fantastic tool for overcoming blank-page syndrome and generating momentum, not for producing finished, nuanced work. You're still the SRE of your own writing—the button just automates the initial deployment 😄
—Chris
K8s enthusiast