Claude recently tried to replace a html sanitizer with a custom regex that perfectly fit all our tests as well as the spec I wrote

It’s a lot of fun for exploring ideas. I’ve built things very fast that I would not have done at all otherwise. I have rewritten a huge chunk of semi-outdated docs into something useful with a couple of Prompts in a day. Claude does all the annoying dependency update breaks the build kinds of things. And the reviews are extremely useful and a perfect combination with human review as they catch things extremely well that humans are bad at catching.

But in the production codebase changes must be made with much more consideration. Claude tends to perform well ob some tasks but for other I end up wasting time because I just don’t know up front how the feature must look so I cannot write a spec at the level of precision that claude needs and changing code manually is more efficient for this kind of discovery for me than dealing with large chunks of constantly changing code.

And then there’s the fact that claude produces things that work and do the thing described in the prompt extremely well but they are always also wring in sone way. When I let AI build a large chunk of code and actually go through the code there’s always a mess somewhere that ai review doesn’t see because it looks completely plausible but contains some horrible security issue or complete inconsistency with the rest of the codebase or, you know, that custom yaml parser nobody asked for and that you don’t want your day job to depend on.

Comments URL: https://news.ycombinator.com/item?id=47100532

Points: 4

# Comments: 2

They ended up adding dependency files later on to make it possible to keep package versions in sync without changing every file on every version change.

Comments URL: https://news.ycombinator.com/item?id=41889394

Points: 3

# Comments: 2

We're essentially a bunch of passionate engineers but none of us care for ops work including myself, I really want to focus on the code, not on the deployments.

Vercel actually kind of saves us money because the apps we work on are mostly internal tools that don't have millions of requests per minute and developer time is expensive. If vercel saves us one hour of engineering work per month compared to aws it's already cheaper and it definitely saves more than one.

Thanks to the odd scroll container i cannot zoom to a view where i do not have to side-scroll anymore.

10 years ago you'd deal with communicating stuff between language borders, what interaction to handle in javascript, what in ruby/php/perl/whatever and how to interact between the languages.

Now you deal with build processes, transpilers, bundle size optimization, framework configuration and broken react state updates.

It's intrinsically complex, deal with it.

https://postimg.cc/N509Z8Kr