Earlier quoted context omitted.
> 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.
It’s amazing how often an LLM mocks or stubs some code and then writes a test that only checks the mock, which ends up testing nothing.
Why is Claude an Electron app?
481–483 of 483 posts
Re: Why is Claude an Electron app?
#482Earlier quoted context omitted.
Having 3x the apps generally means having 3x the support burden, and this is true with or without LLMs.
No it is not the same with LLMs because LLMs are a multiplier that makes the overall work less compared to without them, and that includes support burden. "Support" is a hand wavy word to dismiss the fact that it consists of writing code and fixing bugs, all of which LLMs can help massively with now. They meaningfully change software engineering which you are ignoring when you assume the same cost of pre-LLM developm…
These are not magic. If you have to maintain consistency and security across three different apps written in three different stacks, you are still going to spent 3x the effort.
Re: Why is Claude an Electron app?
#483Boris from the Claude Code team here. Some of the engineers working on the app worked on Electron back in the day, so preferred building non-natively. It’s also a nice way to share code so we’re guaranteed that features across web and desktop have the same look and feel. Finally, Claude is great at it. That said, engineering is all about tradeoffs and this may change in the future!