The Book of Redgate: Don’t be an a**hole

Posted on October 17, 2025 by way0utwest

This was one of the original values:

2025-09_line0001

The facing page has this text: No matter how smart you are, or how good you are at narrowly defined tasks, there is no room for you here if you’re an asshole.

This is a similar value to that I’ve seen at a few companies, such as Google’s: Don’t be evil.

I think this is one of those values that has held true over time. We try to be  professional and respectful with each other. We don’t want to offend others or treat them poorly. The Oxford dictionary has this definition: “a stupid, irritating, or contemptible person.”

I probably stretch the limit of this at times, but I’m not trying to be out of balance with my pressure on others to do better work alongside my respect for them and my desire to be positive. I might not always get the balance right, but I am willing to apologize if I’ve stepped over the line.

I don’t think of anyone at Redgate as being an a**hole, which is a nice feeling. Hopefully, I’m not one.

I have a copy of the Book of Redgate from 2010. This was a book we produced internally about the company after 10 years in existence. At that time, I’d been there for about 3 years, and it was interesting to learn a some things about the company. This series of posts looks back at the Book of Redgate 15 years later.

Posted in Blog | Tagged , , | 4 Comments

The Journey to PostgreSQL (or anything)

Posted on October 17, 2025 by way0utwest

Most of you reading this work in technology, and I assume that you’ve had to learn something new on the job. Technology is constantly evolving, even on our existing platforms. On top of that, we are regularly given tasks that are outside of our current skill sets. Maybe not far outside, but to meet the changing demands of our jobs, we need to learn new things.

I ran across an interesting post (on a new site) from Brent Ozar. I think that guy writes as much as me, but he wrote this one: Why I Started Using Postgres (And You Might Too). It’s a little provocative, but there are good posts on the site about things Brent learned in PostgreSQL. I won’t go into whether learning PostgreSQL is a good idea.

The thing that struck me in this post is that Brent knew that this move was a risk. He was worried about moving to a new platform, despite all the reasons he had for doing making the change. I would bet a lot of us are in similar situations. It might not be PostgreSQL we are being asked to learn, but it could be Fabric, Databricks, Python, PowerShell, CosmosDB, or whatever other thing someone in our organization thinks is cool.

The best sentence in here is this: “I gambled that I’d be able to learn how to do performance tuning quickly enough, …, in time to head off issues.” That’s the attitude I’ve often had in my career when I get requests to do something new.

I’m willing to bet on myself.

You should be willing to do so as well. Not bet on me, but on yourself. I know you don’t want to work 80 hours a week to learn, or get stuck trying to solve problems every weekend with new tech. However, I hope you are willing to do that for a week or one weekend. You’re willing to do some reading at night or experimenting during lunch in order to make something work.

You’re going to have tough times. You’re going to question if you can make something work. Getting comfortable with being uncomfortable (for short periods) is how we grow and learn. It’s how we take leaps forward.

It’s how we take advantage of opportunities that are in front of us.

There are always opportunities to make a difference, to effect change, to build something you are proud of or that your organization values. Those stressful times when you drive to make something new succeed and have to learn a new skill in the process, these are the times when you can take advantage of an opportunity.

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

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

Posted in Editorial | Tagged | Comments Off on The Journey to PostgreSQL (or anything)

A Broken Copilot Query

Posted on October 16, 2025 by way0utwest

I was testing the new SSMS (v22 Preview 3) with Copilot and ran into an interesting issue.

This is part of a series of experiments with AI systems.

My Query

I was working on something unrelated and tried this prompt, which should have saved me a few minutes from looking on MSLearn.

2025-10_0168

As you can see, I get a nice list of things. However, then this happened.

 

This kept going. I gave it a minute, then opened my screen recorder (which is close to a minute) and started recording.

After capturing this, I stopped the query. Things seem to work OK, but this is definitely something that concerns me about agents and letting them go. I don’t know if this was a stuck process, if this was consuming compute or tokens, but it was certainly an issue.

Posted in Blog | Tagged , , | 2 Comments

We Should Demand Better

Posted on October 15, 2025 by way0utwest

I ran across an interesting open letter. Most of these are from individuals, often complaining or lamenting on the way something in the world works, or maybe doesn’t work.

This latest letter was from the Chief InfoSec Officer at JPMorganChase, a large worldwide bank. This open letter was written to the software suppliers looking to do business with JPMorganChase, especially those in the SaaS area (Software as a Service). The letter opens by noting that SaaS is enabling cyber attackers and asks for three things: prioritize security over features, modernize security architecture, and work with security collaboratively to prevent abuse of connected systems.

It’s a good letter. It talks about the problems at a high level, but is specific enough to recognize problems. Software is often delivered as a SaaS type application, even when there might be local components. For example, I lament Postman working this way, as it now seems to now require me to be connected in order to work. That’s something I learned while trying to get work done on an airplane, and I couldn’t get to any of my queries as I didn’t have wi-fi, despite the application running locally on my laptop.

The threat of more attackers is amplified by the connectedness of new systems, new agents, and new protocols that allow a breach to escalate deeply inside systems. This is something we’ve faced in the past, but not at the scale that we face it today. Automation has become embedded in the computing world, not just inside organizations, but also inside hacking organizations. Malicious actors can and do use scripted attacks at a rate that we haven’t experienced in the past.

I wish that most people purchasing software would prioritize security when making a decision, but often price and expediency outweigh anything else. While I do see many companies asking for security information, too often the requests are at high levels, and vendors can word their answers in a way to satisfy the screen without actually improving their own security coding and architecture.

I do think the authorization and authentication of users is improving, so I have hope that more patterns and frameworks are published and widely used, and we’ll see more consistent security throughout software. Now, if we can just ensure the authors of those platforms do a good job of security, we might see the request from JPMorganChase come true.

Steve Jones

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

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

Posted in Editorial | Tagged | 2 Comments