Well ... that's *one* way to do it.
-
From here
I recently encountered a situation in our codebase where a different team created a 'god class' containing around 800 methods, split across 135 files as a partial class.
I asked the other team about this. While my gut reaction was to nuke it from orbit, they insist that it's a good design, a common practice, and that it promotes 'modularity' and 'ease of implementation' because new developers can bolt on functionality with almost no knowledge of the rest of the system.
All I can think is run away, run away.
-
-
@svieira said in Well ... that's *one* way to do it.:
All I can think is run away, run away.
listen to your instincts, young padawan, they will guide you well.
-
Sounds like they have a class only in the technical sense, with a whole procedural program embedded within it.
-
@svieira I think they might be right about “a common practice”.
-
@svieira said in Well ... that's *one* way to do it.:
new developers can bolt on functionality with almost no knowledge of the rest of the system.
You don't need to know the rest of the system if there is no "rest of the system". Makes perfect sense to me.
-
@svieira said in Well ... that's *one* way to do it.:
All I can think is run away, run away.
Naw, that's just a function library. We had those in the old days, before all the kids started believing that OOP was the magic bullet that was going to Fix Everything.
They work OK if they're well maintained and fail horribly when they're not, just like everything else.
-
@JBert Yep, that's me.