Re:Object Oriented Programming is Inherently Harmful
by codygman on Sunday November 30, 2014 @05:12PM
(#8678333)
How do redundant classes and interfaces improve maintainability over time?
Re:Object Oriented Programming is Inherently Harmful
by muhuk on Sunday November 30, 2014 @06:25PM
(#8678655)
Because they improve maintainability, they are not redundant.
Re:Object Oriented Programming is Inherently Harmful
by codygman on Sunday November 30, 2014 @08:21PM
(#8679041)
I asked how redundant classes and interfaces improve maintainability over time.
I'll narrow down my question some more:
How does duplicated code improve maintainability over time?
Re:Object Oriented Programming is Inherently Harmful
by hakunin on Sunday November 30, 2014 @11:02PM
(#8679447)
Author stated that classes and interfaces seem redundant, not actually redundant. Repeated code could improve maintainability because it may actually have different reasons to change, and only look similar on the surface. I've seen this often missed by inexperienced devs who get overzealous trying to DRY up everything.
This. 1000 times over. This is why well factored code bases can often seem to have lots of redundant classes and interfaces to inexperienced developers. It's all about maintainability over time, building bulkheads around change.
> tools that generated the right code—interface builders for example
The irony is that these tools often fail when the benefit is considered over time. This comes through a lack of tools - their code works badly with SCM (no domain-specific diff tools). They throw away everything we've learnt about software engineering just to win the marketing demo's.