HN user

prettyblocks

371 karma
Posts8
Comments106
View on HN

I can’t help but wonder whether constant use of “agent” harnesses will lead to an atrophy of the software engineering (or really any field) muscles.

It will, but I'm not sure the impact of this will be all too great. We suffer from not knowing how to use an abacus because we have a calculator, and people who feel a pull to keep their low-level chops up will do so anyway.

In my experience most people with the type of critique I'm seeing from you have only tried it one time or have not taken the time to invest in an environment/process that will work for agentic coding.

My question is not so much about sharing a cherry picked example, but the question was more like "have you tried in earnest to make it work". That's the part that wasn't clear from your original post. But you say you have, and you weren't impressed. Fair enough. I'm not trying to convince you otherwise, but I encourage people to give the tools a fair chance before throwing up their hands and deciding it's meh.

Having said all that, you're right there isn't a shared experience.

I'm curious. What have you actually tried? Are you just prompting the LLM with one off tasks? For good results, you need to take the time to read the documentation for the harness you are using and configure your environment. This tuning can take dozens hours to nail down. Then there's the actual approach for working on your projects. Many people that have good results with agentic coding actually spend the bulk of their time in plan mode where they go back and forth with the LLM designing a granular playbook for the task at hand before they ever have it write any code.

However, in hindsight, Leary proved to be a false prophet who helped destroy the 1960s movements by pushing young people to take a drug that fried their brains and diverted their energy from political activism.

This is a pretty bogus claim. False prophet maybe, but the idea that political activism fizzled out because everyone was eating acid seems pretty unsubstantiated.

Yes ai can’t see, it only understands numbers.

I've also used AI to build frontends that I'm more than satisfied with, and I think it can "see" perfectly fine. The frontier models are multi-modal and pretty good at vision. You can hook up your coding harness to your browser which will take screenshots of your rendered frontend and modify the code accordingly.

I think it's safe to assume that "AI help was used" in everything these days and I don't understand why that should be a problem.

I think it really depends what time of year you go. Zion is beautiful, but when I went it was early in the season and a lot of the popular stuff was closed and it was very crowded everywhere. On the same trip I did all 5 parks in Utah, and I easily rank Zion as my least favorite, even though people seem to love it the most. I would definitely go back though.

I don't think you will get that anytime soon because for a model to work well with something like openclaw it needs a massive context window.

I think the biggest case for fine tuning is probably that you can take small models, fine tune them for applications that require structured output, and then run cheap inference at scale. "Frontier LLMs can do it with enough context" is not really a strong argument against fine-tuning, because they're expensive to run.