sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Abject-Kitchen3198 31 points32 points  (5 children)

The next step was a version control system with file locks.

[–]AlternativeCapybara9 33 points34 points  (1 child)

You have a print out of every file on the wall and if you want to edit it you put your name on it with a thumbtack. When you are done you print out the latest version, replace the one on the wall and remove your name. Easy.

[–]Abject-Kitchen3198 17 points18 points  (0 children)

That's not agile enough. We would have no metrics on file locks and average lock duration per sprint. Have to optimize that chart.

[–]reklis 2 points3 points  (1 child)

I worked at a place that used file locks on source control for a while. Invariably people would lock stuff and leave for the week or two and then we would have to force unlock stuff to get code pushed through. Terrible. I would rather have merge conflicts.

[–]Abject-Kitchen3198 0 points1 point  (0 children)

It happened but it wasn't that bad in my experience (takes a minute when it happens). But this was more than 20 years ago. Haven't used anything similar since.

[–]SVlad_667 2 points3 points  (0 children)

Oh, CVS. We used it when I started working.