Last week I presented for the PASS Virtual Chapter on Professional Development about Communication Skills and the whole thing was recorded via LiveMeeting. It's 70 minutes of distilled experience with some stories thrown in.

Check it out at https://www323.livemeeting.com/cc/usergroups/view?id=7KH9ZW.

Enjoy!

PS Many thanks to Mark Caldwell for hosting the meeting!

Categories:
Career | Consulting

Every so often I do non-SQL blog posts about things and one of the topics that comes up again and again is communication skills.

The PASS Professional Development Virtual Chapter invited me to present a lecture for them and so at 10am Pacific Time on Thursday, December 15th I'll be presenting on communication skills. I'll touch on written, spoken, blog, presenting and other forms of communication and tell some stories too.

It should be a good lecture - for once with very little technical information!

The LiveMeeting link is https://www.livemeeting.com/cc/usergroups/join?id=7KH9ZW&role=attend

Hope to (virtually) see you there!

Categories:
Career

Jonathan Kehayias is such a nice guy. After our recent perf tuning Immersion Event in Chicago last month he had an idea for each of us to pick someone who's attended a SQLskills class and offer general mentoring (career, technical, professional development - whatever) to them for a few hours a month for six months. After six months we each pick someone else. His thinking was that this would be a cool way for SQLskills to give back to the community outside of the purely company-related things we do like blogging and twitter.

I think this is a really great idea. Back when I was at Microsoft I did a lot of mentoring when I managed teams there, plus in the company-wide mentoring program between senior and junior people in different groups. It's very rewarding to provide completely altruistic advice to someone and watch them grow.

Furthermore, we all have had people help us with our careers so it's important to pay that help forward.

So we're doing it, starting today with me, Joe, and Jonathan.

Joe is going to mentor Luke Jian, who's attended our IE1 and IE2 classes in Chicago this year:

Luke Jian is a well-versed IT professional with over 15 years of experience in the development and implementation of pharmaceutical and healthcare systems, demand driven supply chain management, ERP systems and technical infrastructure design.

Luke's current role is Sr. Solutions Architect with Physicians Interactive a leading resource for healthcare information, medication samples and medical decision support tools. Luke's experience include managing the IT Operations of over 50 clinics,  Oracle DBA for a supply chain software company, Teaching Assistant and Trainer.

Luke holds a Masters degree in software engineering from “Politehnica” University  of Timisoara, Romania with concentration on relational databases and  is fluent in English, Romanian, French and German. He became a US citizen in June 2011, the same week as his first public speaking engagement at SQL Saturday #82 in Indianapolis.

Luke writes at http://blog.sqlpositive.com  and he can be reached at sensware@gmail.com or on Twitter as @sensware.

Jonathan is going to mentor Steven Ormrod, who's attended our IE1, IE2, IE3, and IE4 classes in Dallas, Chicago, and Bellevue this year:

Steven Ormrod has been working as a Database Administrator for an international purveyor of natural and organic foods for the past several years.  Recently, Steven accepted a position with a global provider of orthotics and prosthetics.  His environment contains hundreds of servers spread across three different countries.  Clustering and consolidation projects have been his primary focus.

He has an MCITP for SQL Server 2008 in Database Administration and Development.

Prior to working as a DBA he has been a software developer, system administrator, and a teacher.  He also spent a summer bartending and hitchhiking across Europe.

When he is not tinkering with technology, he enjoys cooking, traveling, and snorkeling. He blogs at http://sqlavenger.wordpress.com/ and is on Twitter as @sqlavenger.

I'm going to mentor Brad Hoff, who's attended our IE1 and IE2 classes in Chicago this year:

Brad is originally from WA and is working in TX as a Lead SQL and Oracle DBA for an international power development company and energy marketer.

Brad has a degree is in Electronic Engineering and his background includes Development, Network/Systems/SAN admin, and WAN/T-Comm.

When Brad's not working with SQL server, he enjoys philosophy, debate, brain-teasers, learning, anything that challenges his mind. He has a beautiful wife and an awesome 17-month-old son. He blogs at http://www.sqlphilosopher.com/wp/ and is on Twitter as @sqlphilosopher.

I'd like to congratulate these three guys and look forward to us helping them out over the next six months!

Categories:
Career | General

There are several reasons why I've drastically cut back on the amount of time I spend in the various online SQL Server forums, including:

  1. People continuing to argue that the advice given to them is wrong (and I mean arguing even after me giving references suppporting the advice and explaining why my advice is correct)
  2. People asking questions that they could have found the answer to in Books Online or by Googling (yes, I prefer Google to Bing) a few keywords

#2 is mostly sheer laziness IMHO.

When Kimberly was on the SQL team at Microsoft many moons ago, she was famous for replying on a 2000-person internal alias (paraphrasing) "If it takes you more time to type this email and send it to the alias than it would to look up the answer in Books Online, you're wasting 2000 people's time". She got 17 responses, 15 of which commended her. She has of course mellowed a little in her old age :-)

When one of my daughters comes to me saying they don't understand how to do a math problem, I always ask them if they have read the instructions at the top of the page in their math workbook. Usually the answer is no, in which case I refuse to help until they've read the instructions, tried the problem again, and can explain what they think they're supposed to do with the problem. The real world doesn't have a friendly Dad there all the time to explain how to solve a problem.

There are good reasons why products come with manuals, including:

  • So that a company's product support is not inundated with simple questions, saving the company money
  • So that people can easily figure out how to use the product's functions without bashing their head against a wall in frustration
  • So that a company doesn't get sued by failed Darwin Award candidates
    • E.g. "Do not operate the TreeMasher X3000 chainsaw with the diamond-tipped CutThroughAnything (TM) blade while drunk"
    • E.g. "Do not attempt to unclog your new in-sink Eviscerator (TM) waste disposal unit using your hands while it is running"
    • E.g. "Consuming excessive Jägermeister in Seattle will result in uncontrolled karaoke singing"

However, sometimes reading the manual does no good whatsoever. For example, on our recent European trip, we rented a BMW in Frankfurt for a couple of weeks of touring around. For the life of me I couldn't figure out how to start the damn car. I tried looking in the manual, but it was in German, which neither of us understands. Eventually (after 15mins of increasing frustration) I figured out you have to press the start button while pressing the brake pedal. But that was my fault, not BMW's - the manual did say how to do it, but I just couldn't understand the manual.

Most of the time though, you can get a good idea of what you're supposed to do by reading the manual. We're currently writing the Denali JumpStart training material for Microsoft (like we've done since 2005 - see here for a description of the 2008 work). When we got hold of CTP-3 in early July we didn't install the VMs we'd been given and then start randomly playing with stuff. We read BOL for the features we're covering, and then started playing around. Why? So we didn't waste time.

Books Online is pretty comprehensive in terms of syntax and in the last year or two their guidance and background explanations have improved and expanded immensely - kudos to the BOL team! So at least have a look in there first.

There's a good reason why the website Let Me Google That For You exists - because people get annoyed when others ask questions for which the answer can easily be found. The LMGTFY tag line is "For all those people who find it more convenient to bother you with their question rather than google it for themselves."

Don't get me wrong, I really like helping people out on twitter, forums, and over email (to a point) - but I get really terse really quickly if someone sends me a question for which the answer is in BOL or shows up near the top of a simple Google search (e.g. a recent email I got was "where can I get a description of the what the input parameters to sys.dm_db_index_physical_stats are?"). You'll know if you've offended if my reply just contains a URL.

Bottom line: Don't waste everyone's time, including your own. Read The F-ing Manual. Search online. Do some due diligence. And then feel free to ask all the questions you want - we'd all love to help you. But only after you've invested a little time trying to help yourself first.

Categories:
Career | General

This is almost our catch phrase. In every class we teach Kimberly and I always say that the answer to every question about SQL Server *starts* with "It depends" - except one: "should auto-shrink be enabled?" :-)

Seriously though, there's a bit of an unnecessary backlash against the phrase "it depends" and I'd like to clarify why we think it's a totally valid way to start an answer.

I think the backlash stems from consultants and trainers using it as the answer to any question they don't know the answer to and then not expounding any further. That's a crappy way to answer a question as "it depends" on it's own doesn't really provide anything useful and I can totally understand people getting frustrated by that. I think that people would be much better answering "I don't know" rather than trying to cover up lack of knowledge by simply saying "it depends" - there's no shame in admitting you don't know something - nobody knows everything about SQL Server.

I find the denigration of the phrase annoying though, as nearly all the answers really do start with "it depends". I don't want this to turn into one of those marketing-ish 'hire-us' blog posts, but one of the reasons Kimberly and I are so well-known for saying "it depends" is because we spend so much time in our classes explaining *why* it depends, *what* it depends on, and *when* it depends. Occasionally I can even say *who* made it depend too :-) We even have "It depends" emblazoned on the back of our SQLskills instructor t-shirts.

Almost as bad as saying "it depends" without the follow-on explanation is saying the answer is *always* such-and-such. That can be really damaging as nothing is black-and-white (except not using auto-shrink! :-) but teaching that it is can lead to propagation of misleading information out into the community.

My challenge to you: next time you hear someone say "it depends", ask them to explain. You'll get a really good feeling for their depth of knowledge and honesty if they can explain to your satisfaction, as otherwise "it depends" is really saying "I don't know".

And don't be scared to say "I don't know" - you'll get way more respect than trying to BS an answer.

Categories:
Career | General

You're ignorant. About lots of things. Yes, you are.

Feel offended? We're all ignorant about lots and lots of things.

Last week I wrote a non-technical blog post The Golden Rule - maybe just optional now? about the growing lack of civility in the world at large. That elicited almost 40 responses (thanks!) so I'm going to intersperse more non-technical posts in with the technical ones - as I have a lot of views to express :-)

This one is about ignorance. In my opinion many people don't understand ignorance and take offense if you say they are ignorant about such and such. In fact being ignorant just means that you don't know something - it's not derogatory or a statement of blame.

And it definitely does not mean that someone is stupid. However, time and again I see ignorance equated with stupidity. This is very common to see on internet forums where question posters can be heavily railed on by more experienced people for not knowing X or Y about SQL Server. And do you think that's going to make them come back to ask more questions to learn about SQL Server? No.

[Edit: I'm not saying that people use the word 'ignorant' all the time, but the implication is there.]

An example: yesterday on a distribution list I'm on, someone asked what to tell a DBA who insists on rebooting SQL Server regularly. The first knee-jerk reply to the alias was unfortunately "You're fired!"

Wrong answer.

So often I see knee-jerk responses to problems and questions - and they're usually wrong - as in this case. Jumping to conclusions quickly can be damaging - something I used to do a long time ago when I first started my career and I was slowly trained out of it (thankfully).

The correct response to the original question would be to ask the DBA *why* the server is being rebooted and the rationale behind rebooting being the preferred fix for the problem. And then educate.

Here's something you may not have thought about: every single person in the world starts out with absolutely zero knowledge about SQL Server.

When I joined the SQL Server team on February 1st 1999, I knew zip about SQL Server. Now I know lots about many aspects of it, and still zip about many other aspects of it. The same goes for Kimberly. And Kalen. And Itzik. And many others that the community considers an expert in SQL Server. Nobody knows everything about everything, and everyone starts from scratch at some point in their careers.

Today there is a growing proliferation of involuntary DBAs who have to deal with the big, complex beast we know of as SQL Server. You can't expect people to know everything straight away. You can't expect people to necessarily know what they *should* know, that comes with experience. And even experienced DBAs who've learned that SQL Server does X sometimes don't know that the behavior changed and now it does Y instead. Sometimes people aren't given time to learn by their employers, and non-work commitments stop them spending hours of their own time learning.

So next time you see someone asking a question that you think is so simple that they should know the answer, or that *everyone* knows you shouldn't do X or Y, cut them some slack and educate them nicely. Empathize. Don't belittle them. Don't rail on them.

And don't equate ignorance with stupidity.

Categories:
Career | General

I think many people imagine that technical acumen and razor-sharp problem solving skills are the most important skills to be a successful consultant. I would strongly disagree. While these two skills are *absolutely* essential for success, I think they are less important than the ability to effectively communicate with your clients.

Effective communication is a skill that doesn't come naturally to most people - it has to be nurtured, practiced, and perfected. I could break down "communication" into a variety of sub-classes:

  • Presenting to a large audience
    • E.g. a conference session, or a large group of IT staff
  • Presenting to a small audience
    • E.g. a class, or a targeted set of IT staff
  • 1-<5 discussions with technologists (devs, DBAs, IT directors/managers)
  • 1-<5 discussions with executives (VPs, CXOs)
  • 1-1 discussions with technologists
  • 1-1 discussions with executives
  • Whitepapers
  • Design, analysis, or strategy reports
  • Status emails or general email conversation
  • Business solicitations

Each of these requires a different approach. Before any kind of client presentation, meeting, or phone call, or when crafting a report or email, I ask myself the following questions:

  • Who is my audience?
  • What am I trying to convey to them?
  • Is my message appropriate for the audience? (e.g. I wouldn't necessarily be discussing business implications of growth choices for the entire company's data tier with a developer, nor would I necessarily be discussing index tuning strategies for specific tables with a CIO.)
  • What politics and inter-personal/departmental relationships do I need to be aware of?
  • What would the ramifications be if my presentation/call/report/email was described or forwarded to another person/part of the company? (e.g. am I being asked to deliver some metrics/advice that would be unwelcome - but needed - in another department?)
  • Is my communication in the overall client's best interests?
  • Am I sure I have all the pertinent facts and details to be able to give my opinion credibly and correctly?
  • Am I 100% sure of the technical content of my communication?
  • Is my tone correct? (e.g. sometimes one needs to take the tone that 'you hired me because of my experience and knowledge, and in this case, respectfully, person X is incorrect' - but it needs to be done professionally.)

And of course everything needs to be concise, bullet-points instead of waffle-y paragraphs where needed, spel chcked, also grammer must be write actually two.

There's no excuse for incorrectness in written communications - many people have the opinion that sloppy communications indicates a predilection for sloppiness in other areas. I also subscribe to this view. Don't get me wrong - it's fine to have mistakes in tweets and the odd email - but consistent errors in emails, blogs and other professional communications doesn't look good. Seeing these things makes me cringe.

But so far I've only mentioned the consultant communicating with the client. The client's communication with the consultant is way more important. You have to be an 'active listener', where you're not just passively listening to the client but you're taking it in, processing it, making sure it makes sense, asking questions for clarification and so on. If you can't work out what you're being asked to do for the client then you're in trouble. It could be that the client isn't very good at explaining, in which case you need to restate what you think you've been asked to do so everyone's on the same page. Every few new clients we find we're following other consultants who didn't do what the client wanted because of communications issues, not necessarily technical deficiencies.

I am overwhelmingly pleased that I grew up into a manager and senior contributor in a fast-moving product group at Microsoft - there was no choice there but to communicate effectively (in all the various forms I listed in the first set of bullets above) - or be left behind - it was that simple. Trial-by-fire is a great way to learn.

If you don't have an opportunity like that, there are plenty of ways to practice - user groups, blogging, and whitepapers - and just making yourself be a better communicator wherever you work. And you might consider having a partner or colleague review certain key communications - Kimberly and I do that for each other all the time (like this blog post, for example).

Effective communication is an indispensable skill that I don't think enough emphasis is placed on in the tech community.

What do you think?

Categories:
Career | Consulting | General

 Dilbert.com

 (Used with permission from Dilbert.com)

Following on from the survey I did about what your company is doing for you and vice-versa (see Job security, loyalty, and employee retention: you need to take control), people asked for a salary survey - so I complied a couple of weeks ago (see here for the survey).

The results show a very wide range in salaries for all ranges of experience. Bear in mind that salaries will vary not just because of experience, but also because of responsibility, full-time vs. contractor, regional cost of living, and other things.

Of course, the only person who can accurately gauge whether you're being paid enough is you but this at least gives you a rough idea of how the DBA community is being paid and how your salary stacks up against those of other people.


US/Canada Results (in US$)

 

 


Europe Results (in Euros)

 

 


Rest Of The World Results

(Alphabetical by country, slightly sanitized, some results removed because I couldn't figure out what was meant.)

  • Argentina
    • 0 years experience, AR$ 90,000
  • Australia
    • 5 years experience, AU$ 125,000
    • 8 years experience, AU$ 80,000
    • 8 years experience, AU$ 140,000
    • 10 years experience, AU$ 105,000
    • 10 years experience, AU$ 140,000
    • 10 years experience, AU$ 140,000
    • 10 years experience, AU$ 200,000
    • 13 years experience, AU$ 130,000
    • 15 years experience, AU$ 190,000+
    • 18 years experience, AU$ 125,000
  • Brazil
    • 2 years experience, R$ 35,000
    • 3 years experience, R$ 42,000 
    • 7 years experience, R$ 57,000
    • 8 years experience, R$ 96,000
  • Hungary
    • 11 years experience, HUF 1,100,000
  • India
    • 1 years experience, INR 240,000
    • 1 years experience, INR 384,000
    • 2 years experience, INR 2,100,000
    • 3 years experience, INR 560,000
    • 3 years experience, INR 630,000
    • 5 years experience, INR 500,000
    • 5 years experience, INR 600,000
    • 5 years experience, INR 650,000
    • 5 years experience, INR 900,000
    • 5 years experience, INR 1,100,000
    • 5 years experience, INR 1,500,000
    • 5 years experience, INR 1,600,000
    • 6 years experience, INR 1,000,000
    • 7 years experience, INR 645,000
    • 7 years experience, INR 1,700,000
    • 8 years experience, INR 600,000
    • 8 years experience, INR 930,000
    • 8 years experience, INR 1,560,000
  • Mexico
    • 3 years experience, MXN 465,000
    • 5 years experience, MXN 293,000
    • 6 years experience, MXN 450,000
    • 12 years experience, MXN 872,000
  • New Zealand
    • 3 years experience, NZ$ 80,000
    • 4 years experience, NZ$ 75,000
    • 8 years experience, NZ$ 125,000
    • 10 years experience, NZ$ 113,000
    • 10 years experience, NZ$ 120,000
    • 15 years experience, NZ$ 125,000
    • 15 years experience, NZ$ 315,000
  • Peru
    • 3 years experience, PEN 85,000
  • Russia
    • 3 years experience, RUB 409,000
    • 13 years experience, RUB 1,000,000
  • Singapore
    • 10 years experience, SGD 45,000
    • 13 years experience, SGD 100,000
  • South Africa
    • 7 years experience, ZAR 300,000 after tax
    • 9 years experience, ZAR 380,000
    • 14 years experience, ZAR 666,000+
  • Sri Lanka
    • 5 years experience, LKR 1, 536,000
  • Ukraine
    • 10 years experience, UAH 16,000

Categories:
Career | Surveys

Following my survey on company and employee loyalty, job security, and retention, I think it'll be very useful to the community to do a survey on salary vs experience for the SQL Server world - so here it is!

This survey is completely anonymous - there is no way for anyone to know what you voted. The more people fill this in, the better!

Please fill in the appropriate survey and I'll report on the results in a week or two. Consider your total monetary compensation (salary + bonus) for 2010 and it doesn't matter what your job title or responsibilities are.

Thanks as always for participating! Please publicize so we get some good representative results.

My favorite currency converter site is http://www.xe.com/ucc/ (link opens new window).


If you work in the USA or Canada:

Please choose the survey based on the number of years of IT experience you have and select your compensation range in US$.


If you work in Europe:

Please choose the survey based on the number of years of IT experience you have and select your compensation range in Euros.


If you work anywhere else in the world:

Choose the 'Other' answer in the survey below and enter your country, years of experience, and salary in your local currency. I'll figure out how to represent the data.

Categories:
Surveys | Career

 Dilbert.com

(Used with permission from Dilbert.com)

It's an interesting marketplace for DBAs right now. Depending on who you speak to, and what your view into the DBA world is, a few data points are evident:

  • There's a view that all the good people already have jobs
  • There's a view that it's pretty hard right now to hire good people
  • There's a view that some companies are looking for unreasonable amounts of experience for new DBA hires
  • There's a view that some companies are looking to give new DBAs way too much responsibililty

So this is all a bit of a problem. How can someone find a new job if many of the jobs are overly-demanding or look to be a recipe for over-stress? And how can companies expect to tempt people away from their jobs if the overall package isn't better?

Smart people working for good companies are going to realize that the grass isn't greener somewhere else, so will be making themselves more attractive to be retained by their present employers. And smart companies with good people are going to realize that they need to make sure they up the ante to prevent people looking for greener grass.

With all this in mind, I thought it would be interesting to conduct a survey to find out what companies are doing, if anything, to retain their talented DBAs, and what talented DBAs are doing, if anything, to show their companies that they're valuable employees. The original survey is here and this post is about the results.

It's worth reading the "Other" answers for each survey as they paint an interesting picture - with some lucky folks in dream jobs and some being treated very badly by their employers.

 

The "Other" responses are:

  • 6 x Not replacing employee's that leave, increasing my work load. yes this is sarcasm...
  • 5 x The company already is excellent for most of the above.
  • 4 x I just joined the company after years at another company that did none of the above.
  • 3 x Increased responsibility/visibility/opportunity.
  • 2 x Company is offshoring to China putting me out of a job later this year.
  • 2 x Company is providing me oppurtunity to work in the direction of making a change in existing working & make it more beneficial & efficient.
  • 2 x I am the company - but trying to increase my rates.
  • 2 x Increased compensation after I told them I was going to leave.
  • Exposing me to new SQL Server Tech that I have not had in other positions.
  • Flexible hours, health plan, trainings.
  • I left my previous higher paying gig to focus on what I wanted to do to build up my skillset.
  • I left the company as a result of salary. They hired someone new and less capable for more than I asked to stay.
  • I love this new job. Running my own SQL practice, autonomy, trust, decision making control, helping great clients. Don't tell 'em but they could withhold raises for a year or two and I'd still stay :-) First time I can ever say that about a job.
  • I'm leaving.
  • Increased compensation, increased training budget, new laptop.
  • Opposite of all: Decrease bene, no comp inc, decrease tellcom, 0 budget for training or hardware, no promo, increased expectations.
  • Outsourcing to India and making me redundant.
  • Paying for PASS Summit.
  • Retaining high quality people to work with.
  • The companys noble vision and mission.
  • Wait until the buy-out - salaries/bonuses may go up/be paid.

I'm very surprised that half the employers out there are doing nothing to retain their staff given how hard it can be to hire new, capable people. That's pretty depressing to see. Of course, we don't know the reasons why - could be the company is strapped for cash because of the economy or just that they employ Catbert as their HR Director. And you should see some of the private emails I've had from people about how companies are truly screwing the people that work for them.

On the flip-side, 40% of companies are increasing pay, flexible working, or training budgets - that's pretty cool. Savvy companies know they have to invest in their people to stay successful.

For those in the first 50%, I'd seriously think about why the company doesn't seem to value it's employees and whether it's time to consider moving somewhere that does. One of the cool things about the online SQL community is that there's a lot of empathy for people looking to change jobs and twitter can be a very powerful way to get the word out that you're available. Even if it's not the right time to be able to make a move, I'd still start racking up learning experiences (either at work or on your own time) to make yourself a more attractive hire when you are able to make a move.

 

The "Other" responses are:

  • 8 x Increasing work hours, increasing responsibility, learning on my own time, saving company money.
  • 4 x Many of the above. More for job satisfaction than for the company.
  • 3 x Fixing all the stuff that was bad before i joined such as no database backups (despite multiple on staff dbas).
  • 3 x I am the company - keeping my skills relevant via out of hours training.
  • 3 x Not what I am doing but what has happen is increasing work hours, increasing responsibility, on-cal, process efficiency and keeping it all together with bubble gum and duct tape.
  • 2 x All of the doing, none of the nothing and actively lookin.
  • 2 x Increasing responsibility, Learning on your own time, acting as unoffical community rep for company.
  • All top seven items.
  • Anything and everything a business owner does.
  • Building up to become the tech face of the company. New position.
  • Conducting SQL trainings.
  • Constantly developing relevant new skills.
  • I resigned weeks ago but I'm still hanging around & helping them.
  • I was a Systems Analyst which was part travel and working from home.
  • Increased work load.
  • Increasing work hours, increasing responsibility, learning on my own time, on-call biweekly, supporting new gloabl regions, improving proccesses, etc.
  • Marketing, Bringing in clients, training others, setting up best practices and processes to have more help in the SQL space.
  • Serial consulting...fixing everyone's problems then having the contract-to-hire not hire.

Wow - almost 90% of people who responded are doing something to make themselves more valuable to their employers. These are smart people. If you're stagnating in your job, there's no impetus for the company to value you and so you bubble up the 'next out the door' list. However, it needs to go both ways - the company has to realize that you're increasing your worth and that over time they need to recognize that increase by giving something more to you. As the economy starts to pull itself together there's going to be a point where you should call it quits and move on if the company isn't valuing your extra efforts - there's only so long you can increase your working hours or your stress from increased responsibility until it begins to affect your home life detrimentally.

Summary

When I used to manage teams at Microsoft I was very much a believer in recognizing good people and giving back to them (I was sometimes hobbled by Microsoft's nasty stack-ranking review process though) and I still do that today with the people that work for us here at SQLskills.com (Jonathan's eligible for a bonus of at least two vouchers for McDonalds Happpy Meals every month, and our assistant gets to spend the night in her own home once a week instead of sleeping in the cot under her desk - which is more than fair :-). A company cannot expect to attract and retain good people with a so-so benefits package and work environment that tolerates mediocrity and doesn't encourage people to excel.

But an employee cannot expect to be valued unless they show value. It can be a delicate balancing act, with some folks doing just the minimum to get by and others pushing themselves hard to be the shining example to the rest of the team. I've always been in the latter group, but I know *lots* of people in the former group who would whine and complain when they didn't get the pay rise or bonus they expected.

But this isn't about me, it's about you. IT budgets are increasing this year for sure, and you only have one life to live. Take a good hard look at where you are in your career, and how the company treats you. No one deserves to be treated badly or be unhappy in their job - and only you can do something about it. Back at Microsoft, I helped many people with their careers and my biggest message to them was that no-one is going to manage your career except you. Everyone's too busy with their own lives and careers to stop and push you to manage yours. Even as a manager, I would dedicate time to those that wanted to progress their career instead of those that didn't.

To close, I want to share with you my mantra for life: "There's no fate but what we make for ourselves" (from the movie Terminator 2). It's cliched I know, but when it comes down to it, you need to make sure you're getting the deal you want - life, job, partner, house, hobbies, respect... no-one else is going to do it for you.

Categories:
General | Surveys | Training | Career

Theme design by Nukeation based on Jelle Druyts