We detached this subthread from https://news.ycombinator.com/item?id=13514538 and marked it off-topic.

> EDIT: The downvoting system on HN optimizes for older, over the hill developers as is shown here once again.

This is pretty lame. You're both whining about downvotes and calling everyone who disagrees with you old.

I don't know what your concern is with feature flags. Maybe the way you've implemented or used them in the past has been problematic. But when your approach to disagreement is this petty, it makes me think you are unlikely to be able to discuss it meaningfully anyway.

I would say for backend you can get away without feature flags most of the time. But for the frontend, it's almost impossible to ship a new incomplete feature without feature flags

That's actually a very valid point. I was not thinking as much about HTML/CSS as I haven't been involved in a lot of large scale frontend refactors.

> EDIT: The downvoting system on HN optimizes for older, over the hill developers as is shown here once again.

Or that making gross generalizations like yours and speaking in absolutes demonstrates lack of experience and immaturity.

> EDIT: The downvoting system on HN optimizes for older, over the hill developers as is shown here once again.

Oh, so this is what ageism looks like? I see.

> There are a few times when you need to, but features can in most cases be written in a way that they can live inside production before complete.

That should never, ever, ever be done.

Why not? Loads of companies do this. Almost all the big ones I know of do this.

Really? http://techcrunch.com/2011/05/30/facebook-source-code