Voice of the DBA

Author: way0utwest

  • T-SQL Tuesday #008 – Learning

    It’s time for another T-SQL Tuesday, the brainchild of Adam Machanic (Blog|@AdamMachanic) of SQLBlog.com. This time we have a SQLServerCentral author, and MCM, Robert Davis, running the show.

    How To Learn

    I’ve had a lot of school in my life. 12 years of primary education, 5 years of undergraduate level education, 2 years of graduate school education, 7 semesters of calculus, and even a few programming classes since then. In all those hours, I have learned a few things, but the most important things were learning how to learn.
    A high school degree (US) or an undergraduate degree (BS/BA) doesn’t really teach you a lot of practical skills, IMHO. However what they subtlety teach you is how to learn. You have to develop the skills more and more to teach yourself, research, analyze information. Those are the skills you will need as you move into a career. Even engineers, who learn a larger percentage of skills in skill, need to learn more in the workplace, and successful students tend to have an easier time picking things up later.
    Not that average/below average students can’t. Sometimes it’s just finding something that brings out your passion, which often isn’t school.

    How I Learn

    So how do I learn? As much as I like lectures, and I listen to many of them at SQL Saturdays or other conferences, it’s not necessarily helping me learn or build a skill. It increases my knowledge base, gives me the ability to think more laterally when confronting issues or searching for a solution, and it inspires/excites me. It gets the juices flowing.
    However to actually learn something, to build a skill, I need to do. I typically learn by actually writing SQL statements. Setting up mirroring, testing restores. Those skills, just like muscle memory from performing a task, are built for me by repetition and practice.
    That’s one reason that I have taken relatively few classes in my career. Taking a week out and being immersed in something like VB or SQL hasn’t helped me nearly as much as having hours a day across months to actually write code and try to solve a problem. This blog, at least the T-SQL parts, have tended to be focused on rebuilding those skills for me. Practicing things that are new, or that I haven’t spent much time on.
    I prefer working with books to classes, but it’s the same thing for me. I retain some snippets from books, but if I don’t practice the skills, actually get hands on time, I haven’t learned much.

    How You Learn

    I don’t know. I think you have to try some different things and then evaluate if they work. If you attend a class, see if you use those skills across the next couple months. Did you really learn something? Try something you learned a couple weeks afterwards. Did it stick? If not, try something else. Read about it and do the same test. Work through examples from a blog post/article/book/class, and see if that helps.
    Learn how you learn. It’s one of the most valuable things you’ll ever do.

  • Why I Write

    I have a great job. Actually it’s a fantastic job for me. I have flexible hours, I can work almost anywhere, which means that I can do things like go with my kids to events, even trips out of town and still work. I get to express myself, and talk about interesting things.
    However there are hassles, it can be a grind, and there is pressure to come up with something interesting on a regular basis. I do enjoy it, but I have had times where I thought about going to be a DBA somewhere and letting someone else point out work for me to do.
    Then I get notes like this:
    I’ve been in this business since 1980, starting with CDC punch cards, so you can see how much ‘experience’ has accumulated in what seems like the wink of an eye. I don’t get the chance to read all your editorials, but from the ones I have read, you have the gift ( because it is a gift ) of seeing the whole picture!
    … Your insight and knowledge of not just ‘work’ but of people and careers is the best, more so than any other I’ve read. Don’t lose that deep appreciation of life/work, care and intelligence your editorials have come to be.
    That’s cool. It arrived in my Inbox recently and made my day.

  • Settling or Pushing On

    I read a blog recently that was titled: Time to Stop Settling. I think that the author (a friend) was intending to motivate you to move forward, and try to change things when you see a way to make them better instead of living with them.

    I agree, but….

    My caveat here is that you also need to find balance in your life. One of my favorite quotes is “God grant me the strength to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference.” I think that quote is telling you to strive for balance, and realize that you cannot change everything, but you can change some things and you ought to think about those that you can.

    We all have tough times in our lives, especially at work. Even though I have the best job in the world, I have bad days, I have things I don’t like, things that I can’t change. I strive to balance the stress and workload with the good things, and while I try to move forward, I move forward in different ways. Some periods might involve more time with my wife, some more vacation with family, some more speaking, some more writing, but they all are a part of life.

    Don’t settle when you don’t need to, but don’t try to change everything. Pick your battles and look to make headway, make things better, not “fix” everything.

  • Sunday Morning Work

    Up early, the only one in the house, so I made coffee, sat down to check on SSC and the news of the world, and got caught up answering questions.

    A few interesting threads caught my eye:

    Went back and forth on a few threads, making the day get started in an enjoyable day. I just enjoy the SQL stuff.