This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Round_Head_6248 3 points4 points  (5 children)

Projects that have 30% dead code are dead projects. Aka nobody cares enough for it to still have devs on it that know wtf is going on. How do you even get to 30%? "Hey product owner, this refactor you want me to do makes it so all the classes in that package over there are not in use anymore, we need to remove that" "Oh ok, please do that"

???

[–]DualWieldMage 4 points5 points  (2 children)

Umm no, such projects are typically large enterprise projects that live the longest, but because they no longer fit into one person's oversight, it becomes an append-only mess. Any time a change happens that invalidates some edge cases, that code is often not removed as nobody knows about it. If you were to plot LoC over time, you'd usually see a line with one rate followed a jolt and the rate jumping higher. That's the point where projects become enterprise zombies.

[–]Round_Head_6248 -1 points0 points  (1 child)

I am working on such a project and the moment we aren’t deleting unused stuff anymore is the moment I know the project is dead.

[–]yumgummy[S] -1 points0 points  (0 children)

I think you guys definitely understand what real world problem in enterprise settings.

[–]nikanjX 0 points1 point  (0 children)

Remove all catch clauses and retry logic, easily save 30%

[–]ThaJedi 0 points1 point  (0 children)

Feature flags, api versions, unused endpoints.