Live data from Hacker News

The Zechner-Lopopolo Continuum: Do you even read your Clanker code? Should you?

sub.thursdai.news

1–7 of 7 posts

Re: The Zechner-Lopopolo Continuum: Do you even read your Clanker code? Should you?

#3
i think the intended target of the software matters - Zechner needs to make a small tasteful core agent that others can extend/depend on, whereas Lopopolo needs to ship a large 1M LOC enterprise app with a tiny team of 5

the code conclusions kinda fall out of those constraints

Re: The Zechner-Lopopolo Continuum: Do you even read your Clanker code? Should you?

#4
post #3

i think the intended target of the software matters - Zechner needs to make a small tasteful core agent that others can extend/depend on, whereas Lopopolo needs to ship a large 1M LOC enterprise app with a tiny team of 5 the code conclusions kinda fall out of those constraints

Thanks Swyx! I agree, I mentioned in the end where I sit on the continuum, but I don't maintain any hugely critical production code.

Do you think the intended target will matter as much as it does in a year?

Re: The Zechner-Lopopolo Continuum: Do you even read your Clanker code? Should you?

#5
post #4
post #3

i think the intended target of the software matters - Zechner needs to make a small tasteful core agent that others can extend/depend on, whereas Lopopolo needs to ship a large 1M LOC enterprise app with a tiny team of 5 the code conclusions kinda fall out of those constraints

Thanks Swyx! I agree, I mentioned in the end where I sit on the continuum, but I don't maintain any hugely critical production code. Do you think the intended target will matter as much as it does in a year?

no it should matter less over time

Re: The Zechner-Lopopolo Continuum: Do you even read your Clanker code? Should you?

#7
I'm clearly on the Lopopolo side of the Zechner-Lopopolo Continuum. We've reached a point where I trust SOTA AI to write better code and perform better reviews than I can in many situations - given proper, thorough prompting. It's far from hands-off, which is why I much prefer the term "agentic engineering" over "vibe coding". The `/review` command is my new best friend: I run it after every major change an agent makes, just as I used to ask "are you sure?" after every important response from a chatbot.