3 ms·
Ask someone who has worked on a long-running project before CI and code reviews became common. If the choice is between slow and randomly failing CI and no CI o
by oriolid 4y ago
Ask someone who has worked on a long-running project before CI and code reviews became common. If the choice is between slow and randomly failing CI and no CI or code review at all and mistakes getting noticed when the software is finally tested weeks or months later, I would always choose the CI. It would be nice if everyone in the team was omniscient genius who never makes mistakes, but sadly I am not one and I haven't met anyone who is yet.
- civilized 4y agoMeetings, CI, etc. are all good things in moderation, but people could be more productive by applying more judgment to the question of when to do them. If you're like a typical colleague of mine, you aren't needed at 80% of the meetings you attend, and you don't get any value out of those meetings either. Your attendance at these meetings is essentially a mindless way to run out the clock on the day.