Files on file server.
- Started
- Last post
- 11 Responses
- mydo
We have a file server in our office. it works really well. even wireless there isn't much speed difference to working locally. yet 99% of the team copy files to their computer, work from there, then uploaded them back to the file server when they are done.
is it just me that thinks this is wrong? or is this pretty standard way to work?
- lambsy0
what would happen if more than 1 person opened and worked on the same file at the same time? is that even a possibility? that's the main reason i can think of.
- Jordy0
Because saving to your harddrive is still faster and more responsive I think. It's also a bit safer in case you lose connection one way or another and close the file without saving or who knows what stupid mistakes people make in that case ..
Just saying .. in our office people do it too.
- and yes, more people working on the same thing at the same time is prevented.Jordy
- Ruffian0
Sound like the right way to do it.
- airey0
sounds like your team are fucking idiots.
the whole point in a server is to store and work from. there's no way the drive or the ethernet cables should be slow enough to make any difference on the working speed. if there is a speed problem then the fileserver must be a turd. i was using a novell server in '96 that was fast enough and that was a long fucking time ago.
- airey0
the idea of copying the files to your server and then copying back is regressive and decided around false logic.
if the server interupts you still have the file open so you can save locally, although this has happened once in 14 years for me.
if you copy the files off, you run multiple risks:
a: someone else can edit the file. meaning 2 or more edit a file then the last person to copy it back wipes any othe redits
b: the person working on the file forgets to copy it back (majority or fuck ups in anything is the people element) and you end up with an older copy on the server. which means an older version is backed up and if the person forgets or is away the next day and someone else goes to work on the file they're going to have the older version.
- mydo0
right, so that's 2 of us.
I believe the only thing you should have on your local machine is freelance work you don't want your boss to see, porn and huge video files. (but i'm not talking video here)
- Stugoo0
if you are talking code then you should consider source control like SVN GIT or Mecurial, copying to and fro servers is a minefield.
Had too many instances working like this before when wires are being crossed and things can get royally fubard
- we have a SVN for code. i'm talking ai psd indd ppt docmydo
- mydo0
actually MS word and ppt has impressive version control by default when sharing files across a network.
- d_rek0
mydo,
I work exactly the same way at our office, and in all honesty, I much prefer working directly off of the server than to working locally. We have a small staff so speed isn't an issue. I can only recall one time where our server was experiencing some issues and it interrupted me from working from it.
The ONLY issue i run into is when coworkers work locally and don't place updated files onto our server.