true, bad abstractions due to lack of understanding and/or motivation, simple code duplication, mechanics over thinking.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Another advantage of microservices

-
I love micro services- but that is coincidental. Modularity , divide and conquer and separation of concerns was always a solid design principle since decades- one could do it with almost all languages and methodologies.
- Show replies
New conversation -
-
-
What do people do when they can't refactor? They just copy it, or wrap around the buggy piece of software. Thus creating more bloats like you said.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This Tweet is unavailable.
-
Most big Corporate IT enterprises have a very low adoption of micro services - monolith is still the norm. If you mean the big tech companies started in last 2 decades- Amazon, Google etc, that is a different question. History matters and lives long roots.
End of conversation
-
-
-
Thats why I say the open/close principle should be a design goal, but not a rule in refactoring. Bloat and complexity builds from not opening components for refactoring when they should be, and instead adding on layer-upon-layer like a fossils getting buried.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
p=mv The momentum of big software projects is what's particularly tough to overcome.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Could the same thing be said about companies/organizations? Try pivoting a company like GE vs AirBnB.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That’s why Services need to really be Micro...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.