Timeline for Legacy code: what to do in regards to maintenance and moving forward?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28, 2017 at 16:25 | comment | added | eparham7861 | Things are changing to where everyone does pull in different directions, and in some cases, or some developers. get micromanaged to some other direction, and you start to see some developers "getting" to do small encapsulated objects and others that don't. To the point where the micromanaged developer(s) are "sometimes" required to change the small encapsulated objects towards the other direction. And, that starts getting into a vague/out-of-scope discussion on the question, which normally ends up being a "it depends" type of answer. | |
| Nov 28, 2017 at 15:31 | comment | added | Ewan | if the team doesnt agree on a coding style then my rule is the most prolific coder wins :) But yeah, if everyone is doing things dramatically differently it can be unproductive. Obvs if everyone is generally doing small encapsulated objects you can have competing styles in the same project without issue. | |
| Nov 28, 2017 at 15:21 | comment | added | eparham7861 | Yes, I do see your point as far as defining the new way. Currently, there is a reactive feel to how things are being developed now which leaves us with no real "new way". As far as my question and no defined new way, could there be a reason that I should keep modified, or new, functionality with some big object, given that it is with similar functionality/ideas, or could the changes become a hindrance rather than being consistent? (hindrance like coupling where the overall class works with one or more entities in a way that breaks/cannot follow some expected functionality) | |
| Nov 28, 2017 at 8:59 | history | answered | Ewan | CC BY-SA 3.0 |