Live data from Hacker News

Claude Code does our releases now

aluxian.com

31–40 of 81 posts

Re: Claude Code does our releases now

#31
post #25

This is a fine example of a process you really want to be deterministic being automated using something that is definitely not.

I did something similar in my hobby project - the agent was promoted, among the other things, to copy a signature from a build artifact into a json file. It worked fine until it didn’t - one day Claude 4 Sonnet randomly flipped one letter in the signature to something else. It wasn’t the end of the world, I catched the error because I always manually test if the release worked, but it shows that AI tools should not b…

> It’s slow, inefficient and error prone.

And really expensive, which is why AI companies want you to do that.

> Just ask the AI to help you write a proper workflow with code.

This.

Re: Claude Code does our releases now

#32

This is a fine example of a process you really want to be deterministic being automated using something that is definitely not.

What is the deterministic alternative you suggest? I’m not endorsing this release practice in particular, it scares me. But I have been involved in a lot of automation projects where perfection was the initial goal, and then abandoned because it was obvious that non-automated work was so imperfect. Human error is a fact of life.

The sibling comment from M4v3R covered this well.

Re: Claude Code does our releases now

#33

This is a fine example of a process you really want to be deterministic being automated using something that is definitely not.

What is the deterministic alternative you suggest? I’m not endorsing this release practice in particular, it scares me. But I have been involved in a lot of automation projects where perfection was the initial goal, and then abandoned because it was obvious that non-automated work was so imperfect. Human error is a fact of life.

If you really have to use an IA, at least use it to generate code once and use that. This way it's deterministic and you get a chance to understand what happens and to debug issues.

Not sure why IA could create something you couldn't however. And at least understanding what happens if part of the bundle.

Re: Claude Code does our releases now

#34
post #24

This is cool and all, but I don't see why this can't be accomplished (and more deterministically) with a bunch of bash/python scripts. I've seen that done and work well in several firms for decades.

Agreed. This prompt is very easy to satisfy with 1970s technology.

Re: Claude Code does our releases now

#35

This is a fine example of a process you really want to be deterministic being automated using something that is definitely not.

What is the deterministic alternative you suggest? I’m not endorsing this release practice in particular, it scares me. But I have been involved in a lot of automation projects where perfection was the initial goal, and then abandoned because it was obvious that non-automated work was so imperfect. Human error is a fact of life.

I am a DevOps Engineer, all the thing that he described in the prompt can be just done by Github Actions except the summary of the PR.

I don't condemn using LLM, but at least they could have use it in order to write better Github Actions instead.

Re: Claude Code does our releases now

#36
post #13
post #6

> So please: > 1. Check if there exists a release PR already. When you check, do not grep, just list ALL PRs. Why would you make AI do this when you can just do it with an api call or git. Does the author not know that there is a chance that it won't actuall list ALL PRs just because he put that in all caps? we have lost our collective minds that this person is proudly publishing this stupidity to the world. i hate t…

> can we pls ban these coders from the industry :( No, as these coders are what will ensure the rest of us will have a nice gravy train in 5 years.

Gotta wait for the crash first, when the buildup of poor code overwhelms the remaining few snr devs and mountain of those that are AI only.

Re: Claude Code does our releases now

#37
post #22

Earlier quoted context omitted.

The cadence of releases is not related to quality. There will always be variances depending on the codebase involved and organisational constraints and product velocities. I could easily say that more frequent or less frequent releases are also a cause for concern.

We are talking about a Gen AI startup that has a handful of employees here. They have little excuse not to implement CI/CD, unless they lack confidence in their product's quality.

Ignoring the Claude AI release, why does releasing 1 - 3 per week implies low confidence and quality issues?
Post reply on HN