Author: way0utwest

  • No More MCM

    This is part 1 of a 3 part series of thoughts on certification and Microsoft technologies.

    I’ve heard that Friday afternoon is the best time to fire someone. People are leaving early, the office is quiet, and you can let people go quickly and get yourself away. It also gives the remaining employees some time to grieve, and hopefully, come back to work Monday without some of the shock they initially experienced. At least, that’s what they say. Personally I think there’s no good day, and productivity always suffers somewhat whenever there’s surprising, upsetting news.

    Recently, just before the US Labor Day holiday, late on a Friday, I saw a number of announcements on Twitter that the MCM program had been discontinued. Since I was on holiday, I thought I’d missed something, but apparently not. It was late on a Friday that the an email was sent to all MCMs and MCAs notifying them of the change. It was a brief email, noted here, and didn’t include some of the reasons of that were given as a comment in a Connect item filed to save the program (the comment was from Tim Sneath at 1:32pm). There’s been a variety of coverage and blogs around the Internet as well.

    We aren’t being told the whole truth, nor do I expect to be told the whole truth. This is Microsoft’s program, and as such, we follow along and adjust, or choose to ignore it. In this case, I can’t believe that this was anything other than a cost based issue, designed to reduce expenses and raise profits. In all likelihood, someone(s) bonus depended on internal Microsoft Learning metrics being met (probably revenue or profit numbers), which the MCM/MCA program were reducing. In an effort to look better, the program was chopped, without a lot of input, communication, or discussion with the people actually working to better the program. I expect Tim Sneath and others were caught off guard with the decision and told to deal with it. They did so poorly, extremely poorly. In hindsight, I’m sure someone wishes they’d composed a better message and delayed sending it for a couple days.

    I attempted the first part of the MCM early on, with a voucher. I didn’t pass, but I learned how hard the exam was, realized it was within my capabilities, but that it would require some serious study. I didn’t proceed further because of other commitments, but I’ve watched more and more people work through the MCM process, usually over months or years as they learn, struggle, research, and drive themselves forward.

    Ultimately the achievement isn’t the certification, but the journey. The efforts candidates go through, the knowledge they acquire from study and hard work, and perhaps more importantly, the skills they build to teach themselves new techniques. I wouldn’t hire an MCM because I was sure they necessarily knew everything about my environment. I’d hire them because I would be 100% confident they could find the problem and fix it, no matter whether they used old knowledge or acquired new proficiency on the spot.

    That was the real value of someone who completed, or even seriously worked towards, an MCM.

    Steve Jones

    Video and Audio versions

    Today’s podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

    Follow Steve Jones on Twitter to find links and database related items and announcements.
    Steve Jones Windows Media Video ( 26.3MB) feed

    MP4 iPod Video ( 30.3MB) feed

    MP3 Audio ( 6.1MB) feed

    Feeds are available at iTunes and Mevio

    To submit an article, rant or editorial,
    log in to the Contribution Center

  • Be Careful in Business

    I like most of the SQL Server people I meet. Most of you are polite, cheerful, friendly, and it’s nice to share a few minutes of my life with you, chatting about anything. Whether that’s technical issues with SQL Server, running, books, or anything else, I often find my life richer for the time spent with others.

    However I wouldn’t go into business with most of you. In fact, the number of people I’d make a business partner can probably be counted on one hand.

    I wish it weren’t so, but I would choose my business partners very carefully, as carefully as choosing a mate. Getting into business is really like growing your family and all of your shareholders and partners are closely tied into your life. Since it’s not easy to get out of those types of relationships, you shouldn’t go into them too quickly.

    I was reminded of this when I read How to Screw a Friend out of an $800 million idea. Like The Accidental Billionaires/The Social Network, it’s a look at friendships and business, and how success caused problems. I don’t know if there is liability here, or a moral failing, but it does remind me that I should be careful in business.

    Just so you know, there are lots of you I’d work with. Easily thousands.

    That’s way less than the number of people I’d work for, which is likely a couple dozen. There are some good business people I’ve met who I think would be a good boss and who I would approach if I needed a job.

    Partners? I could name three off the top of my head and maybe three more I’d consider and want to get to know better.

  • Developer Pressure

    I’ve been learning about continuous integration (CI) and continuous deployment (CD) from a number of people at Red Gate Software. As a company, we’ve embraced the concepts, pushing most, if not all, of our software through this process. We are using our Development Manager software internally for more and more of our web projects. Some of our tools, SQL Prompt, include “experimental features” pushed out rapidly to users, with the options for them to turn these features on or off as users desire. We update these tools often, releasing dozens of times a year. There are no shortage of challenges in working at this pace, but we are addressing the issues as best we can.

    One of the big issues that I see in a CD environment is there is a bigger burden placed on developers to ensure the code is of very high quality. In this type of environment, there may be less QA work being done manually, and more automated testing. There is a quicker turnaround when you find issues that developers need to correct. Customers see changes sooner, and more often, and will expect corrections or new features to appear just as quickly. All of this adds up to more pressure on individual developers.

    The question I wanted to ask this week is about how developers feel about this? You could take this question a number of ways, but let us know what you think.

    Is Continuous Deployment good for developers?

    Does this result in higher quality work from developers? Is it more stressful? Does it mean that developers get into a rut and not learn new techniques because they are working faster? Does a developer have less responsibility because automated test and customer feedback will allow them to quickly address issues?

    I think this is a multi-edged sword for developers. It can be a burden or a blessing, but a lot of the way you view it probably depends the individual developer. No matter what the issues, if you use it to improve your skills, as well as your software, I think it’s the best way to build software.

    Steve Jones

    Video and Audio versions

    Today’s podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

    Follow Steve Jones on Twitter to find links and database related items and announcements.
    Steve Jones Windows Media Video ( 17.5MB) feed

    MP4 iPod Video ( 21.0MB) feed

    MP3 Audio ( 4.2MB) feed

    Feeds are available at iTunes and Mevio

    To submit an article, rant or editorial,
    log in to the Contribution Center

  • Good and Bad Interview Questions

    Why is a manhole cover round? How many cows are in Canada? How would you cure world hunger?

    There’s no shortage of strange interview questions you might be asked in the tech world. If you like these questions, and want to interview, or be interviewed in this way, grab a copy of How Would You Move Mount Fuji and start studying. These are the types of questions that Microsoft, Google, Amazon, and many other tech companies have been asking candidates for years. Since so many technology people read about the practices from these companies, I wouldn’t be surprised if many of you had been asked these types of questions in other interviews.

    Personally I’ve never been asked any of these strange questions, and am not sure how I’d respond. My interviews have often been very technical, but have included a number of “how would you..” or “tell me about a time when..” questions. However ultimately I’d like to think that my soft skills, and my social skills came through positively and that was the reason I often received job offers.

    Many IT managers are starting to feel that these types of questions, and even highly technical questions, aren’t the best way to evaluate a candidate. Hiring costs are up, both in direct costs spent on finding people and the indirect costs of the lost work from current employees interviewing people. There is pressure to hire well, and find people that can be productive. It seems that many managers are starting to look to evaluate candidates in other ways beyond the technical skills. Those skills are important, but not necessarily more important than soft skills.

    That’s been the way I’ve looked at hiring for years. I can often teach someone technical skills, but I can’t teach them to fit in with a group, or be a team player, or even just be someone that won’t annoy the rest of the team. Those social fits are very important if you want your team to function well together, providing support, help, and inspiration to each other.

    Building culture is hard, and while technical skills are important, employees that bond together help push each other to do better work for the team. Employees that dislike each other can bring down overall quality and coordination very quickly. The sooner managers learn that, and learn to respect employees while challenging them, the sooner their departments will start to shine.

    Steve Jones

    Video and Audio versions

    Today’s podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

    Follow Steve Jones on Twitter to find links and database related items and announcements.
    Steve Jones Windows Media Video ( 19.6MB) feed

    MP4 iPod Video ( 23.3MB) feed

    MP3 Audio ( 4.6MB) feed

    Feeds are available at iTunes and Mevio

    To submit an article, rant or editorial,
    log in to the Contribution Center