The main goal of continuous integration is to identify the problems that may occur during the development process earlier and more easily.
No it is not. It causes more problems and wasts developers time on stupid unit tests.
The reason is very simple, you create lazy developers that just do something until the code gets green again. And worse of all it makes your projects suck in the end. You have code rot and you don't realize until the project is dead.
Continuous integration explodes the number of developers it need to develop and with more developers you need team leaders and then managers for these team leaders.... Then expensive build servers then expensive automated unit tests.
I see the results of these Continuous integrations all the times. The green status LED means absolute nothing. Under that green LED status you have design flaws that no one questions. You are creating a project that is destined to fail because no one questions if that code is doing what it is supposed to do.
1 comment
0 u/roznak 22 Feb 2017 21:18
No it is not. It causes more problems and wasts developers time on stupid unit tests.
The reason is very simple, you create lazy developers that just do something until the code gets green again. And worse of all it makes your projects suck in the end. You have code rot and you don't realize until the project is dead.
Continuous integration explodes the number of developers it need to develop and with more developers you need team leaders and then managers for these team leaders.... Then expensive build servers then expensive automated unit tests.
I see the results of these Continuous integrations all the times. The green status LED means absolute nothing. Under that green LED status you have design flaws that no one questions. You are creating a project that is destined to fail because no one questions if that code is doing what it is supposed to do.