Live data from Hacker News

Show HN: Huzzah – a novel approach to coding with AI

danielvaughn.dev

81–90 of 224 posts

Re: Show HN: Huzzah – a novel approach to coding with AI

#81
As I see it, there's a bit of internal contradiction: your declared intent is to not write code, but you had to circle back to code (albeit more relaxed and vague) because human English is (compared to proglangs) imprecise. Pseudocode, however, is not far away from it, still not strict, and LLM is still a stochastic generator. So it will continue to randomly deviate from what you want it to do. I guess it could be an enhancement, but who knows, maybe in a year from now, you will get tired with pseudocode not being precise, and go back to writing code :wink:

Re: Show HN: Huzzah – a novel approach to coding with AI

#82

I think you’re probably missing why it’s exhausting. The problem is not writing English, it’s the rate of change. Programming is meditative, it is a thinking process, the code you output is an artifact of your thinking. Agent-based development… there is no thinking, no meditation, you’re delegating the thinking to a machine, you’re just barking what you want at it, incessantly, endlessly. For businesses it makes sens…

Agree with programming is meditative but disagree that agent-based development means there is no thinking. Agent-based development means more thinking like a lower level manager. You spend more time making architecture decisions, making decisions on the user interface, trying to manage your time and your agents time to increase the amount of work produced in the same time, asking the agent about the code and making new decisions. For many people who went in programming thats not their strong suite and hence is really exhausting. Instead of living in the code you are managing the code and using a part of the brain you are not good at.

Re: Show HN: Huzzah – a novel approach to coding with AI

#83
I really feel the pain here, I have myself tried things ol these lines... I will give Huzzah it a try.

My concern, however, is that all of these options might ultimately be slower than just prompting.

I mean, at this point, another option would be to just go back to actually writing the code ourselves, like we did back then in 2024 ??

Re: Show HN: Huzzah – a novel approach to coding with AI

#84
I had this idea 25 years ago, except that I wanted to use the AI available at the time, which would have probably been genetic algorithms. The idea was to write the expected outputs for some input examples and have a Lisp-like language use evolution/mutation to generate a paragraph or so of code that meets the spec.

Then probably do some fuzzing or SAT solving to formally enumerate the known-good cases and possible edge case exceptions. That was before I knew about ranged variables, category theory, etc.

Unfortunately the real world got in the way, and I spent a quarter century treading water to survive, which was exacerbated by CPTSD amplifying ADHD and OCD symptoms many fold before I knew what they were. So now any great ideas I might have had are rendered obsolete because an LLM can synthesize them in a matter of minutes. It may be time to let go and hand things over to the next generation.

-

I think maybe the goal now is to keep building on these ideas until we achieve creating digital assistants that can manage all of the aspects of our lives that interfere with our goals. That's a controversial statement because the political right doesn't distinguish between setbacks and goals (it's all discipline) while the political left embraces a kind of learned helplessness as controlled opposition. Change comes glacially or not at all. In other words, help isn't coming from above - we have to pick ourselves up by our bootstraps like we always do.

A few things that AI might help solve by rendering the conditions of their existence obsolete:

- Money

- Hunger

- Illness

- Exploitation

- Pollution

The list goes on. Unless we're actively working to solve these things, then whatever we come up with is frankly a distraction. I consider just about all tech innovation since the 1990s to be a waste of time for that reason. It all just made some guy rich. Yawn.

Huzzah however, is great. I hope it leads to something wonderful.

Re: Show HN: Huzzah – a novel approach to coding with AI

#86
I really like the “persisting of intent” part of this approach. I don’t have any experience with coding agents, but it seems to me that this could make it much easier/quicker for others to understand an AI-written codebase (or even PR) and maybe also for agents to better pick up on the “human context” of a project.

Personally, I’d feel much more confident to use a vibe-coded library where I can read the human-written intentions than one where I just see a lot of AI-written code. Maybe it feels more like there is still a programmer/engineer/architect behind it who knows what they’re doing and what exactly they want to achieve.

To me, vibe-coding always feels a bit like this weird transition into something else that is more precise and reliable. It feels backwards to give up on our achievements in formal language for the comfortable vagueness of everyday speech.

Re: Show HN: Huzzah – a novel approach to coding with AI

#87
post #75

I'm not sold on the pseudocode approach, but I agree with the declarative aspect. Declarative specs have become central to my process and I've built this tool to support it: https://github.com/spekk-ai/spekk-cli Rather than writing exhaustive specs, I preserve only the intent and what must be true as discrete assertions. This preserves the leverage you get from LLMs - anything it can reliably infer does not need to b…

I have a pretty similar approach to this. I built a sexp DSL for spec and I have a "compiler" which does static analysis checks and linting.

Re: Show HN: Huzzah – a novel approach to coding with AI

#88
post #82

I think you’re probably missing why it’s exhausting. The problem is not writing English, it’s the rate of change. Programming is meditative, it is a thinking process, the code you output is an artifact of your thinking. Agent-based development… there is no thinking, no meditation, you’re delegating the thinking to a machine, you’re just barking what you want at it, incessantly, endlessly. For businesses it makes sens…

Agree with programming is meditative but disagree that agent-based development means there is no thinking. Agent-based development means more thinking like a lower level manager. You spend more time making architecture decisions, making decisions on the user interface, trying to manage your time and your agents time to increase the amount of work produced in the same time, asking the agent about the code and making n…

> Agent-based development means more thinking like a lower level manager. You spend more time making architecture decisions, making decisions on the user interface,

Whose manager is making these decisions? My managers have always been concerned with how much workload everyone has, delegating tasks at an extremely high level that they barely understand, and handling the messy human interface between their reports and senior leadership so that everyone on their team is kept happy and properly compensated.

I have been in this industry for almost twenty years and I have NEVER had an engineering manager making architecture decisions (that's either my job or the lead engineer's job, depending) or UX interface decisions (that's the realm of Product).

If my LLM agents start taking sick leaves and pager duty rotations then I'll start entertaining this bullshit line about being a manager

Post reply on HN