Tag: career

  • Degree Apprenticeships

    I enjoyed my time in college, and I learned a great deal. While I do think that the time helped me grow, I also recognize that I was always a good student and the cost of my working through that degree was far below what today’s degrees cost at many universities (even accounting for inflation). What’s more, I worked most of the time I was at university to pay for my living expenses.

    These days I am torn on the value of a degree, especially when the total cost can easily exceed USD$50,000. Even more concerning is the fact that many people have to drop out with substantial debt and no degree. That’s the worst of both worlds. While it’s easy to point the finger at people for not finishing or working harder, it ignores the challenges of the real world, which can throw curve balls at all of us.

    For a lot of my college time, I had to work to support myself because I didn’t have enough scholarship funding, and I was worried about loans. I was worried about post-college, and in the 80s, I was able to work 30+ hours a week and earn enough to pay rent and buy food. Later in my time, I was able to secure an internship that paid me, which was nice. Then I wasn’t spending 80+ hours a week trying to learn and support myself.

    I saw a note recently about degree apprenticeships from Purple Frog Systems. The idea is that someone is part-time in university while working for an employer. This might require more than 40 hours a week of combined work, but I like the idea of someone learning about both the academic and practical views of an industry and getting mentorship from both co-workers and academics.

    While many of us who work for an organization might get tuition assistance, it’s not always easy to work out school and work. Managers may or may not work with you, and there isn’t really continuous support to help you complete your degree. The quality of your manager often determines if this works. However, the bigger issue is that many people struggle to find jobs in the first place and not many organizations I’ve worked for have any programs to find people who might be suited for an apprenticeship program.

    I don’t that our industry, or many industries, really need to require degrees. That being said, I do think there are things universities teach well, and they give a good perspective on a variety of topics. Employers can benefit from motivated individuals who learn their business, learn different skills in school, and bring about energy and fresh perspectives. Plus, employers learn how to train and grow new people at a lower cost. We all struggle to hire well and train people to be effective quickly. Working with interns or apprentices is a good way to embed regular mentorship and training into the culture of your company. That’s something everyone can benefit from.

    I hope to see more apprenticeships in the future, not just in technology (or marketing as in the post), but in a variety of industries. I don’t know if we will, but I do think this might help us get better at finding and training new staff.

    Steve Jones

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

  • Be Valuable, Not Critical

    I find there to be a lot of value in actively managing your career. I’ve been a technical individual contributor, a manager, a business owner, and a cross-team supporter in my various positions. Each one has challenges, and in each case, I’ve found ways to build a better career position that not only suits me but makes my life more enjoyable. I hope to inspire others to do the same, and this is part of a series of editorials based on advice I’ve read from Raylene Yung (Facebook and Stripe) on your engineering career.

    One of the first things I read was that engineers ought to aim to be valuable, but not critical. This is similar to the advice from others that good tech staff try to work themselves out of a job by documenting and sharing everything. Not everyone is a great, or even good, engineer, so I understand why it can be scary to share knowledge. However, many of us find ourselves doing something that few, or no one else, does anyway.

    Viewing this as being valuable is helpful. However, if you are critical and the only one that can do something, you might find yourself on-call, or under a lot of pressure from management when something goes wrong. Instead, if you have the detailed knowledge, but you’ve shared that in some way, you can be the consultant or advisor rather than the person everyone expects to be doing the work in a crisis. This is a mistake I’ve made many times in my career.

    You want to provide value in some way to your organization, but not be a single point of failure. In the short term, your manager might feel you can’t be replaced, but often I listen to managers talking about their plans to find a way to remove those critical people who don’t want to share their knowledge from that position. Usually, removal also is accompanied by termination.

    Good engineers find ways to be valuable, partially by gathering tribal knowledge, partially by developing solutions, and partially by sharing with others. Document, explain, train, and assist others, but ensure that if you want to go on vacation, sleep all night, or celebrate life away from work, you aren’t the critical person during a crisis or even normal, daily work.

    Steve Jones

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

  • Declining Work for Mental Health

    This year has been a busy one for me. I had 30 trips on airplanes away from home and around 100 nights not in my own bed. It’s been quite a year, and a little overloaded. There have been a few months were I traveled little, but more than a few where I was gone more than I was home. I spent 19 nights away from home in September.

    A few weeks back, I realized that I had another long trip coming up in October (9 days) and the PASS Data Community Summit in November. My body is a little worn out, but my mind is also distracted and struggling to focus. I recognized the beginnings of burnout when I realized that I was slightly dreading the Summit trip. While I want to see friends and catch up, I wasn’t looking for a long trip.

    On the spur of the moment, actually while sitting in an airport and waiting for a flight, I sent a note to the SQL Saturday Oregon organizers asking them to withdraw my speaking submission and not select me. I felt bad for doing so as I try not to create work for others or submit to events without the intention to go, but the extra 2 days in Seattle would make lift hard, and I thought this was the best choice for my mental health. I also chatted with my boss a bit about some work opportunities that were coming up and decided to decline a few other things, as well as skip conference submissions in Q1 2024.

    I’m not burned out, but I do recognize that I’m overloading my body a bit. Physically it’s a bit worn out and I can see that in my frequency and effort at the gym. Mentally I’m slightly dropping the ball on a few things, working slower than I often do because I find myself slightly distracted and looking for more breaks.

    One of the big learnings for me over the pandemic was that I need to ensure I take care of myself and treat myself as I’d treat someone else in similar circumstances. I’ve had coworkers and friends struggle at times in life, where I’ve made an effort to work more and help them work less. I need to remember that for myself and ensure I can lean on others where needed. Redgate is an amazing employer and everyone is willing to flex with each other to ensure work gets re-distributed or we move deadlines. My manager and I have discussed this, and we are monitoring my workload moving forward in our regular meetings.

    One of the best things I’ve learned over the years is to say no. I say no a lot to various queries on my time. Often when I feel I can’t deliver on time. This year I was looking forward to these opportunities, perhaps a bit too much, and ran myself down a bit with over-excitement. I recognized that and made an effort to take steps to help myself before I burned out or started missing commitments.

    The last month (and half of the next one) has been a bit rough, but I’ve mentally prepared myself for the work, and seeing relief coming in a couple of weeks is helpful. I’ve learned a bit more about myself this year, especially in relation to my slightly changing job and hopefully, I’ll do a better job managing myself next year (or my boss will).

    Learning to balance work and life is important. Remembering that life, family, friends, hobbies, faith, etc. are more valuable than work, and we need to ensure we don’t overwork ourselves makes us better employees and better people. Any of us can get overloaded in the short term, but don’t let that become an accepted part of your life. Your employer may push, but learn to push back and protect your physical and mental health.

    Steve Jones

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

  • SQL Saturday Boston 2023 Slide Decks

    Thanks to everyone who came to my sessions at SQL Saturday Boston 2023. I’ve added the decks to the schedule, so you can click my session and will see the download there. You can see this below, and all speakers can edit their sessions and upload the deck. See the download below:

    2023-10-14 13_43_08-SQL Saturday Boston 2023 (#1046)

    I’ve also copied the links here for slides:

    For the first session, Architecting Zero Downtime Database Deployments, there is also a GitHub repo here. Clone the repo down (or fork) and you can follow the sessions along. The repo is at: https://github.com/way0utwest/ZeroDowntime

    In here, there are a few folders, as shown here:

    2023-10-14 13_45_44-way0utwest_ZeroDowntime_ Code for my zero downtime presentation

    The two items from the session are the DBClient, which is a Visual Studio 2019 project, and the SQL folder, which has all the setup (and teardown code). Each script is numbered, and you can run them in order. There are also some comments in each for when to flip feature flags.

    If you find issues, please submit an issue in the repo.