Tag: work

  • A Spread of Vacation

    I’m off on vacation today.

    Which is a little weird as I just got back from a week long vacation in May, cruising with my family. Usually my trips for personal stuff get a little more spread out, but I’m slowly learning to relax and try to take advantage of the benefits and balance out my life better.

    I travel a good bit for work, taking 13 trips for work, 2 as a coach, and 1 vacation in the first half of 2026. It was a busy time, and for the first time in a quite a few years, my wife didn’t come on any of the work trips. That made it a hard six months for both of us.

    It’s not one’s fault, but we decided to do better, both to enjoy our lives more, but also to ensure we’re recharging and refreshing. Our changes for H2 are to take these trips together:

    • Jul 3-6 vacation
    • Jul 17-20 Day of Data Baton Rouge + 2 nights in New Orleans
    • Aug 10-18 – Cambridge for a week for me and then 5 days at the Fringe Festival in Edinburgh
    • Oct 10-19 – Cruise in Europe
    • July TBD – Camping for a long weekend
    • Sept TBD – a long weekend in the mountains of Colorado

    It’s a nice set of things to look forward to, which will break up my work periods with something coming every month to look forward to. With Thanksgiving and Christmas, this feels like a relatively relaxed H2 for me, which is great.

    I’m learning to relax and work a little less, enjoying life more. Many of you do this better than I do already, so thanks for all the comments, ideas about trips, and sharing about things you enjoy outside of work.

    This also might be the first time I get to Q4 without any extra vacation that I have to start burning without plans.

  • Spending Time in the Office

    I’ve visited a number of customers in the last few years who require most people to work in the office. Recently, I had the chance to go to Epic Systems, just outside Madison, WI, USA. They are a medical records software provider that was very reminiscent of Microsoft in some ways, and quite different in others. I published a blog with some pictures, so you can see how cool this office is in person.

    Epic has all their employees coming into the main office every day. They are flexible if you have needs, but the expectation is that employees go in every day. I believe this is also their policy, and culture, in various offices around the world.

    This is somewhat rare these days, but not unique. I’ve worked with one other (10,000 people) large company and a few small ones that have similar policies and expectations. Their offices aren’t as fun, but they are still neat. I love working at home, but I miss the camaraderie of being in an office. JD Edwards was probably my favorite place to work, and I enjoyed going into the office with friends, having lunch, going to movies together, and especially our Friday afternoon Nerf battles.

    I’m lucky in that I get to split my time. I’m at home much of the time, but I do go to the Redgate offices 4-5 weeks a year. Usually, I visit Cambridge, but I have visited the offices in Austin, Pasadena, Brisbane, and Amsterdam. I’ve yet to get to the Berlin office, but I’m hoping to fix that later this year or next.

    I know many tech professionals, and even those in other areas, prefer to work at home and can do their jobs effectively. We saw this during the pandemic, but I also think that many of us are missing something by not being in the same room with others. I find I build better bonds, better understand the way others communicate, and we can go back and forth with brainstorming, debate, discussions, and other collaborative actions more effectively. This can work remotely, but for many organizations that didn’t start this way, I feel like something is missing. We’re struggling to communicate and work as smoothly together.

    I don’t want to give up my ability to work at home, but I’d also hate to never visit an office either. I think I have a great balance, I enjoy both environments, and I appreciate the ability to change my location on a regular basis. However, if I got another job and had to go into the office every day, I’d be happy to do so (provided the commute is reasonable).

    Steve Jones

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

    Note, podcasts are only available for a limited time online.

  • Doing the Little Things

    I wrote a blog about sitting at LHR recently and watching planes take off. That’s been a fun thing for me to do when I’m stuck at the airport. I can see a plane roll down the runway every 35-45s during busy times. This time I was sitting by a window in the hotel, working and watching.

    There was a moment when I realized no planes were taking off. I looked and saw a vehicle rolling down the runway, and then realized there were two, one from each direction. It was an runway FOD inspection, looking for anything that might damage a plane.

    It’s a little thing that has to be done regularly at an airport.

    How many of you do little things in your job? Do you clean up old logs/backups/ETL source files? Do you double-check security for old/expired accounts, unused databases, forgotten audits/traces, etc.? Maybe do you check the status of patches across your database estate? Is there something else you should do semi-regularly?

    I’ve seen many people (including myself) lose track of things over time because there are so many. My phone (or pager) has rung so many times because a system ran out of disk space due to old files that accumulated over time. Those log files might not be be large, but after years the size can add up. And they’ll fill up a disk at night, not during working hours.

    This is where AI might help. I’ve written many little scripts that helped me clean things, but they were often brittle and focused on a specific task. Generalizing them would take too much effort, and might not even be possible. After all, sometimes I’m not even sure what the general case would be when building the utility.

    AI coding agents can help us in this space. Ask an AI for a script to remove old backup files, leaving the last few. Perhaps you want to look for unused accounts. You can ask an AI to setup an audit to scan for login times (script one) and then process the results to get the last login time for each account (script two). The action might be to disable accounts that haven’t logged in for six months (script three). Set these scripts to run ad hoc or on a schedule as needed. Just be sure you have a calendar entry to remind you to check the results.

    Each of these scripts isn’t that complex, but across many systems, perhaps with slightly different requirements and situations, you might not have time to adjust each script or even build them. However, if you can think about a small utility, an AI can help you build it. Just be sure you also ask the AI to set up tests to ensure the script works as intended. This is especially important since you’ll likely be asking the AI to refactor or change the code and want to prevent regression bugs.

    Doing the little things at work can eat up a lot of time, but building small utilities can help you can ensure that your systems run smoothly. And ensure you still get home in time for dinner.

    Steve Jones

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

    Note, podcasts are only available for a limited time online.

  • Whiling away an afternoon, thinking

    I come to Heathrow often. Today is likely somewhere close to 60 trips to this airport in my lifetime. After over 19 years of working with Redgate (plus a trip in college), this is the airport I’ve visited most outside of Denver (my home).

    This is the view outside my hotel window. You can see an A320 (or a Boeing 737) taking off. This is a good sized plane I fly all over the US. It is about 35 meters (100ft) wide and carries 150-180 people.

    As it took off beside the A380 pulling into the terminal, it looked like a toy plane. Those things are massive.

    20260317_151547

    I’ve stayed here a few times after landing to try and get some work done, and to check in early to take a nap. I landed at 10am after flying all night, and I could use some rest. Rather than heading into London and getting stuck sitting in a restaurant waiting to check in, I booked a room here. Already had a nap and ready to work.

    Thinking Time

    This is good thinking time, which is sometimes rare to get. Years ago on one of our multi-times-a-week SQL Server Central calls, Andy told me that he needed time to think about his work as a DBA and manager of others. Time to just consider how things are going, why things are going well or not, and which direction to go.

    Time just thinking about a topic.

    It has stuck with me all these years that time to just think is important, and it helps me clarify how I view things.

    It’s often how I get editorials written. Turning vague ideas into something concrete. I’ll look at a note I’ve made or re-read something and think about it. When inspiration strikes, I’ll start writing.

    Today I was thinking, watching planes take off when I realized I hadn’t seen a plane in awhile. Normally they take off around every 45s at LHR. Then I saw this little vehicle doing down the runway, something I’ve never seem.

    20260317_151301

    I watched for a few minutes and realized there was another one coming the other way. They met in the middle and circled a few times before leaving the runway.

    20260317_151335

    I’m sure this is some FOD (Foreign Object Detection) process looking for pieces that might have fallen off planes (yikes) or vehicles, or somewhere. A pilot friend said that this is something that is done in the military, sometimes by grunts walking the runway looking for something that might get pulled into a jet engine.

    In any case, it was something new and unusual and inspired me.

    I don’t know that everyone needs thinking time, but if you manage or lead or are trying to develop strategy, I do believe you need some quiet thinking time when you’re not really getting anything done, but just thinking about work.

    Glad that I took the time today and grateful to have the opportunity.

    Now back to writing about AI and other things impacting the data professional.