Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Most places have no idea how to version software. Companies with a lot of legacy software tend to be worse, but most are awful.
So i wasn't writing code at the time but I had exposure to this practice, and it was roughly like you say, with maybe one important catch.
This also was with big bank clients and financial companies and all these different hot fixes was thought to be the cost of doing highly profitable business with them.
That didn't keep anyone from copying and pasting from one hotfix to the next, but all hot fixes were separate on a per client basis. You just didn't know what would get emphasized after they used a given hotfix.
Hotfixes were given a much shorter supported lifespan. Eventually our customers were expected to either upgrade to the more recent mainline code that also got the fix, or just live in unsupported land and in theory the answer was "upgrade and then tell us if you have the issue". Granted like all things some exceptions might apply, but one way or another all hotfixes got a shorter lifespan to avoid and endlessly growing old chunks of code.
asgs836620dHotfixes are only meant to firefight a pressing issue without delaying till the next stable release
It is unfortunate that you have to deal with Banks since it is not easy to work with in terms of technology, upgrades, etc. But your half ass RMs should fix this vicious cycle and reduce the maintenance headaches this practice ensues
raze63920dBasically you can only skip that on startups or other companies that have adopted DevOps practices 🤷🏻♂️
saas124620dThis is an abomination.
So, basically the git requirement in job eligibility is that one should know the git pull, push, fetch, commit commands. How to version, is not needed, not at all.