Live data from Hacker News

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

danielvaughn.dev

211–215 of 215 posts

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

#211

There's a problem being missed here. You're trying to make a big complex thing from a little simple thing. It's like trying to take a hash and turn it back into the original data, without knowing what the original data looked like. You can get close, but things will be missed. So you'll edit, or provide more info to the AI outside your pseudocode, and maybe get to what you want. But another change will undo the fix y…

Yes, human imperfection is and will always be an issue. I think humans should get out of the loop for finite tasks, but the problem specifically with software creation is that it's inherently unbounded. You need a human somewhere to reign it in and ensure it's aligned with intent.

A good example of a finite task is like something we're working on at my company. We're building a multi-agent orchestration engine for large scale offensive network ops. Think like an Active Directory attack. This kind of thing is extremely complex, and involves lots of ambiguity and cross-referencing. You couldn't deterministically program a machine to do this attack, but you could definitely coordinate a bunch of agents to work together to do it. And you don't need a human in the loop outside of some lightweight scoping and gating procedures.

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

#212
It seems very close to Spec driven development. Here the spec is the pseudocode. I slightly disagree with people on the thought that we don't think when we do agent based development. Most of my Agent based development is me specifying a change(lose one line or full fledged PRD) and most of what agent based development solves for me is being thorough with the rest of the codebase.

Although I like your direction, i would hate to see this become yet another programming language.

Also if your pseudocode has a definitive structure, why not write an interpreter or compiler ? And not waste AI cost? Like how traditional BDD stack works gherkin and cucumber and the likes?

Direction, I love. Approach, we can always change. Peace

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

#213

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…

I would disagree that there is no thinking. I think a strong understanding of the fundamentals of coding are still wildly important to get good quality code, and a big part of that is thinking or reasoning through a particular problem. It’s just now we have a way of using common language in order for that to happen instead of having to learn or keep up with every new tool and framework in order to do so. The new prog…

"The new programming language is just in your native tongue." False. Engineering was about implementation, not about result. "How to get there"? Now "thinking" is to check that model actually understood what you want. We are much closer to product manager who's testing new product with his hands and giving feedback to engineers, rather than to engineers who's thinking "how we implement that"?

"but AI has opened up an entirely new world" - i hear this all the time exactly from "not a full time dev's". This is FOR SURE opened whole new world to people who didn't code and collapsed whole old world for people who loved to code.

Maybe it is just me, but creating simple CRUD application pre-llm required more cognitive ability from me than to "implement" whole CRM system with UI and multiple integrations right now. It is not hard, just tiring in a boring sense, like finding needle in a haystack

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

#214
post #117

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…

> Either be a programmer and code, or be a delegator and delegate Even if you just enjoy programming for the sake of programming, you can use it to review your code and then hand verify its findings, or prototype and explore feasibility of something you will in the end fully code yourself. For most people that enjoy programming there are still tasks they don't enjoy, like making a bunch of cross-language bindings for…

Nope. You can't. Expectations and deadlines aligned with code agent usage. No one let you spent x5 time coding things yourself

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

#215

Preface: unpolished thoughts — it is refreshing to see so many people working on this issue! Lately I've been dreaming about a way of using LLMs that never (or in majority of the cases) results in chatting with an agent or checking its traces. Instead, you provide prompts in natural language, e.g. refactor these modules in this way ..., and the result is shown as a visual proposal (some kind of diff on a graph). Then…

Check out Plannotator. It’s not exactly visual, but instead of chats you just give something more like an inline code review. Highlight text, add emoji reactions, contextual comments. This is my preferred way of reveling AI plans. Now I’ve started using it to open planning sessions on existing files and annotating them instead of starting from a prompt, in some cases.
Post reply on HN