DEV Community

Discussion on: Are We Really Doing Continuous Integration?

Collapse
 
andrewcahill profile image
Andrew Cahill • Edited

Hi Jesse,
Thanks for your comment. I fully understand the concerns on this and I had the same concerns due to potentially causing more pain & headache due to the extra effort in co-ordinating finished vs unfinished work.
However, my thoughts around this are not necessarily a right vs wrong scenario rather an ideal to work toward and put in place the necessary processes to allow for unfinished work to be committed such as feature flags etc.
This will allow you to commit not only unfinished work but to your point work you may soon later realize there is a different perhaps preferable approach and update this code ahead of going live.
Yes, there will be issues committing unfinished work if safeguards are not in place however I don’t think this is a reason not to do this as there are definitely advantages of committing with this frequency. So, I think the path is if this is not possible right now - fine however working towards this over time will ultimately yield superior agility.
I would almost compare this to DevOps - there are upfront costs associated with putting in such processes and infrastructure but you believe will pay off afterwards.