Voice of the DBA

Tag: career

  • Look Beyond What You See

    One of the sales managers at Redgate Software posted an origin story about how he came to work at Redgate Software. It’s an interesting story, and while I don’t work in sales or have the same origin story, I don’t know that I could have seen the place I’m in now early in my career.

    When I saw the video, it made me think of this movie scene, where Rafiki asks us to look beyond what we see. I think this is a hard thing for many of us, especially when many of us have been leaning on our skills in the past. What we know and what we are good at doing has led us to this place. Picking a new direction, or thinking in a new way might be hard.

    For lots of us, we might be concerned about the cloud, and what we should learn or where this might lead us.  Azure or AWS? Some might be concerned about moving into management. Will I be good at it? Will it be a better career for me? Others can wonder about specific technologies. Power BI or Tableau?

    I wouldn’t recommend a specific thing for anyone without knowing more about their situation, but I do advise people to be open to opportunities, investigate and ask questions, and embrace possibilities. Look for what might be slightly out of focus or uncomfortable for you. Look beyond what you see and consider what you haven’t seen before.

    My origin story is getting an electrical engineering internship. Finding that the group needed help with Lotus 1-2-3 macros. Realizing I liked working with computers more than walking around a power plant and working with electricians to follow designs. I then realized that I didn’t love programming or network support, but I saw an opportunity in 1991 to work with SQL Server, and I took it. I looked far beyond what I had thought about as a teenager, as a college student, and even as a young person in my career. I embraced an opportunity to write an article and that led me to SQL Server Central and now Redgate Software.

    Think about the directions you could take in any situation and open your eyes to the possibilities. You might find an opportunity that changes your life.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.

  • Being Reasonable

    The last two years have changed the way many of us work in technology. The pandemic allowed many of us to work remotely, a challenge that many companies are struggling with. Or perhaps, management is struggling with and employees appreciate. In any case, no matter what your situation, the way we work has changed.

    The change wasn’t easy at times, and even though many people appreciated the extra time in their day from not commuting to work, they often had other challenges. Co-existing with others in a residence, finding a place to work that allows concentration, and even learning how to separate work from home life. These have been issues for many data professionals and other technologists. Even if we’ve had an easy time adapting, not all of our colleagues have felt the same way.

    One of the core values that we have at Redgate Software is being reasonable. It’s a somewhat amorphous value that I didn’t know how to interpret or act on at first. Our former CEO repeated this often in updates, to the point where I have heard other management and employees use the verbiage in meetings on a regular basis.

    I think as a company, we’ve learned how to be reasonable with others. We don’t overly rely on policies or rules to guide us in how we accomplish work and interact with each other. Instead, we use judgment, and managers are flexible in their interactions with employees. As a Type-A, driven American, it has sometimes felt strange to not have everyone trying to outwork everyone else. It was an adjustment for me.

    The idea is not that we do little work or avoid work, but that we avoid working too much. It’s not about the hours anyone puts in, it’s the contribution they make to their department. No one watches the parking lot to see who’s in the office or who’s logged in. Instead, we expect people to manage themselves, meet their commitments, and be accountable for the tasks they’ve been assigned. At the same time, we cover for each other and support the team. We’ve had people out sick, out for maternity/paternity leave, or struggle with other life-altering issues. The rest of their team will help cover for someone, knowing they will do the same for us.

    We treat each other as humans, have empathy for others, and act towards others as we would want to be treated. At the same time, we have goals and missions to drive us forward to build a better company. We find balance in how we do this, and it’s worked very well for over 20 years. In many ways, it’s how I try to live life. There are good and bad days. There are busy ones, some hectic, chaotic times, but also slower times when I can recover and recharge.

    It is really hard to describe what being reasonable means, and at times I am not quite sure how to act in a situation, but I try to put myself in someone else’s shoes, see their point of view, and then decide how I would want to be treated. That usually guides me as to how I should proceed. It’s worked well for 15 years for me and I look forward to being reasonable for the next 15.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.

  • Share Your Mistakes

    I wrote the other day about a culture of allowing mistakes. We know mistakes are going to happen, so we ought to accept them. Even stupid ones. I make them at times, my wife does, my kid does, so I have been working to not get upset and emotional about them. Instead, hold someone accountable, let them fix things, and try to do better in the future. It’s what I’d want, and what I am trying to do with my family, friends, kids I coach, and others.

    Many of us share knowledge and information. One of the reasons I love events like SQL Saturday is that others share their knowledge. I especially appreciate is when someone shares a solution and how or why they build it. Hearing their stories, the reasons for their decisions, and what works well is great. I learn in a similar way from blogs, which is why we syndicate blogs at SQL Server Central and include them in the newsletter.

    By the way, if you have a blog and want to syndicate it (full feeds, please), contact the webmaster or submit an article.

    We want to share knowledge, but we should also remember to share mistakes. We make wrong turns, and sometimes others might not take our advice because we recommend them. Instead, they might go down the same wrong path as we did previously. They might make the same mistake we did. Sharing and showing how a decision didn’t work well can be a powerful and valuable story. We all respond well when we empathize, and most of us can empathize with a mistake.

    Almost every interview I’ve been in has asked me about a mistake, misstep, or other error that I’ve corrected or learned from. Usually, there is some variation on “tell me about a difficult situation” that you need a story about. In a technical interview, this might be based on a programming or database administration problem. In other interviews, this might require you to think about interactions with others.

    In any case, I encourage you to keep stories handy for interviews or reviews. I’d certainly also suggest that you blog about them. Writing is a valuable communication skill we all need, especially in these days of mostly remote interactions. Practice writing, get better at presenting your thoughts, and learn to share stories that will help others in their journey to be a better professional.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.

  • A Culture That Allows Mistakes

    Building a culture that promotes teamwork, efficiency, retention, and other positive attributes can be challenging. While many organizations want accountability and responsibility, it is easy for managers to tip over into a blame-and-chastise pattern. When someone makes a mistake and a deadline is missed or a client gets upset, how do you respond?

    I saw an article that gives some examples from the cybersecurity world about how to build a culture that allows mistakes and forgives them. We all make mistakes, and we should strive to correct them while working to avoid repeating the same mistake. But we will make mistakes again in the future, so how do we deal with them?

    One of the challenges with building a strong culture that is productive is with management. Far too many people react poorly when things go wrong. I find this is a similar challenge to parenting, where we often struggle to let go of control and accept that mistakes will occur. We can also worry that we will be blamed for others’ mistakes and want to push our employees or children to avoid mistakes. Often our reactions are more fear-based, for ourselves or even for others’ safety. However, we can’t completely avoid things going wrong. It’s never worked for me, either at work or at home.

    There are plenty of articles on creating blameless cultures (one, two, and searches), most of which give reasoning why this works better and hints on what you can do. For many of us, these might feel like a dream we cannot chase. With some managers, the idea of even broaching the topic might be too scary. In those situations, I might try discussing the ideas with peers and perhaps implementing ideas with them, rather than trying to convince management.

    Ultimately culture requires support from those in charge. Management has to actually believe in a culture that tolerates and accepts mistakes, while still striving to reduce their occurrence. Everyone deserves to make mistakes and recover from them. We’d like to prevent repeat mistakes, but those will happen. My goal is to work to be better over time and expect others to do the same. While I might need to move someone to a new job or even let them go, it wouldn’t be because of making a few mistakes. It would be because of constant mistakes without making an effort to change their behavior and be better.

    Steve Jones

    Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.