Live data from Hacker News

Claude Code does our releases now

aluxian.com

41–50 of 81 posts

Re: Claude Code does our releases now

#41
RemindMe! 3 months from now.

Willing to put down a little bit of my money that this is going to blow up in their faces in the near future.

I'm not super technical at all, but I don't understand why a team that does 1-3 deploys a week is not fully automating with "proper" CI.

Re: Claude Code does our releases now

#42
post #16

Earlier quoted context omitted.

> but your release cadence implies low confidence and quality issues. curious why would it imply that.

Why would a startup CTO choose to deploy a couple of times a week with a Claude script instead of implementing basic CI/CD? He makes it sound like he's running a clusterfuck and he isn't qualified for the job.

Aren't you assuming a bit much here? They have implemented CI/CD; their Claude script triggers the git branch part of the release flow, which is what in turn triggers the CI/CD pipeline—a completely normal thing to do, even in established teams (save for the Claude part).

The guy automated the toil away using AI. Not that I would feel confident automating away that part in particular, but it does neither speak badly of the code quality, nor his job qualifications.

Re: Claude Code does our releases now

#45
Please ask the agent to help write a workflow script (GitHub Actions yaml or makefile or similar) instead of using it as a runner - if you do that the release pipeline changes with each execution. You do not want a non deterministic release pipeline that's mostly correct. You want one that's checked in to version control and always does exactly the same thing, with all logs and artefacts recorded.

By all means use whatever AI agent you have to help set that up.

Re: Claude Code does our releases now

#46
post #30

We have a very small team and release at will. Some days multiple times, sometimes days between. We don't use AI, just have a well tested codebase and basic bash script automation mixed in with GitHub actions. Not bashing AI tools in particular, but just learning some basic decades old tooling and processes gets you pretty much all of the way there.

I tell my teams and stakeholders that releasing software is like exercising a muscle. It more it's automated, and the more frequently we do it, the less of a "thing" it becomes. Releasing should not be reserved for a single senior dev: any dev in the team should be able to release at any time, and the system should be set up with the appropriate guard rails to avoid stupid mistakes. Rollbacks should be trivial and everyone should know how to do it.

Re: Claude Code does our releases now

#47

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

Thanks for pointing out something which by some is considered unpopular. Use AI tools all you want but wherever you want deterministic outcome - current generation isn't up to that level.

We must acknowledge, understand and work around a technology's limitations.

Re: Claude Code does our releases now

#48
The author of this article is using AI to run certain console commands, while still requiring them to manually advance the release process.

Almost as if the author does not know how to write a bash script, and reverted to using an AI prompt in stead?

Re: Claude Code does our releases now

#49
Speaking of which - I was wondering if there is a catalogue of release processes? Variety, usual steps, checklists?

Asking because development processes are a hot market themselves think of XP, Scrum, agile etc so wondering if there's something documented about release processes.

Re: Claude Code does our releases now

#50
Is this not a bash script, but run through a "maybe it won't work this time" randomizer?

Sometimes I feel like I live on another planet. Wouldn't you at least get Claude to write the bash script, confirm it works how you like, then run that? Why get an LLM to guess how to do it each and every time?

At least they are still manually approving, which the title made sound like something they'd move on from.

Post reply on HN