alt Hacker News> Claude Code and its ilk can turn "maybe one day" internal projects into live features after a single hour of work. You really, honestly, and truly are missing out if you're not looking for valuable things like that!
You're right, it's possible. But you might be both overestimating the ease of onboarding and underestimating the variety of tasks and constraints devs are responsible for.
I've seen Claude knock out trivial stuff with a sufficiently good spec. But I've also seen it utterly choke on a bad spec or a hard task. I think these outcomes are pretty broadly established. So is the expectation that the tech will get better. Waiting isn't unwise.
Waiting may not be “unwise” but acting now may be optimal. Even though tooling may be much better in 12 months, if it can improve quality or time now, that’s a net benefit.
Bikers in the Tour de France used to not wear helmets. They were seen as uncouth (“why jump on the bandwagon?”). Helmets today are way better than they were then. But if the utility provided is greater than the cost, of course it makes sense to act sooner.
I’m not explicitly arguing for investing in AI or other newfangled tech, I’m arguing that the premise of waiting may be “sounded” but also “leaves money on the table”, or in some cases, lives.
The author talks about vaccines as a counter example but doesn’t really address the cost/benefit in any detail.