Comment IPhone Nano ... (Score 2, Interesting) 231
Looking forward to teeny tiny iPhones
Looking forward to teeny tiny iPhones
You need to read Scott Adams' "The Joy of Work." If you really want to write articles and be in Marketing don't volunteer to do IT stuff. Clearly, your strategy of "quick and courteous service" (see page 40) is not working out for you.
I find Adobe proprietary apps like pdf viewer and flash to be very annoying. I would love a nice rain to wash that mud away.
I agree, have you ever read a http://en.wikipedia.org/wiki/Raymond_Kurzweil book ? the guy can not write a decent paragraph. He should stick to synthesizers. I think that computers are instruments or tools like telescopes or microscopes. They allow us to peer into a universe of logic and math but, they are not 'intelligent'
Having worked at UUNET/Worldcom I can tell you that building and maintaining infrastructure is a pain. What is Google going to do when a backhoe digs into their fiber feeder? I predict it will be 'beta' for a while and then dropped quietly.
How about customer service? Where is the 800 number? Oh I am just 'Labs' experiment? Sorry for bothering you. What is the name of that guy in the video, can I call him?
It's not like it's the Accounting department or HR. I have my own open source lab in my home.
print "DEBUG: This is not a comment\n";
As long as you manage expectations and, make management aware of the costs vs. risk.
There are a lot of factors that determine the manpower needed:
1) Are backups of files required by all users or just a few users (ie CEO, finance, hr etc)
3) What is the expected work hours 24/7? or 8/5?
4) How much redundancy is built into the servers? If they are in pairs then one can go down and be fixed during regular work hours.
5) How is your storage set up ? Disk drives fail so you will need RAID, mirroring etc
6) Have the servers been properly maintained ? A lot of times applications are put on servers without correct startup and shutdown scripts. If there is a power outage and the servers are cycled they should come up correctly with all applications.
7) Do you have a monitoring system in place to try to catch problems before they become catastrophic failures.
8) Do you have good configuration management so that the systems are as identical as possible.
9) Do you have routine maintenance items automated - this is easier if you have item 8 above.
All of these have cost and risk associated with them so it is important to go over them with management. You can explain how if you don't have a decent backup plan then data can get "lost."
If you are a one man IT shop then you can control your own work flow. Keep cryptic notes and todo lists in notebook in a journal style. File emails in different folders. It is funny but it works like a dynamic priority system. The hot projects will pop up any you will not have trouble remembering what to do. The repetative housecleaning tasks are good to do when you get tired of the 10 other things you need to do. One of the most rewarding things is going back through your notebook and cross of completed tasks. If you are good and can produce a lot of results then the management will not try to impose a "Time Management" system on you.
To the systems programmer, users and applications serve only to provide a test load.