I mean, yes, that's how it should be. Refactor it before implementing new features.
I would understand the extreme pushback on this if this made a priest go to hell.
I wouldn't. Religion shouldn't get a fucking hall pass for arbitrarily bad shit because "we don't want to go to the scary place we made up."
They may not technically have teeth but they have a serrated beak.
Silverbullet is nice
- Trombone Champ
- Pizza Tower
- Sekiro
Lol not from me
It would matter if they ultimately decided to break away from the Dems.
I'm not suggesting that my library is unversioned. It's totally version controlled, and users can upgrade to whatever revision they want to pull in the changes. The changes I make upstream don't affect anyone downstream until they decide to upgrade. It could even adhere to SemVer, but my problem remains: how to minimize rewriting user code? Is it better to have more small upgrades or fewer large upgrades? When is one strategy preferable to another?
I don't understand. If you are able to upgrade by just passing a new version number to an API, then the API signature hasn't really changed enough to necessitate any changes on behalf of the user, right? Like, the API function signature hasn't changed?
The kinds of rapid iteration I'm talking about might involve completely removing APIs and making large breaking changes to the API surface itself, requiring user code to be rewritten to some degree.
tatterdemalion
0 post score0 comment score
I'm only familiar with "spectrum" from linear algebra (spectral theory), but I'm not sure that's how people intend to use the word "spectrum" in this context haha.