Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

First Thing IT Managers Do In the Morning?

Posted by kdawson on Sun Jul 08, 2007 04:57 PM
from the beeline-for-coffee dept.
An anonymous reader writes "When I was a wee-little IT Manager, I interviewed for a position at an online CRM provider in San Francisco, a job I certainly was qualified for, at least on paper. One of the interviewer's questions was 'What is the first thing you do when you get to work in the morning?' I thought saying 'Read Slashdot' wouldn't be what he was looking for — so I made up something, I'm sure, equally lame. I didn't get the job. But the question has stuck with me over the years. What do real IT and MIS managers do when they walk in to the office in the morning? What Web sites or tools do they look at or use the first thing? Remember, this is for posterity, so please be honest."
+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by Evil Al (7496) on Sunday July 08 2007, @04:59PM (#19792811) Homepage
    Coffee machine, foo!
    • yup. first thing is coffee.
      after that, check the whiteboard on the door to my office to see where the problems are; when you have 6000+ systems and a cluster in each state and a few overseas, their is always a problem somewhere.
      If anything is on fire, head to level 2 and check with the nightshift to see what the heck is going on before they escape.
      If the fire is local, walk down to the NOC and see whats up, put out fire if appropriate. if it's in Dallas or Seattle or Guam, see the status of the local admin on the ticket queue, get on the phone if I see something they don't; start a team re-tasking operations at the site if it looks like it's going to take a while; downtime is not an option.
      if it is Biz as usual, walk in, fire up the computer, and check the infrastructure; check the queue on SMS to see if anything major is being pushed today, basically just look around to see if there is anything that is going to require me to earn my salary.
      if everything is smooth, or being handled, check e-mail; then, slashdot until the 10AM meeting.

      sometimes I wonder why I retired. then, I remember. Paperwork sucks.
    • by scotch (102596) on Sunday July 08 2007, @07:30PM (#19794065) Homepage
      Probably a big dump. Why can't people shit at home? They were just there half an hour ago.
      • by DutchSter (150891) on Sunday July 08 2007, @08:00PM (#19794291)
        Probably a big dump. Why can't people shit at home? They were just there half an hour ago.

        Expense reduction. The company's doing it, so why shouldn't I? They expect more productivity out of me and instant availability at no extra cost to them. Since it's costing me more to work there, I need to cut my expenses as well. Until I got married, it was possible for me to go an entire month on a single roll of toilet paper because I "timed" everything to always have to take that "7:30 conference call" in room 4-RM (4th floor Men's Restroom).

        Of course my boss still got the last laugh. He gave me a Blackberry. Now I take a dump while my computer boots up, but I use the extra time to get a jump start on my emails using the Blackberry. Drat, foiled again...

        Plus I'd rather be in the building at 7:30 and seen for a short while than show up at work at 7:45 because I opted to take care of business at home first. Yes my current job is like something out of Office Space.
        • by digitig (1056110) on Monday July 09 2007, @06:47AM (#19798453)

          Of course my boss still got the last laugh. He gave me a Blackberry. Now I take a dump while my computer boots up, but I use the extra time to get a jump start on my emails using the Blackberry. Drat, foiled again...
          One more nail in the coffin of widespread adoption of mobile video conferencing.
    • by curusetae (1067168) on Monday July 09 2007, @03:32AM (#19797445)
      I do psychological job interviewing for client companies here in an European nanny state, but I'd like to believe we look for similar things in job applicants.

      We ask questions just like this regularly and actually "coffee" would very likely be the single best way to start your answer.

      If you are in an interviewing situation, it is already known that you are competent from a technical viewpoint so we don't need to hear about any cool monitoring software you'd like to install. Personality type and efficiency in work are the traits the interviewers are after, more so for manager level positions. An honest and (to some point) witty beginning for a question like this is a good way to start. Don't say you will read ./ or any other news, because that would imply you will waste time at work doing something you really should be doing at home. That would be too honest. A cup of coffee is a simple pleasure and doesn't interfere with your job.

      Personally I would give full points to an answer like:
      Coffee - Check for any pressing emergencies - Socialize a little with coworkers for any work related things you need to know

      An honest, thought-out and self-confident answers are the way to go. Questions are designed to throw you out of balance and see if you have these traits even in a surprising situation. A bit of humour one or two times in an interview is also good, it shows you are in control of the social situation. It is not so much *what* you say but *how* you say it.

      If the interviewer is a random executive and it is clear he/she doesn't do interviews very often, it is good to be a little less honest and to show your technical expertise every now and then.

    • by hey! (33014) on Monday July 09 2007, @06:03AM (#19798205) Homepage Journal
      Coffee, then informal chat with each person who reports to me directly about what's up. In that order (important).

      Job of a manager is to lead; you can't lead unless you (a) know what's on the mind of the people you are leading and (b) remind them the direction everybody's supposed to be heading in. I always say that a manager has two functions: setting direction and removing obstacles. You should spend less than 5% of your time setting direction and more than 95% of your time removing obstacles. Simple reason will show that that's how you ensure your department is spending the most time being productive.

      So, you spend most of your time as a manager doing various kinds of communication. Informal communication is the best, because the most information is offered and retained; formal communications are for when you absolutely must have something on the agenda. You need both, but formal communication (meetings, memos/emails) should be infrequent and informal communication (shooting the shit) should be frequent.

      I'm a solitary consultant these days, but I really miss working on a team.
  • Otherwise I get a headache real fast!
  • Shower (Score:5, Funny)

    by Aliencow (653119) on Sunday July 08 2007, @05:00PM (#19792817) Homepage Journal
    I'm sure that would've been the right answer.
  • Check the sev 1s (Score:5, Informative)

    by MosesJones (55544) on Sunday July 08 2007, @05:00PM (#19792821) Homepage
    The first thing you do every morning is check the sev 1 problems that have occurred when you are out. Next off you look at the 24 hour report to see what is out of whack. Anything odd you follow up on. If everything is fine then you have a cup of strong coffee and wait for the first dumb question of the day.

    Deal with the disasters first, after that everything in the day is a lightweight bonus.
    • by Em Ellel (523581) on Sunday July 08 2007, @05:20PM (#19793049)

      The first thing you do every morning is check the sev 1 problems that have occurred when you are out. Next off you look at the 24 hour report to see what is out of whack. Anything odd you follow up on. If everything is fine then you have a cup of strong coffee and wait for the first dumb question of the day.

      Deal with the disasters first, after that everything in the day is a lightweight bonus.
      Generally speaking if you have to check on them, they are not sev 1. If they are sev 1 you should have been contacted by now via automated(monitoring software) or manual(minions) means.

      Of course what is missed in this discussion is that the job is that of an IT manager and NOT SA and as such it is NOT your job to deal with the actual monitoring and fixing of anything (except, as mentioned above, maybe things of highest priority), it is SA's job. Your job to is to support SA's and make sure the emergencies ARE dealt with while also making sure all (including non-emergency) services are taken care of.

      This is why sometimes a good SA does not make a good IT manager.

      -Em

      • by edittard (805475) on Sunday July 08 2007, @05:40PM (#19793217)

        Generally speaking if you have to check on them, they are not sev 1. If they are sev 1 you should have been contacted by now via automated(monitoring software)
        Perhaps they're a C shop - so they count from zero.
        • by CaptainZapp (182233) * on Monday July 09 2007, @01:47AM (#19796803) Homepage

          I feel sorry for you publicly traded entities in that regard - the Government really SOX it to ya, lol

          Dude, I actually like SOX. It means that, as a database developer, I am not allowed to touch the production databases.

          This in turn means that I am not allowed to do production support.

          This again means that I'm not liklely to receive phone calls at 3am, which I like just fine.

  • If it's early in the iteration (we have two week cycles for our agile development plan) then I'll log on to XPlanner [xplanner.org] which is a Free Open Source project management tool that allows me to control the user stories and tasks for our project. Early on I look for people that have more hours than others and I try to mitigate that by visiting them and just talking over what they have to do on a high level with them. Since I'm still young and know all the technologies we use, I give them drawings and any sort of information they need to get the job done.

    If it's near the end of an iteration or someone is empty, I shuffle tasks and then make a note to talk to both the people one on one when they get in. I also take the time in the morning to talk to people about what they need to work on so they don't spend all day on the wrong task. In the event of something pending that isn't going to get done, I schedule a meeting with my manager and maybe the customer. Haven't had to do that yet though.

    Now, keep in mind this is only for a 10 person development team so it might not work on your level. But the first thing I do is assess the day by going over what people checked in and completed the day before in my project management tool, XPlanner. If you haven't used it, I heavily suggest and endorse it--you just need a server to host it on and you're ready. Oh and I'm 25 with little or no management experience prior to this so that could also make this advice completely worthless and naive.

    In my opinion, the best thing a team lead can do is listen and, well before it happens, stop people from putting themselves in bad positions where they're in until 3 AM one night before a customer meeting. You take precautions at the beginning of every day and your team should be alright.
    • by sunwukong (412560) on Sunday July 08 2007, @05:36PM (#19793183)

      Early on I look for people that have more hours than others and I try to mitigate that by visiting them and just talking over what they have to do on a high level with them.
      09:30-1:15 -- mgr walked in to discuss strategic planning and proper time management; gave me a dirty napkin & some URLs; called wife to let her know i'll be late tonight
  • by alexfeig (1030762) on Sunday July 08 2007, @05:00PM (#19792829)
    1) Shmooze around the office cooler for gossip. 2) Make sure my job is still there, and not outsourced. 3) Read Slashdot. 4) Call vendors and complain about service... so I can get free service. 5) Cut my budget even more. 6) Come unglued on a random user. 7) Read Slashdot. 8) Go home.
  • by Anonymous Coward on Sunday July 08 2007, @05:07PM (#19792925)
    Masturbate. It's important you let them know you do this before you get to work. Sticky keys are nobody's friend.
  • Simple (Score:5, Insightful)

    by MyLongNickName (822545) on Sunday July 08 2007, @05:09PM (#19792939) Journal
    You answer it like so:

    "Every evening before going home, I write down my objectives for the following day. This helps me to stay focused the following day on what needs done. Sure, sometimes there are fires to put out, and not everything gets done. But by having a written down list, I find I am more productive. What I do first in the morning depends on what needs to get done that day"/
  • by ushering05401 (1086795) on Sunday July 08 2007, @05:09PM (#19792943)
    After I put the kettle on is scan the news sites. It takes me all of two minutes to identify any news item that might somehow impact me and my little slice of the IT world.

    I do this not so much for security or first-alert type response but for a more simple reason... I start conversations using the info I gleaned from the news. The people I work with each have different areas of technical interest, specialties, etc... managing a team means more than riding people about deadlines. I always start the day with a little chatter, and feel good when one of my team members gets to share some of their 'personal interest' knowledge because of a conversation I started.

    Starting conversations in this manner provides all sorts of little 'contact points' that provide info about your employee's mood, attitude, satisfaction, etc... and way too many managers I have known fail horribly at replicating these contact points through more formal methods.

    Anyhow, after that it is review e-mail, prioritize the day, and only begin coordinating with others once they have had time to do the same.

    Regards.

      • by ushering05401 (1086795) on Sunday July 08 2007, @06:02PM (#19793405)
        Actually it works the other way around. Once you know enough about your employees as humans you have a very hard time dealing with things like layoffs/reorganizations. I left my last position even though my place in the company was assured because of the way my department in general was treated.

        Try it sometime. Pick someone in the office you can't stand and spend one month learning a bit about them on a regular basis. If they are the type that prattles on and on be very straightforward in letting them know when they are annoying you without insulting them. After one month of this your understanding of who they are will have changed, and their understanding of how to interact with you will have changed... usually for the better.

        BTW, it is a manager's duty to retain some level of professional distance from their employees. That distance can either turn the workplace into a coldly efficient production environment, or can become a minimized by a manager who really does care bout his employees even though he may one day have to fire them.

        Regards.
  • by digitalamish (449285) on Sunday July 08 2007, @05:14PM (#19792989)
    The first thing I do is come up with an action plan to provide a best of breed solution that will benefit both our customers and our stockholders. After I take a wag at my daily task list, I begin working on new strategies to augment and improve the current paradigm. Once I have liaised with my support staff to determine the readiness of our infrastructure, I take off my jacket and put my briefcase away. Sir.
  • The obvious (Score:5, Funny)

    by Mike1024 (184871) on Sunday July 08 2007, @05:16PM (#19792999)
    1. Park my bike, shower etc.
    2. Turn on computer.
    3. While it starts, get a coffee.
    4. Log in, drink coffee, check e-mail/calendar.
    5. Get to work.

    I've got to say, that sounds like the sort of interview question that would get some pretty boring responses. Like mine, above. So I usually jazz it up a bit in interview:

    1. Park my unicycle, change out of my superhero unitard.
    2. Get a new guitar from the IT guys because I smashed mine at the end of my last performance.
    3. Check in with each of the 10,000 people who work under my command, all of whom I know by name.
    4. Have my executive assistant relay my e-mails to me, one character at a time, by throwing lettered frisbees back and forth between my company's two tower blocks.
    5. Take my second breath of the day.

    So far I haven't had any job offers, but I figure the market is pretty competitive at the moment - it's only a matter of time!
  • TPS Reports (Score:4, Funny)

    by Joe The Dragon (967727) on Sunday July 08 2007, @05:21PM (#19793053)
    while reading the e-mail and memos from my 7 bosses
  • by blhack (921171) on Sunday July 08 2007, @05:21PM (#19793055)
    When i come in, i immediately remove the backup tapes from last night and replace them with the ones for the night to follow. After that i sit down at my workstation and check the server logs to make sure that the backup completed successfully. Next comes email. There are a few automated emails that get sent to me when cron jobs are completed detailing what was done and how efficiently. If there aren't any problems that need to be dealt with, I start scheduling out my day in my notebook. After that i usually make my rounds around the office checking back in with users who had problems that required attention yesterday, to make sure that the solution worked for them and that everything is running smoothly. Once that is done, i log into the servers to check their state, make sure there aren't any runaway tasks, and basically ensure that everything is running smoothly. If there still haven't been any users with problems that need attention at this point, i will usually start looking through the firewall logs from last night to make sure nothing fishy was going on while i was away.

    At this point, printers usually start exploding.
  • by CrazyJim1 (809850) on Sunday July 08 2007, @05:30PM (#19793119) Journal
    Peter Gibbons: Well, I generally come in at least fifteen minutes late, ah, I use the side door - that way Lumbergh can't see me, heh - after that I sorta space out for an hour.
    Bob Porter: Da-uh? Space out?
    Peter Gibbons: Yeah, I just stare at my desk, but it looks like I'm working. I do that for probably another hour after lunch too, I'd say in a given week I probably only do about fifteen minutes of real, actual, work.

    He got promoted to manager off this.
  • But the first thing I need is to get my first hit of the day

    Some Coffee, a cigarette followed by a few tabs of dexedrine and Effexor.

    Honest to god, i couldn't give a fuck less about anything untill I have satisfied my cravings.

    So what If i'm addicted.
  • by spirit_fingers (777604) on Sunday July 08 2007, @05:33PM (#19793145)
    So the first thing I do in the morning is play Unreal Tournament deathmatch online with the Maytag Repairmen. They suck. Naturally, I pwn their asses. After that, it's time for my mid-morning nap. Then it's off to lunch! Two hours later, I'm back, and it's siesta time, followed by a bathroom break where I peruse the the NY Times. Then, back at my desk, I jiggle the hula doll on top of my Mac Pro and check my email. Yawn. Nothing happening there. Then around 3:00 pm, my supervisor usually calls and asks me to show him for the 300th time how to import his Van Morrison CDs into iTunes. By then it's happy hour in the employee lounge. A couple of brewskies, followed by a fevered round of pinball, and it quittin' time! Yay! I've earned my pay for the day.
  • Walk in the door, counter sarky comment from reception with "Yo mama" jibe. Walk past HR bitch, try not to catch eyes in case she steals my soul whilst i'm not looking. Pass 2-3 people having a conversation about shit not working, try to ignore it, if that proves impossible say "It's probably normal" or "Fucking goldmine/microsoft/Vendor-X" and walk off looking like your about to go fix something. Walk past engineers, stop to have a look at the latest batch of pornography they are trying to pass off as work related e-mail. Make it to the desk, throw down keys locate cup and head for a cup of tea. Return to desk and kill time until eyes finish opening and last nights hangover subsides. Each week is a relentless collage of grey interspersed with trips to the lav.
  • Don't lie. (Score:5, Insightful)

    by pla (258480) on Sunday July 08 2007, @06:02PM (#19793411) Journal
    What is the first thing you do when you get to work in the morning?' I thought saying 'Read Slashdot' wouldn't be what he was looking for -- so I made up something, I'm sure, equally lame

    Perhaps he just wanted to see if you'd lie to tell him what he wanted to hear.

    That question has only one "right" answer - You get coffee, check Slashdot and read your email (possibly not in that exact order), then you glaze over until you hit the bottom of at least your first cup of coffee. Any interruptions before then, you respond to with "Mmmmmpph? Grrrrrrumph. Mrphythuber kurbendurby! Mrffff". Anyone failing to understand that response clearly doesn't work in IT, or worse, likes mornings (grounds for immediate dismissal, IMO).


    And anyone that mods this "funny" either lies or doesn't work in IT.
  • by rjbrown99 (144423) on Sunday July 08 2007, @06:25PM (#19793581) Homepage
    There may be more than one answer, but this one would definitely go a long way in an interview.

    The first thing I would do after arriving at the office is greet any members of the team who were already in the office. It goes a long way when a boss spends the time to interact with the team and employees always appreciate little things like that. It's not a flashy answer, but it demonstrates that you want to emphasize communication and teamwork.
  • by pem (1013437) on Sunday July 08 2007, @06:51PM (#19793775)
    Try to take over the world!
  • My morning routine (Score:4, Informative)

    by Murrdox (601048) on Sunday July 08 2007, @07:05PM (#19793895)
    I'm an IT Manager.

    1) First on the list is to go over any emails or voicemails that came in that need my attention. Hopefully there are no emergencies for me to take care of.

    2) Go make myself some coffee. Just say "no" to bad office coffee people. We have our own coffee maker in our IT area. I drink most of it.

    3) Swing by and say "Hello" to all my people, say good morning, see how everyone is doing, see if anything major is going on that I haven't been emailed about.

    4) Get my coffee and relax for a few minutes reading slashdot or wired.com before delving into the day's projects.

    5) Meetings!

  • ok seriously (Score:5, Informative)

    by cecil_turtle (820519) on Sunday July 08 2007, @07:10PM (#19793923)
    I've read most of the posts above, and below is my answer. I don't drink coffee and if I eat breakfast that day I do it before work. I don't read Slashdot / etc. while at work, I do that on my own time after I get home. Also the full question was "What is the first thing you do when you get to work in the morning?" (emphasis mine) - so there goes the answers like "shower". We'll also assume that this is a normal work day and an automated monitoring system hasn't paged me with a problem causing me to drive in early and fix it. We'll also assume I didn't just get back from a vacation.

    OK, now with all the qualifiers out of the way, here's what I do first thing:
    • Check voice mail. I will only normally have 1 or 2 at the most unless I've had days off, and I also get voice mails via email so it's likely I already heard it.
    • Skim emails. Again I keep tabs on email even when not working so there's not normally a ton of new stuff, but I like to look over all of the emails, delete spam, and read important things first or things I've been waiting to hear back on. This is not when I deal with less important emails or write lengthy emails to people.
    • Check monitors / logs. For me this means disk space monitors, MRTG bandwidth reports, backup statuses, etc.
    • Check my short-term to-do list, normally created the day or two before that gets updated a couple times per week. Start on a project or delegate a project to a co-worker.
    • If I'm in a waiting stage on all of my short term projects (waiting for parts to ship or waiting on a vendor or waiting to hear back from upper management) then I will make an effort to follow up on those items to help move it along (check tracking numbers, send "reminder" emails, etc.).
    • If all of the above is taken care of, move on to the long-term project list.
    My last comment is that some people have very specific ideas of what an "IT Manager" does or should do. Keep in mind that's a very broad term that will vary from organization to organization, mostly depending on the size. Somebody above made a distinction between an IT Manager and a System Administrator, but when your whole team is two people (like mine) those things don't make much difference. Maybe in some organizations IT managers don't get paged, or don't deal with backups, or whatever, but in smaller organizations the manager is also a staff member.
  • by slickwillie (34689) on Sunday July 08 2007, @07:17PM (#19793997)
    to look for a better job.
  • by nick_davison (217681) on Sunday July 08 2007, @07:50PM (#19794221)
    The number one thing I do: Say good morning to the receptionist.

    A good relationship with her (it could be a him, it's simply a her where I work) is essential:

    Just about everyone bitches to her. Whether an issue's with email, with network reliability, a printer not working, phones playing up, the cold tap running hot, she's aware of all of it.

    She's also the one point everyone has to pass at least once and, being close to both restrooms and breakroom, she tends to see most people much more too. Better than anyone, she can serve as a barometer of people's moods. If someone is obviously in a foul mood that morning, if someone's running around stressed about something, she knows faster than just about anyone.

    She's also the person everyone has to let know if a client's coming in as she'll be the person to meet them. She also tends to handle much of the mess that is meeting room booking so she gets even more insight in to who's coming.

    Build a good relationship with her and she looks out for me. If everything's cool, I get a "Hi" back and get on with greeting my team, checking email, checking in with project leads and PMs, reading slashdot, etc. If there's something up, she'll give me a summary that, with her understanding my needs from our previous talks, pretty much prioritizes as I need to know. I can then get on any problems far faster than checking each of the traditional reporting methods or I can go about my normal routine prepped so I don't say send an email that might trigger the guy who's in a bad mood that day.

    And that's just the first fifteen seconds of my day.

    She's also the first person to interview any candidates for me: If someone's an asshole to the people they think "don't matter," they're going to disrupt my team in a million other ways.

    As already mentioned, she handles the mess of meeting rooms - an often precious resource. Do you want that person favoring you or someone else?

    Being the first person everyone bitches to, she can come back with, "Wow, Nick [or Nick's team] is really being a jerk. Let's see what we can do." or she can respond, "Wow, that doesn't sound like Nick [or Nick's team]. He'd never knowingly let that happen. Let's let him know and I'm sure he'll get it addressed right away." Her response, being many people's first reaction when something goes wrong, can totally color the rest of their reaction and how easily I can deal with the issue.

    She also knows where everything is, how everything functions, or who would do. "Hey, I can't find the contractor NDA forms." can get you a sympathetic acknowledgment from a rushed person and hold up your rush filling of a position by a day or two while you track them down or it can get "Hmm, I'll track them down and IM you in about five once I've got them." from someone who likes you.

    The same holds true for all interpersonnel relationships, it's just especially important with a front desk person given everything that crosses their world - plus the question was what do you do "first" and they are pretty much always the first person you'll see.

    Most nerds give great answers about slashdot, about email, about remote logging and paging systems. They're great nerd answers that show why you'd be great for a nerd position. What they demonstrate a lack of is an appreciation of what good interpersonnel relationships give you and adding that on top of the nerd qualifications is what demonstrates you'll be a good manager. Management is no longer a role about who can do the coolest nerd thing, it's about how do you handle all of the relationships around a diverse bunch of people. If your answer is about the systems, not the people, you're most comfortable interacting with - you're probably giving a major red flag for your abilities to work with people who should work with systems for you.

    There were quite a few joke comments about "schmoozing." While I know they were intended as fun, that it's seen as something silly that managers that n
      • by nick_davison (217681) on Sunday July 08 2007, @08:47PM (#19794613)
        None taken.

        Different people like different things. That goes for the employees and the employers. It's why Google does things one way, Fog Creek does things another and why some of us will quit jobs in disgust and never understand why our friends, who we thought were smart, will happily remain there for years.

        I'm lucky, I've got a situation where my management have given me a free rein to do what I think is best, a team that appears to appreciate the environment I create and that's been able to pay off in terms of a sustained, significant increase in profitability (any idiot can increase profitability in the short term at long term expense), a huge increase in reputation for my team members within the company, with clients and even on standards bodies, etc. and, off the back of that demonstrable increase in profitability, the ability for me to argue for, and get, a large number of significant pay raises for every single long term team member in an industry where large raises tend to only be achievable by job hopping.

        Sure, my style's not for everyone. One contractor we used sent me racist hate mail after we let him go for yelling at the receptionist, bitching that a server admin took too long to set up an account and then leaving after three hours because parking cost $8 for the day. In his case, my beliefs that we're the sum of our reputation, including how we treat others as well as how we perform technically, were so objectionable he needed to resort to vitriol. That's cool, I hope he'll be happy somewhere where you're allowed to attack people for improper care and handling of the self important. The great thing about the world is he gets to find a manager that suits him, reaping the rewards of that, while my team members get to find a manager that suits them, reaping their own rewards.

        I'm not in any way denegrating nerds. I'm one first, learning the other aspects on top of that. Technical knowledge remains essential for a technical role and I was careful to state that I don't have respect for the technically illiterate, morally vacuous schmoozers out there. Where I've personally found works well for me, and works well for most employers, is the realization that a combination of strong technical skills with an understanding there's a human level too (where interaction with integrity rather than fake schmoozing is the emphasis) seems to generally make for a good manager.

        I'm not perfect. I make all kinds of mistakes. But that's at least the philosophy I've formed, what I've observed many more senior managers seem to look to hire and, aiming for, has at least brought me a fair degree of success measured both in terms of how my team performs over the long term and how well I feel I've been able to do, looking out for the guys who do work for me.

        Of course, those're just my observations and the direction I try to head in. That doesn't appeal to you? That's cool, it's a huge industry. Interviews should be as much about you interviewing your potential new management as about them interviewing you. You get to find somewhere that works for you, I get to build somewhere that appears to work pretty well for me, and we all come out of it pretty well.
      • Re:Brilliant. (Score:5, Interesting)

        by nick_davison (217681) on Sunday July 08 2007, @11:31PM (#19795903)

        Of course, I've always done it...I liked her and valued her. But never even given a second thought to her power. And you're absolutely right.
        It's the one useful thing I learned at university...

        No lecturer actually collected their assignments at the 5pm cut off. Very few would even see it as a priority before noon the next day. They simply relied upon the department receptionist to tell them who handed it in on time and who gets the instant 20% knocked off for being late.

        Befriend the receptionist and you got an extra night on every assignment. For the really big stuff, if she liked you enough, you'd tell her your woes and find she'd offer to tell the lecturer, "I'm SO sorry, Nick handed this to me before the deadline last week but I guess I put it down on the wrong pile." You then got to listen to the lecturer talk about what he had been looking for, after he assumed no one else could submit work, and leave everyone else wondering how you so effortlessly got straight As.

        Sure, technically, each lecturer held more power. But every one of them always had students sucking up to them, trying to gradegrub, and was pretty much immune. And you had ten or twenty different lecturers you had to try it with.

        Alternatively, one receptionist extended every deadline for you and knew the lecturers well enough to tell you great tidbits like, "Lecturer X admits in the staff breakroom that he likes a glass or two of whisky while he grades. He starts off grading pretty strict but jokes about how his criteria's much more 'relaxed' by the end of the night. I'll slip your assignment in where it'll get the most generous grader. Lecturer Y hates grading and gets more angry as the night goes on, so I'll put your assignment at the top of her stack."

        Amazing how much power the people who allegedly don't have any power really wield.

        Mind you, social engineering is also the reason why some hackers will spend days trying to crack security vulnerabilities in software while another guy will achieve just as much in a single phonecall.
    • by flyingfsck (986395) on Sunday July 08 2007, @05:12PM (#19792969)
      Why do you need to boot your computer? Are you running Windows ME?
    • by PCM2 (4486) on Sunday July 08 2007, @05:13PM (#19792981) Homepage
      In other words, your boss could save the company about fifty bucks a day in lost productivity if he made sure you didn't turn off your computer when you went home at night.
            • Still makes no sense. No modern operating system should require you to cold-boot a computer, even less a laptop at any time. I only reboot my iBook for updates, once in a while.

              We all would like to believe in this day and age that OS's and applications do not leak memory or become unstable but the fact is that they do.
              Applications do. That's what restarting your applications once in a while is a good idea, and that's what a relog is useful for, but once a day is quite overkill on a laptop. And if you operating system is really leaking ram usage, I'll wonder like that other guy if you're running Win ME.
        • by daeg (828071) on Sunday July 08 2007, @06:45PM (#19793743)
          We still tell our employees to shut down. But we also have the machines set to automatically start up at 7:30 AM (an option in most newer BIOSes). Updates are applied at 7:40 AM, rebooting in time for any 8:00 AM early birds (office opens at 8:30).

          Why shut down vs. other power saving options? I don't like dealing with the power save options in XP. Most of them suck and aren't worth the trouble. And people still shut down even if we ask them not to.

          When we finally upgrade to a suitable operating system that can handle true hibernation, I'll change the policy.
    • by pyite (140350) on Sunday July 08 2007, @05:59PM (#19793385)
      as an IT manager, one should have put in place automated monitoring and backup processes ... Then, the first thing one does on arrival is to check the results of the automated monitoring.

      Newsflash: If you're checking the results of monitoring software, you're not a manager, you're an SA or an operator. I'm not even a manager and yet I've not even seen my company's monitoring tools. If something is wrong, someone who's watching that stuff will tell me.

      • Re:First (Score:5, Interesting)

        by Jaruzel (804522) on Monday July 09 2007, @04:57AM (#19797899) Homepage
        1. I arrive at my desk
        2. I open the lid on my coffee
        3. I start to drink my coffee
        4. I glare at my minions until...
        5. ...One of them gives me an update.

        Delegation. Get others to put out your fires for you. THEN claim the credit.

        -Jar.