Voice of the DBA

Tag: syndicated

  • A New Word: agnosthesia

    agnosthesia – n. the state of now knowing how you really feel about something, which forces you to sift through clues hidden in your own behavior, as if you were some other person – noticing a twist of acid in your voice, an obscene amount of effort you put into something trifling, or an inexplicable weight on your shoulders that makes it difficult to get out of bed..

    There are a lot of times I’m not sure how I really feel about something. Whether it’s something in the state of the world (politics, government, culture), or it’s a technical item. There are many cases where I’m just not sure. I have to stop and think outside myself, and often think about how I would react if things were structured one way vs. another.

    In the tech world, I’ve often been a little uncomfortable with EULAs and software licensing, but I also don’t quite know if I would abandon most copyright/IP/patent/ etc. I’m not sure if I think the world (or my life/career) would be better or worse.

    Sometimes it’s smaller, like the way someone else tries to teach me a topic or present an idea, or perhaps the way that an event is organized. I don’t pretend that I know better, and try to remember that I might go about the item/task/etc. differently, but I don’t know if I would. It’s easy to react, and much harder to make decisions and act without the benefit of hindsight.

    I do use agnothesia, trying to step outside of my own emotions and feelings and look at what a situation or idea changes in me, as if I’m studying myself. I don’t often come to any resolution or learn anything, but it helps me to remember I’m just one person, part of a larger community and society, and life can be hard when you don’t have all the answers.

    Or as I feel, many at all.

    From the Dictionary of Obscure Sorrows

  • Skipping SQL Bits 2024

    SQL Bits has been my favorite data platform event for years. Both it and the PASS Data Community Summit hold special places in my heard and I enjoy going, but the community, casual feel of SQL Bits is just a bit more fun for me.

    I’m sad to be skipping SQL Bits 2024, but the timing doesn’t work for me. I saw Brent was also skipping (for different reasons), and decided to state my own reasons, since I have often attended. This was also Brent’s most commented on post in 2023, so I’m hoping to start the year off right on this blog Winking smile

    Managing Workload

    In 2023, I had 32 trips. By mid Oct, I was a bit worn out and struggling. I just wanted trips to be over with and get back home. Between my last pre-Summit event in early Nov and the PASS Data Community Summit, I was home for 12 days in a row. I hadn’t done that since May 2023.

    As a result, I’m trying to be more careful with travel workload in 2024. My boss and I meet every week or two and we review the schedule for the next couple months to manage things.

    I also coach volleyball in Q1 and I try not to miss events or practices so I try to limit my travel.

    Scheduling

    While I local SQL Bits, I’ve missed a number over the years because of scheduling conflicts. Their March events have conflicted with other events in my life, often outside of work. I preferred when they had an Aug/Sept event as well.

    This March, I am committed in March from the 9-11th, and then have to be in Atlanta on the 13th-14th. I have the next week at home, and I could potentially go to the UK on the 18th, but I have to be back on the 24th to coach an event in Denver. That means leaving Sat from the UK at the latest, and leaving SQL Bits on Friday. I’ve done that before, but I have to miss some practices in Denver that week and it’s not worth it just to indulge myself in another event.

    I also have to be back in the UK in April and travel the in between week in the US, so I’m thinking that this is a time when I could make the schedule work, but it would impact my managing my workload.

    Skipping a Year

    I’ve been blessed and honored to speak at many events. While I would like to go back and enjoy SQL Bits, I also want to make room for others and let them enjoy the experience. Missing a year is OK, and I’ll look forward to 2025 (and cross my fingers that the date doesn’t have workload or scheduling impact).

    If you’re anywhere near London or can get there in March, attend the event yourself. It’s fantastic and a lot of fun.

  • Changing the Origin in Git–#SQLNewBlogger

    I needed to show a customer how to migrate from Azure DevOps to GitHub recently, and to smooth this process, we needed to repoint the origin remote.

    Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers. You can see all posts on Git as well.

    Changing the Remote

    When you want to see remotes, you run this code:

    git remote –v

    As you can see, I have my origin pointed to Azure DevOps..

    2023-12-19 11_46_54-cmd

    Now, I can delete and add back the origin remote if I want, but there is an easier way. I’ll use the set-url parameter with this code:

    git remote set-url origin https://github.com/way0utwest/DatabaseDevOpsMS.git

    This points the origin to my new remote in GitHub. Once I run this, I’ll set the branch and push, as the GitHub repo is empty. This pushes everything to GitHub and voila, I’ve got code there.

    2023-12-19 11_48_22-cmd

    You can see this online

    2023-12-19 11_35_59-way0utwest_DatabaseDevOpsMS — Mozilla Firefox

    SQL New Blogger

    I had to write this up in more detail for a customer as documentation. You might do this at work for someone, but I grabbed this focused, small piece of this and created my own blog, reusing a few screenshots.

    Note: Don’t reuse screenshots of company assets. Recreate this in your own space.

    This took me only about 5 minutes to write up after the other work was done. You could easily do that.

  • Career Plan for 2024

    It’s a holiday today, but I’m dropping this as I spent last week working on it. I wrote about having a career plan on Friday, with a few notes in there on how I was viewing my career in 2024. This post will cover a little more of my thoughts on the future (for me) and my plan.

    Note: I’m mid-50s, and my career is closer to being over than beginning, so take this with a grain of salt if you’re in your 40s or younger.

    Thoughts on My Career in 2024

    I tried goals for a number of years, but those are hard for me to work on through a year for a few reasons. One is that my view in Dec/Jan is not always one that continues through the year, at least not with my job. Second, I start to get focused on the goals and it creates stress and pressure that I don’t need. Rather that improving in an area, I’m driven by the goal.

    I don’t like that.

    I also find my career is evolving more rapidly in the 2020s in the past, with each year moving me in new directions that are tangentially related, but hard for me to build goals in since both me and my employer are learning new ways to use my talents throughout the year.

    I’m closer to the end of my career, with roughly 10 years—ish left. I’m also doing more work with customers as an architect and advisor rather than a marketer. I find my time is spent more with sales than marketing or engineering, and I both need new skills there, but I also have to focus my time in different areas.

    Lastly, a portion of my job is still journalism, running SQL Server Central, so I need to remain aware and learning about the state of the data professional in the world.

    With that in mind, I’m setting plans in motion to help me in those areas, without goals. Just a direction. I think that’s a new approach for me, where I look to find time to grow in a direction, but without the pressure of a goal. If I have to skip some sessions or alter the direction, I can do that easier by altering the direction rather than trying to abandon one goal and find a new one.

    Think of this as finding a new route while on a road trip rather than being driven by the time of arrival.

    The 2024 Plan

    Where do I want to be in a year? Here are the things that come to mind:

    • Produce a specific content on Redgate technical issues or architecture recommendations that I upload to our Seismic site.
    • Learn how to use all the Flyway commands well from the CLI so I can make good recommendations for flow and using them
    • Learn to use static code analysis tools and create custom rules in a pipeline
    • Be comfortable enough with AI to use it every week

    That might be too much, but the first 3 are really related to my job, so I’ll be getting career growth out of them and I can spend some of my time at work focusing in this direction. These are areas I’m interested in and having a direction to produce these learnings as documents shared within the company will force me to learn them a bit better.

    The last one about AI is not because I think AI is great, but because I’m still unsure of how or where to use it. I have some coursework on AI from Microsoft that I’m going to go through and try to better understand what’s happening, what’s involved with training, and how I can prompt better. I think this will be a good tool at some point, if not for writing code, perhaps for other things.

    That’s my plan, now, what’s yours?