Voice of the DBA

Steve Jones

A series of episodes that look at databases and the world from a data professional's viewpoint. Written and recorded by Steve Jones, editor of SQLServerCentral and The Voice of the DBA.

  1. vor 1 Tag

    Follow Your Hunch

    For a while, I kept seeing that the cost of writing code was approaching zero. So many people felt that with an AI LLM, the costs would go way down to produce software. I'm not sure that's true. In fact, some companies are finding they spend more on AI tokens than salaries. However, the ability to produce more code, experiment with ideas, or generate proof of concepts has gone up. Whether it's worth the cost or not depends on the engineer, but some organizations are finding that they can try more things than they would ever had time to try in the past. The time of engineers was the constraint, and if you can afford the cost, AI LLMs can relieve that time pressure. Read the rest of Follow Your Hunch

    2 Min.
  2. You Might Also Like: On Purpose with Jay Shetty

    vor 1 Tag ·  Bonus

    You Might Also Like: On Purpose with Jay Shetty

    Introducing Dr. Ramani: If You're Thinking About Going No Contact With a Family Member - Listen to THIS (How to Know If It's Time To Walk Away) from On Purpose with Jay Shetty. Follow the show: On Purpose with Jay Shetty Some relationships leave us questioning whether love is enough to stay. In this conversation, Jay sits down with Dr. Ramani to explore the painful reality of family estrangement and the growing number of people considering no contact with those closest to them. Together, they unpack the difference between self-protection and punishment, why guilt often accompanies healthy boundaries, and how years of unresolved hurt can lead someone to step away from a relationship they once fought hard to save. Rather than offering simple answers, this episode invites a deeper reflection on safety, repair, accountability, and healing. It challenges the belief that family ties should come at the expense of your well-being and reminds us that choosing yourself is rarely easy. Whether you're navigating a difficult relationship, supporting someone who is, or trying to understand a loved one's decision, this conversation offers compassion, clarity, and the reassurance that healing doesn't always look the way we expect. In this episode you'll learn: How to Know When No Contact Is Necessary How to Stop Abandoning Yourself for Family How to Recognize When Repair Isn’t Working How to Handle Guilt After Going No Contact How to Protect Your Peace Around Toxic Relatives How to Navigate Family Pressure and Backlash How to Choose Self-Protection Over Self-Betrayal Not every relationship is meant to be kept at the cost of your peace. Sometimes healing means repairing a connection, and sometimes it means creating distance from what continues to hurt you. With Love and Gratitude, Jay Shetty JAY’S DAILY WISDOM DELIVERED STRAIGHT TO YOUR INBOX Join 900,000+ readers discovering how small daily shifts create big life change with my free newsletter. Subscribe https://news.jayshetty.me/subscribe   Check out our Apple subscription to unlock bonus content of On Purpose! https://lnk.to/JayShettyPodcast  What We Discuss: 00:00 Intro 01:29 What Does Going No Contact Really Mean? 06:24 When No Contact Becomes Your Only Option  08:10 Can a Broken Relationship Be Repaired? 11:40 The Most Common Reasons People Go No Contact 14:48 It's Not the Mistake, It's the Repair 17:01 Pay Attention to Your Why 21:58 Detaching from a Harmful Relationship 26:29 You Have to Do What Feels Right for You 30:12 When Family Requires Self-Abandonment 35:37 The Weight of Internal Shame 36:44 The Hidden Cost of Always Keeping the Peace 42:26 When Someone Cuts You Off Without Explanation 44:13 When Is It Time to Cut Off Contact? 48:01 But They're Family... 53:16 Building Your Chosen Family 55:05 No Contact vs. A Falling Out 55:54 The Silent Treatment Is a Form of Emotional Aggression 58:01 Are We Getting Worse at Repairing Relationships? 01:02:38 The Relief of Finally Deciding to Go No Contact  01:04:09 How to Repair a Relationship After Being Cut Off 01:05:37 Forgiveness Isn't Always Healthy 01:08:26 The Challenges of Trying to Heal Trauma 01:11:29 Why Some Parents Don't Understand Estrangement 01:13:13 Handling Family Backlash After Going No Contact 01:15:12 When a Parent Is Both Supportive and Harmful 01:17:54 When Breaking No Contact Is Worth Considering 01:19:26 Can a Narcissistic Parent Change? 01:22:16 Should You Invite an Estranged Family Member to Your Wedding?  Episode Resources: Website | https://doctor-ramani.com/  YouTube | https://www.youtube.com/@DoctorRamani  Facebook | https://www.facebook.com/doctorramani  Instagram | https://www.instagram.com/doctorramani/  LinkedIn | https://www.linkedin.com/in/ramani-durvasula-4132067  TikTok | https://www.tiktok.com/@doctorramani  X | https://x.com/DoctorRamani See omnystudio.com/listener for privacy information. DISCLAIMER: Please note, this is an independent podcast episode not affiliated with, endorsed by, or produced in conjunction with the host podcast feed or any of its media entities. The views and opinions expressed in this episode are solely those of the creators and guests. For any concerns, please reach out to team@podroll.fm.

  3. vor 3 Tagen

    The Slow Growing Problems

    Both as a DBA and developer, I've had plenty of immediate, this-is-broken, fix-it-quickly issues. Usually, I, or someone else, wrote some bad code and somehow got it deployed. I mean, I do test things, and I would (probably) never change code after I'd tested it to fix that one little annoying thing, like the formatting. I'd (almost) never do that, and I'm sure you wouldn't either. Yet somehow bugs slip in at times. Those are the acute issues, and they can be hard to fix at times, but often we can reproduce the problem in development and build a fix. Sometimes we even spot the issue quickly and just fix it in production. I'm sure you never do that, but I have had that experience myself a few times. Read the rest of The Slow Growing Problems

    3 Min.

  4. 7. Juni

    Would You Retire Rather Than ...

    Bjarne Stroustrup is the creator of C++. I read a few of his books and alternately loved what he'd done and hated having to write C++ code in university and at a few jobs. I found it tedious and hard, though arguably better than C once you had a decent set of classes structured. BTW, I love his website, the basic text view of the world, which is how I have built a few sites on my own. I caught an interview with him and this short response on AI and coding. He had this quote: "Senior developers are already retiring rather than deal with it." He doesn't love the results from AI, which is fine. And it's not what I want to talk about today. Read the rest of Would You Retire Rather Than ...

    3 Min.

  5. 4. Juni

    The Data Model Matters

    I ran across a statement that seems exciting to me as someone that has written a lot of code in their career. It said: "Many of the "modern" software practices of the last decade were early adaptations to this shift, even if we didn't articulate them that way. Immutable infrastructure. Stateless services. Containers. Blue-green deployments. Infrastructure as code. These ideas all share a common premise: never fix a running thing. Replace it." These are a few sentences in this piece on the death and rebirth of programming. That's how a lot of software developers have viewed the world during the last decade and we've seen a lot of software advances in that time. The very successful developers and teams, who often speak at conferences and publish papers have adopted many of these practices. Serverless, containers, lots of tests allowing continuous deployment of new objects into complex environments that scale to levels many of us never thought possible. These are the very high performances talked about in the State of DevOps report every year. Read the rest of The Data Model Matters

    3 Min.

  6. 2. Juni

    Over of Under Provisioned

    Lots of people move to the cloud; it's common. In fact, it's very common to hear customers who are being asked to migrate their workloads to a cloud vendor for a variety of reasons. You might not agree, but often there is some reason to move to the cloud. Sometimes it's even moving from one cloud to another, just because one of the big three (AWS, Azure, GCP) seems more attractive this year than the one from last year. When you move, do you size your system for the peak? 80% of the peak? Perhaps there is another goal for which you design. Do you worry about ever being under-provisioned and letting customers have a slower system? Or do you ensure you never hit the peak, which increases costs? Read the rest of Over or Under Provisioned

    3 Min.

  7. 21. Mai

    The New Software Team

    One of the things I used to emphasize in talks about DevOps is that no modern software of any significance is built by one person. Everything takes a team, so the foundation of version control becomes extremely important. We need a way to coordinate work across multiple individuals and communicate what changes are being made. This requires a strong foundation, and that starts with version control. In 2026, that hasn't changed, but what has changed is the makeup of the team. No longer do I need a bunch of humans. In today's world, with extremely powerful AI LLMs, we can have a team of AI agents that write code, often at a pace far exceeding that of human teams. However, they still need to coordinate and communicate and ensure their changes mesh together.  Read the rest of The New Software Team

    3 Min.

  8. 19. Mai

    Limit the Blast Radius

    You still need DBAs (that know how to back up systems and test restores). If you think you don't, or if you manager does, then perhaps they ought to read this piece on how an AI agent deleted a production database. This wasn't the case of an agent just running around with sysadmin access to all resources, or a lack of tests that allowed bad code to flow through a CI/CD process. This was a system design that had a hole in it. An API call to change infrastructure that could change both staging and production. Not something an AI set up, but humans did. A hole from both PocketOS and the API vendor that allowed the AI agent to make the same type of mistake we've seen humans make. A mistake of not double checking, not verifying, not following the rules of getting a second set of eyes, even a second set of virtual eyes, on the code that could drop resources. Read the rest of Limit the Blast Radius

    4 Min.
Alle anzeigen (101)

Info

A series of episodes that look at databases and the world from a data professional's viewpoint. Written and recorded by Steve Jones, editor of SQLServerCentral and The Voice of the DBA.

Informationen

  • Erstellt von
    Steve Jones
  • Jahre aktiv
    2007 - 2026
  • Folgen
    101
  • Bewertung
    Unbedenklich
  • Copyright
    © Copyright 2020 Steve Jones
  • Sendungswebsite
    Voice of the DBA

Das gefällt dir vielleicht auch