I worked at an agency where we didn't have version control. Usually, we could isolate projects and parts of work, and check in with each other. (I'll work on the news feed, you work on the profile page).
One time we took a "talking stick" approach with a Koosh ball. If the ball wasn't on your desk, you weren't allowed to update production.
There were lots of bugs and losing work was not uncommon. Wouldn't recommend it.
We used to post floppy disks with source code on them back and forth in the 80s - version control was 'open the files side-by-side and see what might have changed' ;-) Luckily in those days it tended to be one long huge file so it was easy to spot ;-)
Working with a department with the state of NJ and we currently don't have version control. We have a shared drive and create a folder π labeled with the change control number where the copy of the files changed live with documentation.
Where I work, there's still a large 1990's era monolith written in C (not even C++) powering some core systems (identity, access management, etc). Developers SSH into the server where all of the source files are and fire up Vim to modify files. Conflicts are prevented thanks to Vim lock files. Once a week, somebody compiles the whole tree and the resulting CGIs get moved to the production server.
The crazy thing is, it all works surprisingly well. Doesn't mean that we're not actively trying to modernize it all, though, especially since the developers who really know their way around the thing are all getting close to retirement.
1978? π³ I don't know, I just assumed version control tools were pretty recent. Maybe my idea of version control tools is just wrong π . How were you doing it back then?
Panvalet was around in the 70's. Many companies used mainframes and proprietary software. I worked at a small company with 30 folks in IT. A quick web search shows panvalet had more than 3000 customers. CVS was available in the 80's.
Top comments (13)
I worked at an agency where we didn't have version control. Usually, we could isolate projects and parts of work, and check in with each other. (I'll work on the news feed, you work on the profile page).
One time we took a "talking stick" approach with a Koosh ball. If the ball wasn't on your desk, you weren't allowed to update production.
There were lots of bugs and losing work was not uncommon. Wouldn't recommend it.
The "talking stick" approach... nice π
for real :-)
We used to post floppy disks with source code on them back and forth in the 80s - version control was 'open the files side-by-side and see what might have changed' ;-) Luckily in those days it tended to be one long huge file so it was easy to spot ;-)
cp current version_$(date +%Y%m%d%H%M%S)
I guess πold sharks !!! #respect
Working with a department with the state of NJ and we currently don't have version control. We have a shared drive and create a folder π labeled with the change control number where the copy of the files changed live with documentation.
π³ Why don't you have version control?
Where I work, there's still a large 1990's era monolith written in C (not even C++) powering some core systems (identity, access management, etc). Developers SSH into the server where all of the source files are and fire up Vim to modify files. Conflicts are prevented thanks to Vim lock files. Once a week, somebody compiles the whole tree and the resulting CGIs get moved to the production server.
The crazy thing is, it all works surprisingly well. Doesn't mean that we're not actively trying to modernize it all, though, especially since the developers who really know their way around the thing are all getting close to retirement.
Zip files I guess.
In the ages of assembly, Uncle Bob mentioned that they were printing codes of libraries (packages) on papers and sell them π
How far back to you have to go for "before version control tools". We had them in 1978 and I've used them ever since then.
1978? π³ I don't know, I just assumed version control tools were pretty recent. Maybe my idea of version control tools is just wrong π . How were you doing it back then?
Panvalet was around in the 70's. Many companies used mainframes and proprietary software. I worked at a small company with 30 folks in IT. A quick web search shows panvalet had more than 3000 customers. CVS was available in the 80's.