How Much Linux Do You Need?
Voice of the DBA
info_outline
The End of Azure Data Studio
Voice of the DBA
I don't know how many of you will be disappointed or impacted by this, but Azure Data Studio (ADS) is being retired, as of 6 Feb, 2024. It will be supported for a little over a year, until 28 Feb, 2026. On one hand I'm not surprised, and on the other, I'm a little shocked by this. I have written , and shown how things work, as well as pointed out a number of things that don't work well in the product or its extensions. These pieces have gotten a number of reads, and people have commented on them, so I wonder if there are a lot of you that are upset by this. Is this going to change the way you...
info_outline
Extended Event Comfort
Voice of the DBA
info_outline
Unreliable Narrators
Voice of the DBA
info_outline
Building a Data Center
Voice of the DBA
info_outline
Words vs Data
Voice of the DBA
info_outline
Data Debt
Voice of the DBA
info_outline
Creating vs. Maintaining
Voice of the DBA
If your job as a developer or DBA has been like mine, it's a constant stream of requests to change something, often without enough information and short deadlines that create a bit of stress. There's always more work to be done, and while it might be a great job, you're often trying to finish something quickly enough to get to the next thing. In this mode, how often do you think about creating (or modifying) the thing you're working on for today vs maintaining it for tomorrow. In other words, do you consider how easily your work can be understood, is documented, is designed to allow for...
info_outline
The Era of Cloned Humans
Voice of the DBA
info_outline
Can You Become a More Productive Engineer?
Voice of the DBA
The short answer is of course, most of us can learn and improve our skills to become better developers, engineers, DBAs, etc. While we might not be able to become the 10x engineer that many aspire to be, we can certainly become a better employee inside of an organization. There's a piece on becoming a more effective engineer, which is actually titled . It a piece from an engineer that started with a : The text was:You can either complain and pontificate on Twitter on how the tech industry *should* ideally work, or you can learn how your org *really* works and what’s rewarded, and optimize...
info_outlineWhen I was younger, I had a variety of jobs, but in most of the positions I had to work hard for stretches. Really hard, as in more than 8 hours a day or 40 hours a week. Often as I was starting a new position, it took some time for me to develop some understanding, some skill, and some muscle memory. In some jobs, especially in restaurants, I also had to build the physical skills to be on my feet for many hours.
In technology, I've often found myself unsure of how to approach a new position, aware I had knowledge gaps about how things worked, and often, I was naïve or ignorant of some piece of technology my employer used. Even at jobs where I started as a developer or DBA on a known platform (ASP or SQL Server), I sometimes encountered some aspects of the technology that I hadn't used in the past (like clustering).
Read the rest of Learning to Grind