Live data from Hacker News

Beyond agentic coding

haskellforall.com

21–30 of 96 posts

Re: Beyond agentic coding

#21
post #19

I wonder if the problem of idle time / waiting / breaking flow is a function of the slowness. That would be simple to test, because there are super fast 1000 tok/s providers now. (Waiting for Cerebras coding plan to stop being sold out ;) I've used them for smaller tasks (making small edits), and the "realtime" aspect of it does provide a qualitative difference. It stops being async and becomes interactive. A suffici…

You still have to synchronize with your code reviewers and teammates, so how well you work together in a team becomes a limiting factor at some point then I guess.

Re: Beyond agentic coding

#22
I have been considering what it would be like to give each function name a specific color and a color for each variable's type followed by a color derived from the hash of the symbol name and keywords would each be their specific type. And essentially printing a matrix of this, essentially transforming your code into a printable matrix "low-lod" or "mipmap" form. This could be implemented like the VSCode minimap but I the right move here is to implement it as a hook that can modify the output of your agent. That way you can look at the structure of the code without reading the names in particular.

Re: Beyond agentic coding

#23
What I've found is that most people who dislike the chat interface aren't using it in a way that leverages its strengths.

Up until recently, LLMs just plain sucked. You'd set them on a task and then spend hours hand-holding them to output something almost correct.

Nowadays you can have a conversation with the chatbot, hash out a design, rubber duck and discuss what-ifs until you have a solid idea of the thing you're building, codified in a way an agent could understand, and now you have a PLAN.

From there, it's a matter of setting the agent in motion and checking from time to time to make sure it's not getting stuck on something under-specified.

That said, I've found that this kind of workflow works a lot better with claude than with gemini.

Re: Beyond agentic coding

#25

I whole heartedly prefer chat interfaces over inline ai suggestions. I find the inline stuff so incredibly annoying because they move around the text I am looking at.

Same! It feels like being shouted at nonstop by an overeager teacher's pet who's wrong 60% of the time.

I do appreciate in-IDE functionality that can search the codebase etc etc, but I want to hit a button when I need it.

Re: Beyond agentic coding

#26
post #2

Post had nothing to do with Haskell so the title is a bit misleading. But rest of article is good, and I actually think that Agentic/AI coding will probably evolve in this way. The current tools are the infancy of AI assisted coding. It’s like the MS-DOS era. Over time maybe the backpropagating from “your comfort language” to “target language” could become commonplace.

Agreed. This website seems to prepend the blog name to each page's document.title

Would suggest that one of the mods remove it

Re: Beyond agentic coding

#27

[dead]

> Honestly the model that works best for me is treating agents like junior devs working under a senior lead. The expert already knows the architecture and what they want. The agents help crank through the implementation but you're reviewing everything and holding them to passing tests. That's where the productivity gain actually is. When non-developers try to use agents to produce entire systems with no oversight tha…

[dead]

Re: Beyond agentic coding

#28
I really like the "file lens" example:

> “Focus on…” would allow the user to specify what they're interested in changing and present only files and lines of code related to their specified interest.

> “Edit as…” would allow the user to edit the file or selected code as if it were a different programming language or file format.

Re: Beyond agentic coding

#29
post #20

The “Calm technology” thing always annoys me, because it skips every economic, social, and psychological reason for the current state of affairs and presents itself as some kind of wondrous discovery, as opposed to “the way things were before we invented the MBA.” A willing blindness to predators doesn’t provide a particularly useful toolkit.

I would be interested to hear you elaborate on this more. I feel like I almost get what you are saying but am not confident I actually understand.

Re: Beyond agentic coding

#30
“Facet-based project navigation You could browse a project by a tree of semantic facets. For example, if you were editing the Haskell implementation of Dhall the tree viewer might look like this prototype I hacked up2”

^ This is a genius idea - someone add this to claude

Post reply on HN