Is there actually a name for the development model where you don’t have a single codebase for all your clients/device model/whatever but rather fork the codebase whenever a new client/device model/whatever comes along? You then continue your development in the new codebase and occasionally cherry pick some of the improvements for the older variants of your codebase (of which you eventually accumulate dozens if not hundreds).

@WPalant a mess 😅

@kzar Definitely. But given that this isn’t the first time I encounter it, I suspect that there is some more specific term.

@WPalant svn branching! :D

@piecritic Yes, that but without SVN. And distributed - they probably have to figure out which developer machine has the branch they are looking for.

Argh, just confirmed manually: yet another piece of code present in an old branch that makes absolutely no sense there. It’s missing from the branches that appear to be most closely related, normally it’s only present in much newer branches.

There go my efforts of establishing some kind of meaningful development timeline. No way of figuring out what was introduced when and in which order.

@kzar Very much a mess. https://infosec.exchange/@WPalant/115730698105042221 😬

@WPalant "makes perfect sense when you are in the business of breaking stuff so people have to pay you for fixing it" - https://dzone.com/articles/why-you-should-avoid-jsf

@WPalant
Is very common with videogame studios, for example, but I doubt it has a specific name.