|
| Featured Contents |
| Question of the Day |
|
| The Voice of the DBA |
he Journey to PostgreSQL (or anything) 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 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 was a risk. He was worried about moving to a new platform, despite all the reasons he had for doing so. 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 thought was 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. 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 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 in the process are the times when you can take advantage of an opportunity. Steve Jones - SSC Editor Join the debate, and respond to today's editorial on the forums |
|
| Featured Contents |
