Voice of the DBA

Tag: career

  • People are talking about you

    I was listening to a friend give a presentation on getting a job recently. In the presentation, Chris Shaw, the speaker, mentioned my Modern Resume presentation, which was cool, but he also said something interesting in his talk.

    He said that social networking is huge, and you can choose not to participate, but even if you don’t, people will talk about you.

    I think that’s very true, and I caution people to be aware of what others might be saying about you. You never know when a coworker, a friend, or maybe a no-a-friend-at-all might post something about you. You never know when a particular person asks about you, your job habits, attitude, skills, or something else in their network.

    People will talk about you, and not necessarily online. It might be offline, and the best way that you can help ensure that you are aware of what people say is to be involved in networks. It could be social networks, but maybe you just want to touch base with your own network, trying to keep in regular contact with 10-20 people that could let you know if they hear anything about you.

    You won’t know everything that is said about you, but the more you participate in some type of networking, the more likely you are to hear what is being said publically.

  • Braindumps and Certification

    I saw a post recently that said that braindumps were the best way to prepare for certifications. It was posted from a certification vendor, so take it with a grain of salt, but I think a lot of people think this.

    That somewhat torques me off. I understand that certification can help someone get a better job, and it is good for a career. That’s fine, and I understand that if you are out of a job, or searching for a better job, that the price of the exam seems a little steep, and if you fail, you are out a decent amount of money. An exam costs $125 in the US, and that’s not an insignificant amount of money.

    However.

    We have enough people that don’t know what they’re doing. We have lots of people that struggle in their jobs, and often then don’t know what to do. Their bosses and co-workers aren’t happy. The struggle and get stressed, and they complain about their jobs. Stability is lower, software quality slides along the floor, and it’s a bad fit.

    Not everyone falls into this category, but having taken quite a few exams, I’d say that if you have some knowledge of SQL Server, and you work through a lot of exercises from any certification book, you’ll be fine. It’s hard, but it’s supposed to be. You’re supposed to be competent if you pass the exam.

    Finding ways to pass without being competent, or searching for a guarantee, isn’t good for your career. And it’s certainly not good for mine. Every person that passes who doesn’t really understand what they’re doing makes certifications that much more of a joke, and that much less valuable to employers.

    Which is the point for most people. They get the certification so that employers will be *more* likely to pay them more.

    Do yourself a favor. Study for the exam, learn how to handle the objectives, and then take your chances on the exam.

    There are a number of deals for second takes as well, so be on the lookout for those.

  • More Than SQL

    SQL Saturday #52I am speaking at the upcoming SQL Saturday #52 – Colorado in the Denver Tech Center in a little over a week. I’m doing a presentation on The Modern Resume and a short mini-keynote talk at lunch time, and I’m joined by some amazing speakers, like Kevin Cox from the SQL CAT team, User group President Marc Beacom, and local MVPs Glenn Berry, Paul Nielsen, and Chris Shaw. We have some amazing people coming from out of town like Jack Corbett from Florida and Tim Mitchell from Texas, and Jason Strate from Miinesota. It’s a fantastic lineup with many more talented speakers and the chance for you to get a free day of world class training on things important to your career as a data professional.

    Those of us speaking are doing our part to give back to the SQL community, which is an amazing group of people that not only strive to be better at their jobs, but also engage and interact with one another, sharing that knowledge. I’ve learned a lot from many of these people, and hope that I can teach a little bit as well.

    However at this SQL Saturday, we are giving everyone the chance to do more than just learn about SQL. You can give back to this local community as well. We will be accepting donations of food that speakers will distribute back to the community food banks and victims of the fire near Boulder in Four Mile Canyon.

    There is more to life than our work. The SQL community is here to help you with your career, and we are happy to do that. This is a great way of also looking to give back to the local community in a way that I hope catches on at other events.

    Steve Jones

  • Technical People Should Blog

    I ran across a great blog titled: Post 300 or why all developers should be blogging. The reasons given in the articles are great, and I think they apply to all technical people.

    You will learn by blogging, and you will keep stuff in a place that you can go back and review it, in addition to giving you something to impress interviewers. There is one more big reason, however.

    You need to communicate.

    I don’t think I’ve ever seen a position that didn’t require some type of communication skills. You might not need to get up in front of a group and express things (or you might), but almost everyone needs to document things or communicate through an electronic written medium. It could be email, IM, texting, some forum system, or anything else. However you need to communicate.

    The more you build these skills, the better off you will be. There are definitely some very talented people that can get away with poor social skills and poor written skills, but that’s not most of us. Most of us need to communicate effectively.

    To me, blogging is like typing. A developer that hunts and pecks with two fingers is not likely a good developer. And certainly they’re not an efficient developer.

    The same thing comes from communicating. You need to practice it to get better at it. You don’t need to write as much as me, or write as long a posts as I do, but by writing regularly, you’ll learn to better express yourself.

    (cross posted to The Modern Resume)