Live data from Hacker News

Why is Claude an Electron app?

dbreunig.com

131–140 of 483 posts

Re: Why is Claude an Electron app?

#131
post #116

Earlier quoted context omitted.

Only if they are supremely lazy. It’s possible to use these tools in a diligent way, where you maintain understanding and control of the system but outsource the implementation of tasks to the LLM. An engineer should be code reviewing every line written by an LLM, in the same way that every line is normally code reviewed when written by a human. Maybe this changes the original argument from software being “free”, but…

There's a pretty big difference between the understanding that comes with reviewing code versus writing it, for most people I think.

Definitely true for me. What’s particularly problematic is code I need to review but can’t effectively test due to environmental challenges.

Re: Why is Claude an Electron app?

#132

Earlier quoted context omitted.

Why isn't Claude doing QA testing for you?

I can't tell if this is sarcasm, but if not, you cant rely on the thing that produced invalid output to validate it's own output. That is fundementally insufficient, despite it potentially catching some errors.

I have had other LLMs QA the work of Claude Code and they find bugs. It's a good cycle, but the bugs almost never get fixed in one-shot without causing chaos in the codebase or vast swaths of rewritten code for no reason.

Re: Why is Claude an Electron app?

#133
post #116

Earlier quoted context omitted.

Only if they are supremely lazy. It’s possible to use these tools in a diligent way, where you maintain understanding and control of the system but outsource the implementation of tasks to the LLM. An engineer should be code reviewing every line written by an LLM, in the same way that every line is normally code reviewed when written by a human. Maybe this changes the original argument from software being “free”, but…

There's a pretty big difference between the understanding that comes with reviewing code versus writing it, for most people I think.

[deleted]

Re: Why is Claude an Electron app?

#134

Earlier quoted context omitted.

I can't tell if this is sarcasm, but if not, you cant rely on the thing that produced invalid output to validate it's own output. That is fundementally insufficient, despite it potentially catching some errors.

> you cant rely on the thing that produced invalid output to validate it's own output I've been coding an app with the help of AI. At first it created some pretty awful unit tests and then over time, as more tests were created, it got better and better at creating tests. What I noticed was that AI would use the context from the tests to create valid output. When I'd find bugs it created, and have AI fix the bugs (wit…

I'm not saying you can't do it, I'm just saying it's not sufficient on its own. I run my code through an LLM and it occasionally catches stuff I missed.

Re: Why is Claude an Electron app?

#136

Because code isn't free. I can see it in my team. We've all been using Claude a lot for the last 6 months. It's hard to measure the impact, but I can tell our systems are as buggy as ever. AI isn't a silver bullet.

I love the fact that we just got a model really capable of doing sustained coding (let me check my notes here...) 3 months ago, with a significant bump 15 days ago.

And now the comments are "If it is so great why isn't everything already written from scratch with it?"

Re: Why is Claude an Electron app?

#137
post #116

Earlier quoted context omitted.

And after 12 months, most probably no one from your team will understand what the result of half of those bugs is. When devs outsource their thinking to AI, they lose the mental map, and without it, control over the entire system.

Only if they are supremely lazy. It’s possible to use these tools in a diligent way, where you maintain understanding and control of the system but outsource the implementation of tasks to the LLM. An engineer should be code reviewing every line written by an LLM, in the same way that every line is normally code reviewed when written by a human. Maybe this changes the original argument from software being “free”, but…

> An engineer should be code reviewing every line written by an LLM,

I disagree.

Instead, a human should be reviewing the LLM generated unit tests to ensure that they test for the right thing. Beyond that, YOLO.

If your architecture makes testing hard build a better one. If your tests arent good enough make the AI write better ones.

Re: Why is Claude an Electron app?

#138
post #109
post #87

This post and this entire thread are HN-sniping to the millionth degree. We have all the classics here: - AI bad - JavaScript bad - Developers not understanding why Electron has utility because they don't understand the browser as a fourth OS platform - Electron eats my ram oh no posted from my 2gb thinkpad

My guy if you can’t see the problem with a $300B SF company that of course claims to #HireTheBest having a dumpy UX due to their technical choices I don’t really know what to tell you. Same goes for these companies having npm as an out-of-the-box dependency for their default CLI tools. I’m going to assume anyone who thinks that every user’s machine is powerful enough to run electron apps, or even support bloated deps…

[deleted]

Re: Why is Claude an Electron app?

#139

Earlier quoted context omitted.

There's a pretty big difference between the understanding that comes with reviewing code versus writing it, for most people I think.

Definitely true for me. What’s particularly problematic is code I need to review but can’t effectively test due to environmental challenges.

Thats a tough situation. How do you handle the testing with human code?

Re: Why is Claude an Electron app?

#140

Because code isn't free. I can see it in my team. We've all been using Claude a lot for the last 6 months. It's hard to measure the impact, but I can tell our systems are as buggy as ever. AI isn't a silver bullet.

And after 12 months, most probably no one from your team will understand what the result of half of those bugs is. When devs outsource their thinking to AI, they lose the mental map, and without it, control over the entire system.

I find this such a weird stance to take. Every system I work on and bug I fix has broad sets of code that I didn't write in it. Often I didn't write any of the code I am debugging. You have to be able to build a mental map as you go even without ai.
Post reply on HN