3 ms·
> less manual work is always better. Why do your releases involve non negligible manual work? > We release 1-3 times per week. If I were a customer, I would
by mkl95 1y ago
> less manual work is always better.
Why do your releases involve non negligible manual work?
> We release 1-3 times per week.
If I were a customer, I would be concerned by this statement. Having an amateurish deployment strategy is one thing, but your release cadence implies low confidence and quality issues.
- apwell23 1y ago> but your release cadence implies low confidence and quality issues. curious why would it imply that.
- wmichelin 1y agowhy not have CI?
- Mashimo 1y agoBut the questions was about the cadence and not the method.
- mkl95 1y agoWhy 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.
- 9dev 1y agoAren'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.
- DonHopkins 1y agoBecause there is more toil in writing a blog post about how you use AI to do a release, than there is in writing a script that makes the AI and the blog post unnecessary. But then you wouldn't have something about using AI to blog about.
- 9dev 1y agoThat’s an entirely different issue: people maintain a blog to improve their hireability, and that entails blogging about things that may not always be brilliant insights. It’s not this person's fault that that’s the state of tech hiring however. Don’t hate the player, hate the game.
- AStonesThrow 1y agoBlogging is actually a good way for professionals to earn CEUs to maintain certifications. Chances are, if you’re reading low-effort blog posts that are consistently in certain knowledge domains, they’re intending to apply for CEUs at renewal time.
- DonHopkins 1y agoWell looks like he had the last laugh on us: GitHub was down, so nobody with CI/CD GitHub Action deployment scripts could make a release unless they used AI or did it by hand! https://www.githubstatus.com/ https://www.githubstatus.com/ Update - Packages is experiencing degraded performance. We are continuing to investigate. May 26, 2025 - 08:39 UTC Update - Copilot is experiencing degraded performance. We are continuing to investigate. May 26, 2025 - 08:26 UTC Update - Actions is experiencing degraded performance. We are continuing to investigate. May 26, 2025 - 08:25 UTC Update - We are continuing to investigate degraded performance. May 26, 2025 - 07:53 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. May 26, 2025 - 07:35 UTC Investigating - We are investigating reports of degraded performance for API Requests and Git Operations May 26, 2025 - 07:21 UTC
- rbinv 1y ago
- maeln 1y agoIt really depends on the product. Especially if 0-downtime deployment is not possible.
- politelemon 1y agoThe 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.
- mkl95 1y agoWe 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.
- Mashimo 1y agoIgnoring the Claude AI release, why does releasing 1 - 3 per week implies low confidence and quality issues?
- DonHopkins 1y agoBecause 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.
- Mashimo 1y agoYes 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.
- friendzis 1y agoIt 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.