Public Voice Network
- Smart Phone #2 88
- Skillz of the day 1818
- What are you listening to… 41644164
- Your Last Concert 369369
- AE shadows won't work 77
- Show some recent work 47664766
- QBN+ Challenge 26 4343
- Trailer Of The Day 387387
- Politics 1759317593
- intern -> job 1616
- Chick of the Day 1431314313
- the gif animation thread 1132111321
- DUBSTEP of the Day 369369
- Show your latest Pics 29702970
- Skateboarding. 596596
- Vid of the Day 1095610956
- blog 5557755577
- ♥ Things girls like ♥ 9595
- Pic of the Day 5935759357
- Key Note 22
- edge printing 1111
- New illustration work 1414
- instagram 201201
- PNG Fix 1010
Files on file server. 1111 Responses
Last post: 1 year, 10 months ago | Thread started: Mar 22, 10, 2:34 a.m.
- 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?
- Mar 22, 10, 2:34 a.m. – Permalink
- Jordy
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.

- Dog-earMar 22, 10, 2:38 a.m. – Permalink
- airey
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.


- Dog-earMar 22, 10, 2:59 a.m. – Permalink
- airey
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.

- Dog-earMar 22, 10, 3:03 a.m. – Permalink
- d_rek
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.


- Dog-earMar 22, 10, 5:43 a.m. – Permalink


