[nonines]

The point I think you're making is that "it depends" and I agree with it.

I've seen companies that have no funding issues building products that they know they will need to maintain in coming years and still follow a few or none of the best practices.

But I've also seen people building SW that no one can guarantee that will ever be used (and gets scrapped after a few months) spending days and weeks setting up the perfect agile CICD setup and arguing in endless pedantic discussions in code reviews.

[rezonant]

All things with balance, and I agree analysis paralysis and overengineering are real problems to avoid...

but I'm sorry you can't deploy without CI/CD unless it's like a desktop or mobile app or something. You don't skip that for servers. Does it have to be perfect? Hell no, but it needs to be in place before you can seriously call it shipping

[phonebanshee]

I'm guessing that you work on server-side stuff, because most people who do mobile/desktop work would say exactly the opposite if they desperately had to come up with a general rule: do whatever you want for servers, but you have to do things right for mobile/desktop. Those are your servers, and you can fix them whenever you want. You push software to end users, and it's gone forever.

[rezonant]

I do, mostly. Also anticipated there'd be at least one mobile/desktop app dev who would swoop in to say it's important there too and I agree! It's just so common to have two servers to deploy to, and as soon as you do, you aren't going to repeat manual steps to deploy your software on them. I guess in that sense app stores are sort of like CI for apps :-P

But indeed, especially on mobile where you need to have releases go through external validation, CI/CD can save you a lot of time.

[gowld]

Plenty of Unicorn IPOs disprove this thesis.