|
|
|
|
|
|
by oblio
2019 days ago
|
|
|
> Serious blowback happens when you break something for some segment of your users. You don't have to break things to provide new features. Do you work in software development? 1. With that many users, you are going to break something for someone. Probably for tens of millions of someones, at the minimum. 2. At some point you will have to break something. Some of the new stuff will be incompatible with the old stuff. No one has a crystal ball. |
|
|
I've written software for over 20 years. C++ mostly, a lot of Python, some Xojo.
> With that many users, you are going to break something for someone. Probably for tens of millions of someones, at the minimum.
Maybe. I don't think it's a given though.
> At some point you will have to break something. Some of the new stuff will be incompatible with the old stuff. No one has a crystal ball.
Why? At no point does making something modular have to break something. Usually when something breaks during modularization it's because it was already broken and modularization simply made it need to get fixed.