Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Building better AI tools

hazelweakly.me

Post reply on HN
Print view View original

31–40 of 189 posts

Re: Building better AI tools

#31

Post by JoshuaDavid »

dingnuts wrote: post #15
pplonski86 wrote: post #6

Earlier quoted context omitted.

It is much easier to implement chat bot that intelligent workspace, and AI many times doesn't need human interaction in the loop. I would love to see other interfaces other than chats for interacting with AI.

> AI many times doesn't need human interaction in the loop. Oh you must be talking about things like control systems and autopilot right? Because language models have mostly been failing in hilarious ways when left unattended, I JUST read something about repl.it ...

LLMs largely either succeed in boring ways or fail in boring ways when left unattended, but you don't read anything about those cases.

Re: Building better AI tools

#33

Post by dfee »

taylorallred wrote: post #14

One thing that has always worried me about AI coding is the loss of practice. To me, writing the code by hand (including the boilerplate and things I've done hundreds of times) is the equivalent of Mr. Miyagi's paint-the-fence. Each iteration gets it deeper into your brain and having these patterns as a part of you makes you much more effective at making higher-level design decisions.

I’m concerned about becoming over reliant on GPT for code reviews for this reason (as I learn Rust).

Re: Building better AI tools

#34

Post by lupire »

taylorallred wrote: post #14

One thing that has always worried me about AI coding is the loss of practice. To me, writing the code by hand (including the boilerplate and things I've done hundreds of times) is the equivalent of Mr. Miyagi's paint-the-fence. Each iteration gets it deeper into your brain and having these patterns as a part of you makes you much more effective at making higher-level design decisions.

Do you write a lot assembler, to make your note effective at higher level design?

Re: Building better AI tools

#35

Post by creesch »

ahamilton454 wrote: post #29

This is one of the reasons I really like deep research. It always asks questions first and forces me to refine and better define what I want to learn about. A simple UX change makes the difference between education and dumbing users of your service.

Have you ever paid close attention to those questions though? Deep research can be really nifty, but I feel like the questions it asks are just there for the "cool factor" to make people think it is properly consider things.

The reason I think that is because it often ask about things I already took great care to explicitly type out. I honestly don't think those extra questions add much to the actually searching it does.

Re: Building better AI tools

#36

Post by cheschire »

lubujackson wrote: post #19

Great insights. Specifically inverting the vibe coding flow to start with architecture and tests is 100% more effective and surfaceable into a real code base. This doesn't even require any special tooling besides changing your workflow habits (though tooling or standardized prompts would help).

you could remove "vibe" from that sentence and it would stand on its own still.

Re: Building better AI tools

#37

Post by didibus »

I think the author makes good points, if you were focused on enhancing human productivity. But the gold rush is on replacing humans entirely for large swath of work, so people are investing in promises of delivering without human in the loop systems, simply because the ROI allure is so much bigger.

Re: Building better AI tools

#38

Post by ACCount36 »

nico wrote: post #8
Edmond wrote: post #4

In terms of AI tools/products, it should be a move towards "Intelligent Workspaces" and less chatbots: https://news.ycombinator.com/item?id=44627910 Basically environments/platforms that gives all the knobs,levers,throttles to humans while being tightly integrated with AI capabilities. This is hard work that goes far beyond a VSCode fork.

Using Claude Code lately in a project, and I wish my instance could talk to the other developers’ instances to coordinate I know that we can modify CLAUDE.md and maintain that as well as docs. But it would be awesome if CC had something built in for teams to collaborate more effectively Suggestions are welcomed

Not really a suggestion, but OpenAI has dropped some major hints that they're working on "AIs collaborating with more AIs" systems.

That might have been what they tested at IMO.

Re: Building better AI tools

#39

Post by tjr »

taylorallred wrote: post #14

One thing that has always worried me about AI coding is the loss of practice. To me, writing the code by hand (including the boilerplate and things I've done hundreds of times) is the equivalent of Mr. Miyagi's paint-the-fence. Each iteration gets it deeper into your brain and having these patterns as a part of you makes you much more effective at making higher-level design decisions.

I'm concerned about this also. Even just reading about AI coding, I can almost feel my programming skills start to atrophy.

If AI tools continue to improve, there will be less and less need for humans to write code. But -- perhaps depending on the application -- I think there will still be need to review code, and thus still need to understand how to write code, even if you aren't doing the writing yourself.

I imagine the only way we will retain these skills is be deliberately choosing to do so. Perhaps not unlike choosing to read books even if not required to do so, or choosing to exercise even if not required to do so.

Post reply on HN