Hacker News new | ask | show | jobs
by arielweisberg 3887 days ago
Being able to merge in progress development to your main branch is an important part of reducing product in development and reducing cycle time. When dealing with big features that aren't going to reach a viable end user visible state for months to years it can be a real challenge especially when what your are working on feels like a it "touches everything."

This is more than just the technical capability. I've been on teams that insist they are completely unable to iteratively develop and deliver big features. As a result you end up with huge impossible to review patch drops at the ends of months of work behind closed doors. It's a disaster every time.

I'm still struggling to communicate to people how to do it and what the benefits are.

1 comments

I'm well aware of the concept and have been doing this for years in my company's web apps. My sarcasm comes from seeing this covered as a revolution in software engineering as opposed to the application of some rather old concepts with new UI and broader application.