Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@MammaNeedHummus it’s like an edge case but even more edgy or cornery in that case.
It’s a case that only occurs in very rare conditions. Sometimes it’s used as an argument to not care about the problem because it’s not common enough. -
@iceb domain driven stuff helps with modelling and dependency management when the problem space is large enough.
A lot of times it's not and using DDD just makes shit horribly complex. Also like anything is you don't use a model effectively it's worse than it you would do something intuitively.
One DDD codebase I work with is filled indirection (interfaces) to cross the layers. Horrible code navigation and abstractions for basically no reason at all. -
@hjk101 ya. I think those abstractions are not necessary while the idea of ddd still works without it. It's unfortunate that they have been bundled together
So when code is badly written, more corner cases are unnecessarily introduced. And it’s sometimes tricky to find the corner cases and probably messy to fix the corner cases.
And so the code grows in size as a result. And when these fixes to the corner cases are not well done, they introduce more corner cases.
So what results is a large collection of corner cases. Only corner cases remain when this goes on for a while.
Because of this, every new feature can be effectively translated to a collection of corner cases to be implemented.
As corners grow, triangles become circles and tetrahedrons become spheres.
I live in such a sphere.
rant