To be fair, the article doesn’t quite deliver on this promise. The examples are mostly focused on improving work-related workflows, so I guess that’s what they think “daily life” is.
I agree, but some (most?) software being written doesn’t require a deep understanding to verify because the domain is small enough or you’re not required to solve for all of its intricacies. E.g. prototypes, internal tools, low scale CRUD apps, personal projects, etc.
I believe this is where the huge divide in perceived AI productivity in SW comes from. It’s folks working on low-understanding-required domains talking to folks working on high-understanding-required domains.
Agreed. I kinda concluded that the expected `doctor` usage is to have an agent run it for you and then they can try to figure it out when `doctor` can’t fix the issues.
I tried both Beads and Gas Town and had the same experience.
These fully vibe coded tools seem to have near zero QA. The fact that they ship with a `doctor` command that you regularly need to run (even if you didn’t change anything about your environment) tells you all you need to know.