I tried an experiment: instead of asking an LLM to help with a project, I asked it what it would build.
It picked a small Rust CLI for code archaeology - a tool to explain why a repo looks the way it does.
The interesting part wasn’t the code, but my role: mostly setting boundaries, killing scope creep, and keeping it a tool instead of a product.
Less “AI replaces creativity,” more “AI accelerates the boring parts if you already know when to say no.”
https://jakegoldsborough.com/blog/2026/letting-ai-pick-the-project/