3 ms·

Its a bit too extreme to trump it. But in big corporations, especially in some small branch that can't make the processes and restriction of big corp work with

Its a bit too extreme to trump it. But in big corporations, especially in some small branch that can't make the processes and restriction of big corp work with limited resources, its normal to wait for computer for 1 week. You can't do much, since any studying of internal stuff requires... computer. Its not so nice when you see an external guy burn through 10k$ budget in a week and all he can do is watch his phone for 8 hours a day. The rest, just wow, 1-guy subversion via usb sounds like a bad story from 1999. Anything non-trivial would be impossible to ship in any reasonable quality, ever. Normally management is not that comically incompetent (and worse).

trashtester 4y ago
There are still plenty of people not using any kind of source controll system at all. Particularly among data scientists, DBA's, etc.
dcminter 4y ago
No single element of it was really unusual at the time. It was the lunacy of everything simultaneously that made it truly memorable. I do think we have it pretty good these days. In particular, the dev-ops movement has pretty much put an end to the days of waiting for a server to be made available to a new project. > The rest, just wow, 1-guy subversion via usb sounds like a bad story from 1999. Heh. According to Wikipedia USB sticks went on the market around 2000. But yeah, zip drives or something. But there'd have been reams of printed documentation in binders (or badly stapled realistically) and JIRA wouldn't have been a thing, so perhaps a net win :) My first gig after university we moved all the files around on 3½" floppy disk and I'm retrospectively embarrassed by my resistance to a colleague's insistence that we start using a CVS server instead!
- gumby 4y ago
  > I'm retrospectively embarrassed by my resistance to a colleague's insistence that we start using a CVS server instead! If it makes you feel better: back around 1991 or 92 one of our employees insisted that we implement version control, specifically CVS. Gilmore and I were extremely opposed and made a long list of absolute requirements (e.g. “100% transparent in emacs with no change to anybody’s work flow”) — all requirements to be fully met or no go. The guy behind this installed cvs, moved the code into the repo, and completely ignored our stupid “requirements“ list. Of course it was such a win that neither John or I ever mentioned our list. The story of how (or rather why!) we wrote cvsserver is hair raising too.

trashtester 4y ago

There are still plenty of people not using any kind of source controll system at all. Particularly among data scientists, DBA's, etc.

dcminter 4y ago

No single element of it was really unusual at the time. It was the lunacy of everything simultaneously that made it truly memorable. I do think we have it pretty good these days. In particular, the dev-ops movement has pretty much put an end to the days of waiting for a server to be made available to a new project. > The rest, just wow, 1-guy subversion via usb sounds like a bad story from 1999. Heh. According to Wikipedia USB sticks went on the market around 2000. But yeah, zip drives or something. But there'd have been reams of printed documentation in binders (or badly stapled realistically) and JIRA wouldn't have been a thing, so perhaps a net win :) My first gig after university we moved all the files around on 3½" floppy disk and I'm retrospectively embarrassed by my resistance to a colleague's insistence that we start using a CVS server instead!

gumby 4y ago
> I'm retrospectively embarrassed by my resistance to a colleague's insistence that we start using a CVS server instead! If it makes you feel better: back around 1991 or 92 one of our employees insisted that we implement version control, specifically CVS. Gilmore and I were extremely opposed and made a long list of absolute requirements (e.g. “100% transparent in emacs with no change to anybody’s work flow”) — all requirements to be fully met or no go. The guy behind this installed cvs, moved the code into the repo, and completely ignored our stupid “requirements“ list. Of course it was such a win that neither John or I ever mentioned our list. The story of how (or rather why!) we wrote cvsserver is hair raising too.