I started at a place that had

store_v1.js

storev2.js

store4.js <----- this one was the newest, and current production version

store_new.js

store_newest.js

I got their head engineer fired by explaining to the CEO what industry best practices were and how incredibly common and valuable they were (and honestly, the engineer got himself fired by refusing to even consider changing his ways). I introduced concepts like "store your products, sales, and user data in a database instead of a flat file" and "use version control" and "use a deploy script that supports rollbacks". Then I quit for a better paying job.

The CEO complained that I convinced him to change everything in the software stack and to get rid of the guy with 15 years of experience there, and then bailed on him. I pointed out that $40k/yr is not enough to buy loyalty. Last I heard he got acquired by a bigger company who threw out our entire estore anyway. He's doing great.

That doesn't mean that _you_ can't use version control. Or just introduce it to the company.

I introduced Git at an industrial automation firm.

A handful of folks thought it was "pretty cool", everyone else kept on versioning with myriad copies of "Copy of plc_control-1a (new) (final) (1) (b).ACD"

Oh, I tried.