Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 4
    Sounds like you need a better practice for developing new features. I personally like to build my projects to that it is easy to isolate features, usually in a separate file/class/or whatever. That way adding or removing code doesn't cause any major disruptions in delivery or problems when merging in new code, or pulling out old code. This works well when developing with multiple developers as well. But I can understand if you're working a project that may not have been started by you, or you have no real say-so as to how the project continues. Commented Sep 13, 2011 at 13:50
  • 1
    @b01, Thats pretty much spot on. Nobody can come up with the perfect design when requirements go back and forth and change faster than an ADHD child on crack. Other times you end up trying to refactor legacy code to improve the design and this situation does come up from time to time. It isn't the worst problem a team can have, and is a far cry better than some places I worked where even suggesting refactoring in a meeting will get you beat to death with a baseball bat like a scene out of The Untouchables. Commented Sep 13, 2011 at 14:14
  • Totally disagree. If you split by quality branches, and merge frequently (daily is good), then you avoid nearly all "manual and error-prone" merges. Commented Sep 13, 2011 at 15:58
  • @Paul, Trust me that doesn't work for all projects or technologies. Think of a common XML configuration file like in Struts where everybody is dipping their hands into it everyday. But no, your way works all the time and I totally deserved the downvote. Thanks. Commented Sep 13, 2011 at 17:07
  • 1
    @maple_shaft meta-hint, if you consider the tags (git) and post something the typical user of those tags would consider a negative, expect flyby downvotes. Flybys are almost always unjustified reaction to being butt-hurt by some comment you take personally. Consider it good because it boosts your rep through he roof. Commented Sep 13, 2011 at 20:26