Voice of the DBA
info_outline Words vs DataVoice of the DBA
info_outline Data DebtVoice of the DBA
info_outline Creating vs. MaintainingVoice 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 HumansVoice 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_outline The AI Budget AssistantVoice of the DBA
info_outline The Types of ChangesVoice of the DBA
info_outline The Managed Cloud Database OptionsVoice of the DBA
info_outline Simple(r) CoffeeVoice of the DBA
Starbucks has too many order combinations. about the challenges for their new CEO notes there are over 170,000 combinations of things customers can order. As someone who has visited a store often and stood behind someone placing an order, that sounds like an accurate number. Sometimes I hear people order things to drink that I had no idea were even possible. When there are too many choices, sometimes there can be a delay as the person tries to process the information and make a decision. Some people can't make a decision. Others enjoy the variety and keep making different decisions each time....
info_outlineI was watching a video called Microservices are Technical Debt. In it, the person being interviewed said that a lot of people really have a distributed monolith. That caught my eye since I've worked with a number of customers who are trying to adopt microservice architectures for their applications. I think this is less a performance/scaling choice than a reworking of their software development teams, and I'm not sure they will end up with a better system.
What is a distributed monolith? I am not an expert, but this appears to be a place where all the services still depend on each other. For example, I might have a service getting user profile info that an app calls, with another service getting previous orders, and a third service that returns inventory. In a monolith, if any of these are down, the others don't work. In a distributed monolith, these might be built independently, but perhaps the core app/web page still requires all these to be working to show the user something.
Read the rest of Distributed Monoliths