undefined | Better HN

0 pointsmkl9510mo ago0 comments

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.

0 comments

Mashimo10mo ago

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

friendzis10mo ago

It means you release whatever you have first thing and then release a bunch of patch releases on top as the QA (outsourced on users, probably) results come back.

Sans security patches, why are your features not sized to roughly a sprint? What do you manage to prepare, build and validate in a day or two? To me release cadence less than every few weeks screams "whatever landed in master is good to go" and is a sign of mis-/un-managed development.

Mashimo10mo ago

Maybe they don't do sprints.

Yeah, could be user feedback. And if it's a public beta release why not?

3 devs working for 5 days on each their feature means 3 releases per week.

For the last 10+ years I have been working on the same project with 2 releases per year, so what do I know. But I have used projects with quick release cycles that work very closely with the community. Push new beta, feedback on discord. Was also fine from my (limited) perspective.

DonHopkins10mo ago

Because they should be spending one day writing scripts and github actions for their CI/CD system before pushing out new code by hand or AI assistance several times a week.

Releasing 1 - 3 times a week means it's 1 - 3 times more important to have a deterministic release process than if you release 1 time a week.

Mashimo10mo ago

Yes yes, I agree with a deterministic release process. I get that, and it's not what I'm asking about.

I still don't understand why 1 - 3 releases per week implies low confidence and quality issues.

j / k navigate · click thread line to collapse

0 comments

Mashimo10mo ago

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

friendzis10mo ago

It means you release whatever you have first thing and then release a bunch of patch releases on top as the QA (outsourced on users, probably) results come back.

Mashimo10mo ago

Maybe they don't do sprints.

Yeah, could be user feedback. And if it's a public beta release why not?

3 devs working for 5 days on each their feature means 3 releases per week.

DonHopkins10mo ago

Because they should be spending one day writing scripts and github actions for their CI/CD system before pushing out new code by hand or AI assistance several times a week.

Releasing 1 - 3 times a week means it's 1 - 3 times more important to have a deterministic release process than if you release 1 time a week.

Mashimo10mo ago

Yes yes, I agree with a deterministic release process. I get that, and it's not what I'm asking about.

I still don't understand why 1 - 3 releases per week implies low confidence and quality issues.

j / k navigate · click thread line to collapse