“What was your biggest challenge?”
Just now coming up on the one year mark of being unemployed, and having gone to about a dozen different interviews now, one of the most common questions I hear is “What was your biggest challenge?” or “Describe a time when you had a particularly difficult challenge and how you resolved it.”
In order as I think of them:
Apple and it’s lack of Enterprise support
Node locked software on a machine that just died, it out of warranty and the company refuses to return support phone calls or emails.
The user who doesn’t understand that going to certain web sites pretty much automatically means the machine is getting a virus.
Being asked to deploy non-existent machines to user who were hired only a few hours earlier and are scheduled to start the next day.
Explaining what “Corporate Standard Software” means, and why I can’t simply give you a license number so that you can install at home “to learn”
Complaints about machine slowness and weird problems to find that the uptime is 45 days.
User who upon being told “Those computers are too old, you will not be happy with them when I’m done,” buys new computers (from someone else,) the next day and then expects them to be installed for free after I’ve already done all the work.
Users who do not contact their IT support at all when there is a problem, then go home for the day because they “can not get any work done.”
Being expected to install a 15 computer network within 8 hours, never having done so ever before (it’s harder then it sounds)
Users who expect something done their way when it’s technically impossible.
The above, but when it’s illegal or unethical
Explaining to your direct supervisor why you REALLY don’t want to see the Midget Porn Website they found
Yeah. All of those.
How To: Disable ._ Files and .DS_Store on Network Shares
In heterogeneous networks of Macs and Window users, few things tick off Windows users then the “droppings” Macs leave behind in the form of files with . or ._ in front of them. These files are known as resource forks on the Mac side and store all kinds of really nifty information that makes OS X interact with files quicker and more efficiently. Among their uses they store metadata about files such as keywords, file size, and preview information.
None the less for various reason Windows (and to a lesser extent, Linux) is not able to always ignore these files and automatically sorts them to the top of the file view list. These files tend to be confusing if one is not aware of what they are. Or worse yet cause problems in directories with thousands of files present.
If on a small network with only a few Macs there is a program that takes care of this automatically. For $13 BlueHarvest works just perfectly.
Of course there is a simple trick to disable .DS_Store files. In Terminal run the command:
defaults write com.apple.desktopservices DSDontWriteNetworkStores true
If the network is Leopard only, then editing nsmb.conf is a good trick too. In /etc/nsmb.conf look for the following line: streams=no and change to streams=yes .
If the file does not exist, then it can be created via TextEdit or VI.
These files are only viewable under very certain circumstances but they can cause a lot of coworker friction, and worse yet even cause management to question the usability of OS X in the work place. These simple tricks will go a long ways to resolving those issues and making work much more friendly.