Tag: career

  • The Top Ten Skills You Need

    One of the things I’ve found is that so many people struggle to get started with SQL Server. There are regular questions about how to learn to work with SQL Server, so I built this quick talk that should help you get started.

    This talk is built on the 80/20 rule, the idea that 80% of your job needs 20% of the DBA skills, and vice versa. So these are a series of skills, presented quickly, that should get you through most of the things that you need to deal with in SQL Server as an administrator.

    Developers will find that spending a little time learning these skills will also let them easily setup a SQL Server instance that can maintain itself for the most part without them. And it will protect them in the event there are issues.

    The talk moves quickly, but there are lots of links and references in the deck.

    Slides

    The slides are on my SkyDrive.

    Length

    This talk is built for 60-75 minutes

    Related Blogs

    These are the blog posts related to this talk:

  • Sabbaticals

    This editorial was originally published on Oct 25, 2005.

    Does your company offer a sabbatical? Andy and I were discussing retention and benefits awhile back and we got around to sabbaticals. He was trying to secure this benefit for his development staff, and I’d had a little experience, so we got to talking. I’ve never personally had one, but my wife has. She worked for a high tech company in the 90s and after 6 years, she was allowed to take 6 weeks, full salary, as a sabbatical.

    I’ve never personally worked at a company where it was offered, much less stuck around long enough to earn one. But I’ve always thought they were a great idea, without really understanding the purpose. It seemed like a great reward to let someone get a little extra time off after devoting six or seven years to the company, which seemed to be the norm with my friends.

    However I started to research this a little and found that the idea wasn’t extra vacation. It was to allow someone to recharge, but in a constructive way. In academia, this usually means working on some defined project, a paper, book, or something else that has a tangible and specific end to it.

    That is an interesting idea. When my wife took her sabbatical, she basically took 8 weeks of vacation; the sabbatical and some other PTO time she’d shared. For her it was a project, to try and be a stay at home Mom, but it wasn’t something defined with her employer. I’ve spoken to a few other people that were lucky enough to get them and it was really a vacation time for them, a chance to get away.

    I think that setting up a sabbatical is hard. You don’t want to just pile up work for someone that takes off for 6 weeks, especially if there’s a chance they will not return. And if they return to something like that, it’s more of a punishment than a reward. Allowing someone to leave for an extended period, and I’d argue that 6 weeks isn’t that long, but it is hard on a company and the other employees. But I think it’s almost a necessity given the long hours and extra efforts that many IT people put in.

    The idea of setting up a specific project, even something like attending a cooking school or training for a marathon, is a good one. There should be some flexible rules that bound the time, but still make it productive for the employer. Xerox has a great volunteer sabbatical where employees can spend a number of weeks volunteering with some organization, and I think that is outstanding.

    I think I’d enjoy 6 weeks of pounding nails with someone like Habitat for Humanity.

  • A Little Interviewing Advice

    Make your next interview a two way interview.

    I know there was a great uproar over the interview piece at the beginning of this week and I received lots of opinions on various parts of the article, good and bad to go over. But one comment came yesterday that was very interesting to me. Paraphrasing because I cannot seem to find the email in the deluge that is my desktop, it was questions the line “And you want them to think you’re one of them”

    I read that a few times before I received the comment, not thinking much of it. After all, when you are interviewing, you want to get along with people and have them like you and hopefully hire you. When I got this comment, however, it struck me what the advice was and what I read were two different things.

    You see I think teamwork is very important, much more important than the technical skills. Not that skills aren’t important, they’re just behind you fitting into a team environment. So where’s the problem with that line? You see it?

    “think”

    When I interview you, or when I interview a company, I am searching and trying to find out if I AM one of them. I want to fit in, but it has to be something that happens naturally. I try to present an honest face and I try to relax candidates to get an honest sense of how they really are. I want to know if they really fit in, or if I do. Not if I can act the part and fool someone into thinking that I’m some other candidate.

    I know it’s hard. You apply for a job, maybe need one, and you want desperately to get hired. And you want to make the impression needed to get hired. And if you are really desperate, then perhaps there’s some justification. But most of the time that’s not the case. I see many DBAs and developers wanting a new job, more money, etc. and they are interviewing while they already have a job somewhere else. There’s nothing wrong with that, but if you are looking to move, do it the right way.

    Be honest and give an honest impression of yourself. And at the same time interview the company and try to ensure they are giving you an honest impression of what it will be like working there.

    After all, companies lie in interviews almost as much as candidates.

  • Why I’m raising my son to be a nerd

    A good read, from ESPN and CNN columnist, LZ Granderson: Why I’m raising my son to be a nerd.

    We need more STEM (science, technology, engineering, and mathematics) education in this country, and probably in all countries.