4 ms·

> Windows used to have a version control called Visual Source Safe. > You'd have to select files you want to modify and check out them. Then they're locked. No

> Windows used to have a version control called Visual Source Safe. > You'd have to select files you want to modify and check out them. Then they're locked. No one else in the team can touch them. > God forbid you forgot to check them in at the end of the day and are not at work for a week then those files are locked and don't even have your changes. Holy shit, this is what lawyers still do--I always thought the developers who built the shitty enterprise software used by law firms knew this was garbage "version control", and wondered what they thought of it--but now you're telling me that the developers of that old dotcom era software themselves used a similar flow? for software engineering? insane

Natsu 3y ago
I had an employer who used MS-DOS + Novell Netware. Source was distributed with the application. If you needed changes, you had to pull the source file off the machine and send it to the developers. So the "same" application on different machines could have all kinds of minor differences. I hacked autoexec.bat to load the network and set some variables that identified each machine, then run another batch file stored on the network drive that did automatic weekly backups, copied new files back to individual machines on restart (without me having to run around with a floppy disk), etc. Once I got it set up, I did all further administration from my office, except the times I had to use the backups, in which case I would just xcopy all the files back onto the machine and run sys c: from my floppy disk.
- catlover76 3y ago
  Nice lol
EvanKnowles 3y ago
We used to use a VCS called Borland (yeah, Delphi Borland) StarTeam, which was basically the exact same flow. Luckily for us they audited us at some point, decided we were using too many licences, and insisted we triple our monthly expense or stop using StarTeam - that was the incentive to persuade business to let us slow down dev for a bit while we changed to Git.

Natsu 3y ago

I had an employer who used MS-DOS + Novell Netware. Source was distributed with the application. If you needed changes, you had to pull the source file off the machine and send it to the developers. So the "same" application on different machines could have all kinds of minor differences. I hacked autoexec.bat to load the network and set some variables that identified each machine, then run another batch file stored on the network drive that did automatic weekly backups, copied new files back to individual machines on restart (without me having to run around with a floppy disk), etc. Once I got it set up, I did all further administration from my office, except the times I had to use the backups, in which case I would just xcopy all the files back onto the machine and run sys c: from my floppy disk.

catlover76 3y ago
Nice lol

EvanKnowles 3y ago

We used to use a VCS called Borland (yeah, Delphi Borland) StarTeam, which was basically the exact same flow. Luckily for us they audited us at some point, decided we were using too many licences, and insisted we triple our monthly expense or stop using StarTeam - that was the incentive to persuade business to let us slow down dev for a bit while we changed to Git.