back

by jjmarr·5mo ago·view on hn ↗
I vibe coded a Kubernetes cluster in 2 days for a distributed compilation setup. I've never touched half this stuff before. Now I have a proof of concept that'll change my whole organization.

That would've taken me 3 months a year ago, just to learn the syntax and evaluate competing options. Now I can get sccache working in a day, find it doesn't scale well, and replace it with recc + buildbarn. And ask the AI questions like whether we should be sharding the CAS storage.

The downside is the AI is always pushing me towards half-assed solutions that didn't solve the problem. Like just setting up distributed caching instead of compilation. It also keeps lying which requires me to redirect & audit its work. But I'm also learning much more than I ever could without AI.

4 comments
> that would've taken me 3 months a year ago, just to learn the syntax

This is hyperbole, right? In what world does it take 3 months to learn the syntax to anything? 3 days is more than enough time.

You perhaps just introduced one more moving part, that you don't understand well. Instead of thinking of a simpler solution.
I hope we get a follow-up in six months or a year as to how this all went.
> I vibe coded a Kubernetes cluster in 2 days for a distributed compilation setup. I've never touched half this stuff before. Now I have a proof of concept that'll change my whole organization.

Dunning-Kruger as a service. Thank God software engineers are not in charge of building bridges.

Looking forward to your post-mortem.