Voice of the DBA

Tag: SQL Saturday

  • SQL Saturday #28 – Slides and Impressions

    I’m late, I suck, but here’s some things I started in Baton Rouge and am just now getting out.

     

    First, I’ll add my slides to the SQL Saturday site soon. I did two presentations and the keynote, which I posted yesterday. However I know a few people want to see them, so I’ve added them up on SQL Saturday to a static page I built.

     

     

    Impressions of SQL Saturday #28

    I have to say that Patrick LeBlanc’s enthusiasm is infectious. There is a whole team of people in the local area that I was thrilled to see again and impressed with the level of effort they put into making the event run smoothly. They’re always happy, very welcoming with Southern hospitality, and they make the event a lot of fun for everyone involved, especially those of us that come from out of town.

     

    I grabbed a little video and some images, adding in a little narration. Nothing special, but some memories for me:

     

     

    This was an impressive lineup of speakers. Not to take away from the local speakers, who did a great job, but I believe Patrick had 14 MVPs, many from out of town like me, that came to the event. The speaker’s dinner was great, with about 50 people there, which is huge. Many I’ve attended had about 12 people. Patrick even personalized shirts for us. I don’t wear many of my SQL Saturday shirts, but I’ll wear this one.

     

    The event ran very smoothly. The group gets the use of a building a LSU, which is a beautiful place. They had two hallways, with food and sponsors in between them. As much as many people don’t want to see vendors, those people and their money is the reason the event runs. Remember that the next time you don’t want to hear about a product or pass a table.

     

    I had one of four early morning sessions that gave people something to do if they arrive early, and helps beginners get some basic knowledge. I’d like to see this at more events. Then I gave the keynote, which can be a challenge at many places. About 250-300 people were there, I hurried a bit, but I think it went well.

     

    Then it was a full day, 8 or 9 tracks, of sessions. There was even a great .NET track run by a guy basically giving a full day of .NET basics to people. I loved that!

     

    Lunch went smooth, with some optional vendor presentations (see three paras above), but they were sparsely attended. Lots of people sitting around instead, which is fine. I think lunch is a good decompression time.

     

    After lunch, more sessions, and I walked between a few, trying to get some clips of different people, checking out some speakers that I, surprisingly, hadn’t seen before. I popped in to watch Sean McCown, Tim Costello, Denny Cherry, Wes Brown, and a few more. I made it a point to watch a few people talk.

     

    The hallways were mostly dead during sessions, a nice sign. People were coming for training. I shook a lot of hands, and had a lot of 3 minute conversations with students that attended various colleges, even some out of state. They were looking for some basic training. I met local people coming to get some knowledge that the boss wouldn’t pay for, and even a guy that had driven 3 hours from M-eye-ess-ess-eye-ess-ess-eye-pee-pee-eye for training since his employer didn’t pay for much. I queried everyone if they thought it was worth it, and got all positive responses.

     

    A long day, especially for me since I started at 6:30 and left around 5:15. I went for a run on lovely University Lake before going to the after party (after showering). It was mostly for volunteers and speakers, but I had fun chatting with people until around 10 when I left to get dinner.

     

    All the SQL Saturdays are good events. I haven’t seen a bad one, and they have tended to run fairly smoothly. The only things I noticed here were a lack of water (we ran out in the afternoon, but had lots of Orange soda) and the raffle at the end was hard to hear Patrick. For the latter, I told him they should be up on the stairs, not at the bottom. For the water, I know there’s a lot in the air, but more would be nice, especially since I try to promote being healthy. Patrick had fun as there were tweets asking us to drink Orange Soda and then he raffled off a case at the end.

     

    The enthusiasm and fun that that the volunteers have, the jokes they make, and even the tweets coming out make this the most fun of all the events I’ve been to.

    A few other links:

  • SQL Saturday Advice – Feedback and Raffles

    At SQL Saturday #28, I was surprised to be given the speaker evaluations after my first session. One of the volunteers approached me and gave them to me, saying that I could have them and use them.

    That surprises me since I think one of the things that people rarely do is give good feedback to speakers. Too often we design these nice forms and someone just gives all 4s or 5s. They just don’t think about it much.

    I favor a simple feedback form, but I’d also include a raffle prize or two that can incent people to turn them in. I know it’s a pain to sort them out by speaker, but I think a simple session name/title, a ranking (1-3 or 1-5) and a comment would be nice.

    Then draw some at the end of the day and give prizes. I suspect we’ll get more, though not necessarily better, feedback.

  • The Long Road

    Text of my keynote from SQL Saturday #28

    Welcome to SQL Saturday #28 and I’m pleased to be back in Baton Rouge. This is my second time here for the event, and it’s as hot and muggy as I remember. At least this year I knew enough to bring a second shirt to wear on the ride over

    My theme today is The Long Road.

    Life is, to me, a long road and hopefully it will be for most of you as well. That’s a metaphor that we see used often for our lives. It’s a road that you can plod along, one step at a time, dreading each day, looking down at your feet. Or one that you can skip along, looking at the flowers, enjoying each step as you make it.

    This same metaphor can fit your career as well. Most of us will work for over 40 years, close to half our lives, and in that 40 years we’ll spend most of our time each week working. Five days a week, sometimes more, working at some craft, some profession. There’s nothing wrong with that, but you should enjoy that time, and you should be growing yourself as you move through your career. It’s been said that there are three things that really motivate all of us: autonomy, mastery, and purpose. Hopefully you can find all three in your career.

    I’ve seen two sayings about the long road metaphor that I think are applicable to our careers. The first saying is that "today is the first day of the rest of your life", implying that it’s never too late to get started on whatever it is you want to do, or want to learn.

    The other saying is "you’ll never be as young as you are today." Also meaning that it’s as good a time as it ever will be to start something. That one seems to mean more to me as I get older

    One of the things that I really enjoy as I go through life is running. Those of you that follow me on Twitter or Facebook might see me posting something like Day 523 or Day 697. Today is actually day 704, though it won’t be official until later today. I run every day, and that number is the consecutive day count.

    As I run, I’ve noticed that there are days when I feel good, when I’m strong and enjoying the run. Those days I look up, and watch the world as I run. I might find myself deep in thought about something at work. Those are the days the run goes quickly, and I’m amazed how far I’ve gotten.

    There are other days when I’m tired, or sore, or in a hurry. Those are the days I look down at my feet, counting steps. It’s a struggle when that happens and those are the days I don’t necessarily enjoy the run. My aim is to have more good days than bad ones, and to really appreciate the good days when I have them. Or remind myself about the good days when I’m having a bad one.

    As I’ve run, I’ve tried to learn how to run better. That sounds a little silly if you’re not a runner, but it takes time to learn how to run. You have to get in shape, obviously, but you also have to eat right, maybe alter your technique, and learn to find the "zone".

    I think you want to approach life, and your career, in the same way. Enjoy the good days, work to build more of them, and strive to have more good days than bad ones.

    Hopefully all of you will have a long and prosperous IT career. It can be a career that’s as simple as doing your job every day. There are many people that can do that, even today, by just doing a solid, average, competent job. They go to work every day, relying on the skills that they have learned in the past, content to do a similar level of work every day, and they go home every night to a life outside IT.

    There’s nothing wrong with that, and if you can do it, that’s great. However I’m not sure that’s enough, especially for those of us working in technology.

    Life is full of risk. In making decisions about how we live our lives, we  intuitively run risk calculations about possible outcomes every day. Can we cross the street before that car arrives, is this jambalaya safe to eat, we make millions of these risk assessments each week.

    Some of us lean towards less risk in our choices, some more. And the level of risk we can tolerate is not necessarily consistent in all parts of our lives. I know people that are afraid to gamble $5 at black jack, but they’ll happily drive a car along a busy highway at 120mph. Those examples are from my life, by the way.

    In our careers, we deal with risk constantly. Is our job safe? Is the way we do our jobs affecting how our boss perceives us. Does the company value our skill enough to invest in our training. Is the company making enough money to avoid layoffs? Are we likely to be let go? Each of these situations introduces some level of risk into our continued employment. We often perceive that as some level of "worry" about our jobs.

    And we can’t always control the risk in our job. Companies might decide to downsize, cancel a project, or even leave the area. ENI Petroleum, one of the largest oil drilling companies in the US left New Orleans after Katrina. That was a decision that I’m sure did not involve a consultation with the IT staff. Or maybe not even any warning.

    An employment change doesn’t just happen because of a disaster. We all have seen the changes that IT brings to a company, often eliminating some amount of work being done by people. Sometimes there’s other work to be done, but sometimes there isn’t and people are let go.

    In the news the last few years we’ve seen that companies might decide to offshore work to save money, or outsource it to another company and downsize, or even onshore it to another part of the country where you can’t even apply for the position anymore. I’ve seen all of those happen, often with a loss of jobs in the local area.

    Maybe it’s not a cost savings issue. Maybe the owner just decides to move the company. United relocated their headquarters from Seattle to Chicago and not all people were given the choice to move. Lots of non-executive staff lost their jobs, some because of layoffs, some because people didn’t want to move. I once worked for a private company, with about 50 people in it. I left, but a few years later the owner decided to move the company out of state, wanting to relocate his family. I’m sure some people  moved, but some wouldn’t, and some wouldn’t be given a choice.

    What does that mean for you? After all, lots of the "bad" situations for your career are out of your control.

    Or are they?

    You can lower your risk, or mitigate it, by increasing your skills. Each additional skill that you take on, or each time you add depth to your skills, you are making yourself valuable. Or you should be. And you need to make sure that you are adding skills that are relevant to your career, and you ought to make sure your boss knows this. These skills can reduce the chance you’re laid off, or increase the chance that you’ll easily fnid a new, or even better, job, if something happens to your job.

    These skills don’t have to be in IT. I’m sure there are some of you that want to pursue a career in some other field. Maybe you want to be a chef and practice at night, doing this IT thing during the day. That’s fine and if that’s the case, make sure you’re picking up relevant skills in cooking that will help you find that dream job. However if it’s going to take some time, don’t completely neglect  growing your day job.

    By coming to events like this SQL Saturday, attending conferences, even reading books and articles online, you are helping grow your skills. These events should increase your value to your employer. Or to a future employer. They show some effort on you part to learn, to become better at your job. They make you more marketable and that should give you some security, and peace of mind, that you can enjoy a long career. That’s if you actually are making an effort and learning some new skill.

    I’ve heard people complain about the long hours in IT. The lack of time to work on their skills, no training budget, or just being exhausted. IT is harder than other jobs.

    But is it?

    Lots of industries require new knowledge on a regular basis. Doctors are required to work on their continuing education every year. Many doctors are constantly struggling to keep up with medical journals, attend seminars, and advance their skills. It doesn’t always show up when we visit them, but they are always learning. I’m sure there are slackers, but as a group, doctors and  nurses are devoted to continuing education.

    Lawyers as well have constant education requirements. Some of it is driven by regulation, with requirements set by the various state bars. Some of it is driven by business, with the need to understand new laws and court decisions that affect their particular specialty.

    Accountants as well must work on their career regularly. Many of them driven by the ever changing tax code, which never seems to get simpler.

    I think sometimes that we just think IT is a 9-5 job because of the office environment, but I’m not sure that it is, or should be. Not that I think we should work 100 hours a week like a doctor on call, but that we should be prepared to be flexible, and be prepared to constantly improve our skills.

    In IT we typically do not have regulatory requirements, though some of you impacted by HIPPA or SOX might disagree. We do, however, have business requirements that change, and we are driven to learn by constantly changing software and hardware. Often we find ourselves pushed into new areas as companies evolve and look to implement new systems and applications, often built on new platforms.

    So we do need to continue to work on our skills, and we ought to embrace that. Developing skill at your craft will benefit you by making your job easier, you’ll work faster, and at a higher level of quality if you enhance your skills.

    And it’s a lot easier if you learn to enjoy what you do. You ought to enjoy the particular Long Road you’ve chosen to journey down. If you don’t, I really urge you to consider changing professions. I know many of you have mortgages or other responsibilities that require you to earn a certain amount of money, but there really is more to life than money. If you really want to do something else in your life, make a plan, sit down with your family, discuss it, and find a way to make it happen. My wife is looking to leave her job at some point and work with horses full time. We’re working to get to that point where she can actually do that.

    I’ll leave you with a short story of someone that continued to work on his craft for years. A man from this part of the country that you might have heard of developed some skill as a musician. He became successful and played over 300 shows a year for 30 years. That’s over five days a week every year. Probably not that far from what many people in IT work.

    Early in his career, while building his skills, he hauled coal for a living while he playing at night until he could focus on his music. Not the best job in the world, and some of you that don’t like your IT role ought to think about that. You have a fairly easy job, physically. Even after gaining success, he continued to work at his craft.

    At age 63, still playing many nights a week, he finally had a #1 hit. That song dislodged another band from their 14 consecutive weeks in that slot. Anyone know the group that was dislodged?

    It was the Beatles.

    Does anyone know the song?

    It was Hello Dolly!

    The artist?

    Louis Armstrong.

    You could do the same thing, though perhaps not with the same intensity, but with some level of effort. My business partner is Andy Warren, and he’s the founder of SQL Saturday franchise and SQLServerCentral with me. He says that to build a good level of skill in a new technology, you need to devote 100 hours. That’s a reasonable level of effort in a year that I think many of you can spend. It’s 2 hours a week, 2 hours out of your weekend, concentrating on building a skill. Maybe you don’t want to do that every year, but perhaps you can spend 50 hours a year, a little over one week of full time work, growing your skills. If you are in a riskier situation, or want to advance quicker, maybe you want to spend 200 hours and learn two new things fairly well.

    Today I would urge you to spend part of your time here on sessions that will help you build stronger, deeper skills that you need in your job right now. Then I’d try to spend some time looking at something that interests you, or might help you get that next job. Maybe something to make you more attractive as an employee, and lower the risk that you’ll be out of work or, more likely, that you have to accept a job that you don’t like.

    And if you still have time, visit a session on something new, something you’ve never worked with. You might discover that a fascinating way to spend 100 hours in the next year. Or that it’s definitely not the way to spend 100 hours.

    You are well on the way down your own Long Road in your career. Maybe you are building on your existing skills, or you are working on new ones. Either way, you are taking time out of your busy life, and spending your valuable free time to come here today. I thank you for coming, and applaud you for making the effort.

    I wish you the best of luck on the journey down your own Long Road.

    Enjoy your day here at SQLSaturday.

  • Travel Day – SQL Saturday #28 Baton Rouge

    On my way to New Orleans today where I’ll pick up a car and then drive to Baton Rouge for SQL Saturday #28 tomorrow. This is my second time heading to Baton Rouge for SQL Saturday and I’m looking forward to it.

    Last year I flew in early, thinking I’d get to the New Orleans Saints training camp in the afternoon, but a thunderstorm cancelled the event and I missed it. This year Friday is a day off, as is Sunday, so I won’t go again, :(, but I am likely meeting Tim Mitchell (blog | Twitter) for lunch as he’s coming in from Dallas about the same time.

    I’m looking forward to a little New Orleans food and then a great speaker’s dinner tonight.

    Tomorrow I have an early session, Beginning SQL Server, to try and get people introduced to what SQL Server can do and a few basics. If you know about SQL Server, but haven’t worked with SSIS, Tim Mitchell has a basic session on Building Your First Package early in the morning as well.

    I also have a seat on the Ask the Experts table during the afternoon, but before that I’m doing my Modern Resume presentation at 10:15. I’ll be done early, and hanging out until the raffle. Then I’ll go run around University Lake before heading to the after party.