Content provided by Voice of the DBA. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Voice of the DBA or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App Go offline with the Player FM app!
HR is no longer just about managing people—it’s about shaping the future of work. Jens Baier, BCG’s HR transformation expert, discusses how AI and shifting employee expectations are forcing companies to rethink talent strategies. From re-recruiting to upskilling employees, HR must adapt to a rapidly changing landscape. Learn More: Jens Baier: https://on.bcg.com/41ca7Gv BCG on People Strategy: https://on.bcg.com/3QtAjro Decoding Global Talent: https://on.bcg.com/4gUC4IT…
Content provided by Voice of the DBA. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Voice of the DBA or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Content provided by Voice of the DBA. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Voice of the DBA or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
This is a strange time for many technology professionals and their employment. It seems many organizations have open positions and are struggling to fill those slots with qualified candidates ( one look at this ). At the same time, many other organizations have followed the large technology firms (FAANG, MSFT) and laid off large numbers of their staff in the last year. At the same time, with the hype and rapid growth of GenAI systems, we have companies that are looking to machines to fill some of their labor needs. Salesforce noted that they did not expect to hire more software engineers in 2025 as their plan was to use AI tech to help them write enough code. They’ve seen productivity gains with AI tech, so they aren’t adding more developers. They still need human developers, just not more of them. While thinking about the labor market, I ran across this report from the Bureau of Labor Statistics in the US, which tries to project jobs across many different industries in the future. They typically are careful and conservative, and while they show growth in the need for database administrators and database architects (and software developers) they also admit they can’t quite tell what impact GenAI tech will have on the labor market. They do think there will be an impact, but for now they have the need for data professionals growing faster than average. Why is it hard to get an IT job ? I know plenty of people looking for work that have struggled to find a position that suits them. I think there are a few things at work here. First, many companies have been burned in the past with unqualified candidates. We know hiring is hard, and we will make mistakes with some hires. With the focus on cloud, new technologies, DevOps, and more, companies want to hire skilled people who can hit the ground running. I also think the supply of workers is high and companies are more choosy about who they hire. Lots of companies are also investing in their own workforces, upskilling and re-skilling them in new technology. It’s often easier to train someone whose work ethic, soft skills, and other factors are known than hire someone new who might or might not be a good cultural fit. I know that I often see budgets for conferences and classes are low, but there are plenty of companies still sending people to classes, conferences, or providing opportunities to learn. If you want a new job, or you’re struggling to find one, I can’t stress enough the importance of working on your own skills and showing prospective employers that you are investing in yourself. Take stock of your skills and work on projects, experiments, build things, blog about them, and show companies that you have the skills they need. Don’t forget your soft skills as well if you’re investing in yourself. Learn to communicate well, both written and verbal, as that can often set you apart from other candidates. As someone that has interviewed others, those skills sometimes are more impactful than your technical ones. Invest in yourself now, and you’ll be ready for the challenges you face in the future. Steve Jones Listen to the podcast at Libsyn, Spotify , or iTunes . Note, podcasts are only available for a limited time online.…
Recently there was some online complaints about social security numbers (SSNs) in the US being duplicated and re-used by individuals. This is really political gamesmanship, so ignore the political part. Just know that social security numbers appear to be one of the contenders used in many data models. I found a good piece about how SSNs aren’t unique, and have a mess of problems. Despite this, many people seem to want to use SSNs as a primary or alternate key in their database systems. They also aren’t well secured in many systems, even though we should consider this sensitive PII data. As we have moved many analog systems to digital ones, we often find that our assumptions about the rules governing data aren’t that well defined. I’ve worked in many systems where data elements were assumed to be unique in some way, but they actually weren’t. I’ve seen invoices, POs, and other “unique numbers” actually duplicated because of simple mistakes by humans. When we try to enforce uniqueness in a database, we end up with problems. Often we actually need to drop keys and make exceptions because the data must be entered. This has led many people to not create unique constraints or even foreign keys in their systems, and I understand why they don’t. There are real problems when we assume the real world has the same strict structures we implement in code. I’ve seen systems go online and then FKs removed because of poor data quality. It might be a mistake, but it’s also a reality when we find there is existing child data without a parent. We might create a pseudo-parent at times, but we might also decide not to do so if that creates other problems. I suspect over time the real world will migrate some of their problematic keys to something more robust. However, some that are used widely in older systems, like SSNs, are unlikely to change in my lifetime. There are far too many places where this is in use and I am not sure that there is any consensus to undertake the massive amount of work to implement something else. I suspect even trying to add digits to the value is a task we’ll put off indefinitely. Be careful of using natural keys in your data models unless you are sure they are really a natural key. To me, I’m better off with some surrogate key in the event that my “natural key” turns out to not have the uniqueness I expected. Steve Jones Listen to the podcast at Libsyn, Spotify , or iTunes . Note, podcasts are only available for a limited time online.…
I’ve been working with databases for a long time and there are no shortage of things I’ve seen other people do that I don’t like. Sometimes I shake my head a little. Sometimes I might groan inwardly (hopefully not aloud), and sometimes I might make an effort to convince someone else to do something differently. Sometimes I’m really annoyed (or angry) and don’t even know what to do. I know that most people are trying to just get work done. They might rush through something and not do a good job, perhaps because of oversight, or perhaps they are naïve about the effects of their work. Maybe they have ingrained habits and are unwilling to change. Maybe there’s another reason (let me know if there is one). However, no matter the reason, it can be very frustrating to work on poor database designs. There might be other things that bother you, but today I’m focused on the data model. Do you see poor naming of objects? Are there problems with the way they structure their entities? A lack of indexes? What are your biggest complaints about the structures in your databases? While I am looking forward to your stories, I want you to be professional. We’ve all made mistakes, and there is likely some (most?) code we’ve written that we wish we could redo. Don’t embarrass anyone or any organization, but let us know which types of problems or anti-patterns are your biggest complaints. Bonus points if you can do it in a humorous story. Steve Jones Listen to the podcast at Libsyn, Spotify , or iTunes . Note, podcasts are only available for a limited time online.…
Welcome to Player FM!
Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.