3 ms·
> not use CI/CD That is ludicrously bad advice. Setting up a straightforward CI/CD pipeline can take a couple hours and it instantly provides huge productivity
by hn_throwaway_99 4y ago
> not use CI/CD
That is ludicrously bad advice. Setting up a straightforward CI/CD pipeline can take a couple hours and it instantly provides huge productivity benefits.
I worked for a startup that didn't have an automated deploy pipeline and didn't have any tests. It was a complete shit show from day 1, and I will never work for that chaotic of an environment again.
I am certainly not for over-engineering early in a company's lifecycle, but there are simple, "table stakes" things like use of SCM, automated builds and CI/CD pipeline. If I don't see those I assume your engineering team doesn't know how to build software fast.
- andrewstuart 4y agoThe number of hours I have seen developers spend on things related to CI/CD is vast. Kill CI/CD with fire for the sake of speed. "Craptacular development mindset" is needed.
- selcuka 4y ago> The number of hours I have seen developers spend on things related to CI/CD is vast. Sure, same as everything else that is overengineered. A simple, no-frills GitHub Action (or equivalent) should not take longer than a few hours to implement. If you need more time than that, it means that you have an overly complicated deployment process, which is a time sink when done manually anyway.