Voice of the DBA

Steve Jones
  • 4,9 (9)
  • TECHNOLOGIES
  • DEUX FOIS PAR SEMAINE
Voice of the DBA

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. 20 DÉC.

    Comforting Habits

    I was chatting with a friend recently about routines and some of the helpful or silly things we do. I mentioned that when I played adult baseball, we often had Sunday morning games and a routine of mine was to drive to town, stop at a 7-11, and get a large cup of coffee and an apple fritter. It was a comforting habit that I still have today, often stopping when I have a morning flight to do the same thing in the way to the airport. Only in Denver though, not when I'm flying out of other cities and returning home. Read the rest of Comforting Habits

    3 min

  2. 18 DÉC.

    Big Data or Small Data

    I went to San Francisco for Small Data SF, a conference sponsored by Mother Duck. The premise of the event was that smaller sets of data are both very useful and prevalent. The manifesto speaks to me, as I am a big fan of smaller sets of data for sure. I also think that most of the time we can use less data than we think we need, especially when it's recent data. That often is more relevant and we end up with contorted queries that try to weight new or old data differently to reflect this. Maybe the best line for me is this one: Bigger data has an opportunity cost: Time. Read the rest of Big Data or Small Data

    3 min

  3. 16 DÉC.

    Learning to Grind

    When 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

    4 min

  4. 13 DÉC.

    The AI/Human Spectrum

    I was asked this question recently: is it more likely that AI will replace humans or assist them in their work? It's a good question. If you think about the way AI is being hyped in 2024, many people think AI is, or will soon be, replacing people and we need less of them in work. I guess the simplified view is that AI can do the jobs of many people, but I'm not sure the world is that simple. What I think is more likely is that AI becomes a lever that assists a few people in getting more work done and potentially replacing other, less knowledgable humans. Read the rest of The AI/Human Spectrum

    4 min

  5. 11 DÉC.

    Continuous Learning

    It seems there's quite a dichotomy in the technology workforce. On one hand I hear about the Great Resignation where many employees are leaving their jobs because of RTO (return to office) mandates or some other dissatisfaction with their job. On the other, I've seen quite a few people who were laid off and are struggling to find new positions. On the third hand, there is no shortage of companies who report they are struggling to find and hire talented people for some positions. I don't quite know what to think, but I do know that employment seems to be harder to come by. If you are looking for a job, I believe you need your own sustainable learning plan. If your organization can't find qualified talented staff, then the organization definitely needs a continuous learning plan. Read the rest of Continuous Learning

    3 min

  6. 9 DÉC.

    Why Would You Do That?

    I was listening to someone at Microsoft talk about their product recently. I can't disclose which one it was, but lots of people use this product and are impacted by changes. The particular thing that caught my attention was that the presenter noted there was a breaking change in the new version for some people. This wasn't a huge change or one that would affect a lot of people, but it was a breaking change for a few. Another attendee asked this question: I would tend to do xxx instead of what you showed, so why would you do this? Read the rest of Why Would You Do That?

    3 min

  7. 6 DÉC.

    Distributed Monoliths

    I 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

    3 min

  8. 4 DÉC.

    Reducing the Cycle Time

    There are lots of software development methodologies. This page lists a few, among them waterfall, agile, iterative, rapid, and more. What's been interesting to me is that the process of deciding what to code and then whether it works doesn't change much between different ways of building software. Instead, the cycle time between when we ask a client what to do and when we deliver it changes. The more agile/lean we are, the lower the cycle time. The more waterfall-ish, the larger the cycle time. I guess that analysis and breakdown of problems into work also changes, as the scope in modern DevOps styles of development is smaller (more contained) than in waterfall. Read the rest of Reducing the Cycle Time

    4 min
Tout afficher (100)

4,9
sur 5
9 notes

À propos

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.

Informations

  • Création
    Steve Jones
  • Années d’activité
    2007 - 2024
  • Épisodes
    100
  • Classification
    Tous publics
  • Copyright
    © Copyright 2020 Steve Jones
  • Site web de l’émission
    Voice of the DBA

Vous aimeriez peut‑être aussi

Pour écouter des épisodes au contenu explicite, connectez‑vous.

Recevez les dernières actualités sur cette émission

Connectez‑vous ou inscrivez‑vous pour suivre des émissions, enregistrer des épisodes et recevoir les dernières actualités.
Choisissez un pays ou une région

Afrique, Moyen‑Orient et Inde

Asie‑Pacifique

Europe

Amérique latine et Caraïbes

États‑Unis et Canada