Voice of the DBA

Imagine that you are about to tackle a new project that will take more than a year. This might be a new system, perhaps a cloud migration, or maybe it's rewriting something that doesn't work well. You don't have enough employees to undertake the project without overloading everyone. Your team needs to grow. Would you rather hire a more senior person from outside the organization or pick a junior person that's already inside your company and teach them what they need to know? Think about this as if you were the one making the decision about the future direction of your software team. Philosophically, do you want to buy experienced people or train/build new ones from your internal staff. Read the rest of Internal Staff Growth

I ran across a thought-provoking post from Chrissy LeMaire asking if we should reconsider SQL Server HA. The post actually asks if you've considered not using it. The default from Chrissy, for most installations, is to use standalone SQL Servers. This isn't to say she's against HA solutions (FCIs or AGs), but that they often cause problems and might not be needed. It's an interesting position to consider. For a long time, I avoided SQL Server clusters as they were hard to setup with a lot of complexity, hardware requirements, etc., and didn't really provide enough benefits over using log shipping with a second server for me.  These days I have clients with mostly AGs, and they seem to run fine. That being said, Chrissy notes that after she left a job, a network outages caused a bunch of downtime. I could see there being downtime, as the old database mirroring (and the it-will-never-die replication) needed a working network. If you have network issues, you better know how to manage your HA technology's issues. Read the rest of Do You Really Need HA?

I wrote recently about some work with Redgate Clone, and one of the things I did was start up a blank container instance of SQL Server from the image named empty-sql-current. This image contains SQL Server 2019. Clearly, "current" was a poor choice. I see this often in various places, where someone will reference "current", "new", "latest", or some other term that denotes the most recent changes. If everyone reading the reference is doing so with knowledge of the past and at a time close to publication, this works fine. However, a year later, does this make sense? At the same time, I do like consistent names that might be used in scripts. If I always want developers pulling the latest item, I might use latest. However, if versions are important, than "latest" or "current" might not be the best choice. Much of the time, I tend to try and get a version or some other specific indicator in a name. Read the rest of Poor Name Choice

There is a ton of hype now about using GenAI for various tasks, especially for technical workers. There are lots of executives who would like to use AI to reduce their cost of labor, whether that's getting more out of their existing staff or perhaps even reducing staff. Salesforce famously noted they weren't hiring software engineers in 2025. I'm not sure they let engineers go, but it seems they did let support people go. For many technical people, we know the hype of a GenAI agent writing code is just that: hype. The agents can't do the same job that humans do, at least not for some humans. We still need humans to prompt the AIs, make decisions, and maybe most importantly, stop the agents when they're off track. I'm not sure anyone other than a trained software engineer can do that well. Read the rest of Data > Hype

I wrote recently about a bad first day for an intern. He/she was fired, without cause in my opinion, when a production database was damaged while following a document for developer setup. The situation felt like a mistake, and one that wasn't necessarily the fault of the individual. To me, this was extremely poor handling of the situation from a CTO. In the discussion for the piece, someone pointed out that it might not just be a new employee who makes a mistake that causes downtime. Certainly, an inexperienced employee could have caused the issue, but I know there are plenty people with lots of time in a position who make similar mistakes. It could be that one who has been there a long time followed a poorly documented procedure for the first time, or applied the procedure to the wrong situation. Often, I find these are relatively simple mistakes because someone isn't as familiar with a protocol or skill as another person assumed they were. Read the rest of Practice Until You Don't Get It Wrong

I ran across this article on a survey about AI usage recently. The headline is this: 55% of businesses admit wrong decisions in making employees redundant when bringing AI into the workforce. That sounds a little ominous for those making these decisions, and a lot of you might be saying, "I could have told you that. Using AI to replace people is a bad decision." On the surface, I agree. I dislike the idea that companies will opt for a semi-competent AI bot or agent to replace people, thereby further exacerbating the challenges faced by many workers in the modern world. Read the rest of The Selfish Case for Learning AI

Cloud costs are high and growing. Some orgs think they're out of control and are trying to limit spend. Some orgs are looking to leave the cloud. A lot of IT spend over the years has been seen as a cost center, with many executives trying to limit the growth or spend, even while they aim for digital transformations of their businesses. Throughout my career, it's been interesting seeing the tension of groups trying to take advantage of technology and the finance departments trying to manage costs. The cloud brings some of the same debates/arguments/concerns to the forefront. Partially because of scale, as we can add cloud resources much quicker than we can with a CapEx purchase. Partially because we've also often lost some control over budgeting with the move to OpEx and subscription things. Read the rest of Reducing Cloud Cost

DevOps can mean a lot of things, but I find in practice that this results in a team using Continuous Integration and Continuous Deployment/Delivery using automation to check and evaluate your software in some way. This should result in quicker delivery of updates and changes to customers, better agility, and higher quality of code. That last one only comes if you use testing and try to ensure your code is well-written. It's easy to just use DevOps to throw out more poorly written code that doesn't perform well. Read the rest of DevOps is DevOps

The other day, I asked my daughter if she wanted me to make her some eggs. She responded with a "Yes!" in text and came to sit up at the counter while I cooked for us both. We chatted a bit, and at one point she said, "Thanks for cooking, but it's not that I can't cook." I laughed a bit and responded with "this isn't a can/can't situation, it's a do/don't or will/won't one." I know my girl can cook; I made sure all my kids learned how to cook. It's that they often choose not to, hunting for leftovers, going for takeout, or skipping meals. Read the rest of Can/Can't Do/Don't

I fly a lot, as you might have guessed if you read my blog regularly. In 2025, I've been on 56 United planes as I write this, with about 10 left to go before the end of the year. One of the things United does is sometimes send out a quick "survey" after a flight, checking to see if everything went smoothly. I don't always fill these out, but recently I decided to give some feedback as I had a great experience. I really wanted to just complement the onboard crew, but the survey was quite a few pages (10?) and a lot of questions. I started to try and fill it out, but lost focus after a few pages. This felt like a chore, and I started to just randomly click some of the selections asking me to rate things 1-10. I wasn't really rating the items; I was trying to get done. Eventually, I bailed on the survey and didn't complete it, but that got me thinking about the data from these surveys. Read the rest of Be Wary of Data

Most of you reading this work in technology, and I assume that you've had to learn something new on the job. Technology is constantly evolving, even on our existing platforms. On top of that, we are regularly given tasks that are outside of our current skill sets. Maybe not far outside, but to meet the changing demands of our jobs, we need to learn new things. I ran across an interesting post (on a new site) from Brent Ozar. I think that guy writes as much as me, but he wrote this one: Why I Started Using Postgres (And You Might Too). It's a little provocative, but there are good posts on the site about things Brent learned in PostgreSQL. I won't go into whether learning PostgreSQL is a good idea. Read the rest of The Journey to PostgreSQL (or anything)

I ran across an interesting open letter. Most of these are from individuals, often complaining or lamenting on the way something in the world works, or maybe doesn't work. This latest letter was from the Chief InfoSec Officer at JPMorganChase, a large worldwide bank. This open letter was written to the software suppliers looking to do business with JPMorganChase, especially those in the SaaS area (Software as a Service). The letter opens by noting that SaaS is enabling cyber attackers and asks for three things: prioritize security over features, modernize security architecture, and work with security collaboratively to prevent abuse of connected systems. Read the rest of We Should Demand Better

I caught a short post from Gary Bargsley on LinkedIn that had this quote: "Many people do not believe this is true. If there isn't a fire to put out, then you are not doing a good job." He included a repost from Shaik Ashraf with that quote and an image that explains better what things a DBA is doing because they aren't always busy. I would say that by busy we think of a DBA as rushed and always trying to fix something that isn't working well. I've certainly walked into operational positions where this was the case. Things weren't working smoothly or breaking regularly. My phone was always ringing, as I moved from crisis to crisis. For some systems, rebooting them regularly was the fix, not because I didn't want to determine a root cause and fix them, but because I had too many other priorities. A reboot at least recompiled plans, cleared caches, and got the system working for a few days. Read the rest of The Improvement Limit

Recently, I got a bill from Azure. That's not an unusual thing for many of you, but for me it was a surprise because it said I was late paying. I've had a number of services running, and I thought at first that I had left something running too long, like a VM. As I checked, most of the things were paused, even the expensive ones like a Synapse workspace. Instead, I found that my free credits were not being applied. Fortunately, I had changed credit cards or I might have been billed for a few months before I noticed. This was a change in how Microsoft managed benefits, which is fine. I opened a support call and someone helped me, but it took several days to get a response. I was slightly worried about the bills, so I decided to audit the things I had running. Read the rest of Cleaning Up the Cloud

I've spent quite a bit of my career as a DBA/sysadmin/Operations person. However, I've had my share of development positions as well. As I work with customers who look to mature their database development to be more like other software development, I've noticed that PRs sometimes don't get handled as smoothly as we might like. In some sense, they are like help desk trouble tickets that never get closed. One of the first things I caution people about is specifying specific reviewers, especially DBAs. There are often DBAs who are the gatekeepers for code, but if we require them to be the only ones to review code before a CI or test process, we really slow things down. This often happens in smaller environments where one DBA wants to avoid anything impacting their job. They want to review everything before it commits. Read the rest of PRs Are Like Trouble Tickets

Some of you out there are positive about AI and looking to use them. Some of you aren't too thrilled with the tools and might avoid using them. I think that not learning to harness the power of an AI is a mistake. This technology is going to change the world in many ways and you need to learn how it can help you. You also should learn where the sharp edges are as there are some very, very sharp edges. Read the rest of Choosing an AI in Sept 2025

I get a regular email from Quora, with questions that I might be able to answer or might be of interest to me. There are some database questions, some Tesla ones, and others, but recently I caught an interesting one that asked: why are most people broke? To be fair, there are a lot of questions that appear to be trolling, not people seeking answers, but this one caught my eye. This isn't very data-related, but it is a bit of advice from someone who is getting older. As I look towards retirement in the next decade or two, part of my planning is ensuring that finances are in order. Once I stop working or slow down, the economics of my family change, and we need to be thinking forward to ensure that we have enough funds for our daily living. This can vary in different parts of the world, but I'm surprised at how many people don't really think about covering their daily expenses without a salary. Read the rest of Don't Forget About Financial Skills

As I get older, I find that time is the most valuable commodity I have. It's the one thing that I need more of, but I can't get it. Even if I find more efficient ways of doing things, it seems there's an endless list of things at work and on the ranch that need to be done. It seems to be the same for most of my friends in other jobs, whether in medicine, law, or any other position; they're often overloaded with more work than they can get done in a week. Arguably, it's not all important work, as sometimes we might tackle a task, only to have our boss throw the work away or delay the project. That's annoying, but I also understand priorities change. Read the rest of Getting More Time from AI

I studied economics in university, which isn't that close to database work, though I did have to work through linear regression problems by hand. I always enjoyed mathematics, so this wasn't a hardship. Until I purchased a PC that was capable of letting me do graphs and calculations in PASCAL and BASIC. Then I realized that my enjoyment wasn't that efficient or useful, and a computer could help me get things done way more efficiently. Many of us work on systems that process tremendous amounts of data, something our organizations couldn't complete without computer hardware, efficiently or not. We just wouldn't be able to get the work done by hand. That's the main reason why downtime is such a problem in the modern world; we can't fall back to manual systems in many cases. Read the rest of All the Costs of Downtime

One of the most prolific and popular authors at Simple Talk has been Phil Factor. He wrote many pieces on all aspects of database work and has probably written more articles on the Redgate Product Learning site than anyone else. He has entertained, informed, and inspired many database professionals in his many years as an author. Phil, aka Andrew, passed away recently. This was a shock to many of us and a sad day. Tony Davis introduced me to Phil, whom I always thought of as Andrew, many years ago when I first traveled to Redgate. Tony published a tribute to Andrew on Simple Talk and has many more fond memories of Andrew. If you ever get the chance to meet Tony, ask him for a few. Read the rest of Remembering Phil Factor

Many of you reading this likely have an Availability Group (AG) set up on at least one database in your organization. Maybe not most, but many of you as this has proven to be a technology that many people like for HA/DR, upgrades, and probably other uses. As the technology has evolved from it's SQL Server 2012 debut, it has improved in many ways. This might be one of the few features that has received regular attention from the developers in Redmond across multiple versions. That's not to imply this is a foolproof or bug-free feature. Numerous people have had issues with the various types of AGs. From setup to performance to scale, I've seen many people post questions and search for answers on how to get their system running smoothly and reduce any late-night calls. Read the rest of Pushing the Limits of AGs

Take a moment and think about how much work you do each day. If you write code, how much time do you actually spend writing code around meetings, admin work, and other tasks. If you manage systems and develop scripts, how often do you get to work on a script, change it, upgrade it, or add a new feature? I bet it's a minority of time for most of you. Studies show that many developers spend only an hour or two writing code each day. I would guess it's lower for sysadmins or DBAs who incorporate coding into their jobs. Now think about how much you enjoy each thing you do. I assume meetings aren't the most exciting thing you work on, nor is updating a document for others to read. When I wrote code as the main part of my job, solving the problem, trying different algorithms, experimenting with enhancements, those were the fun times. Read the rest of AI Steals Joy

There has been a lot of news about air traffic problems in the US in 2025. I haven't had any delays due to this, though I've gotten a few messages in my travels that I might want to reschedule. There was an article that some of the technology still used in various facilities is old and needs upgrading. Old as in Windows 95 and floppy disks. That's old, but obviously it still works. Even with the various accounts of problems, almost every day thousands of flights are managed successfully by the people who run these systems. They're not alone, as the article also points out that some other transit systems make do with technology that most of us would never think of using for any system. Read the rest of The Security of Old Tech

I remember working at a large organization with a team of other IT Operations staffers. We rotated this one job every month amongst a few people, each taking turns, where we'd lose a day to update all the privileged passwords for our servers. This was before Managed Service Accounts and the cloud, when we were required to change these every 30 days and then store the new ones in an encrypted store. What struck me when I got stuck with this wasn't the requirement to change every 30 days; that seemed normal. The thing that bothered me was how manual this was. As a former developer, I wrote some scripts to automated this, pre-PowerShell, and make the task easier on my fellow sys admins. I had scripts to generate a password, change it in AD, then print the pwd to be copied into our secure storage (no API there). This ran in a loop so I didn't lose a whole day to changing password. Read the rest of Password Guidance

I was working with a customer recently that is trying to improve their processes. This was a large company, over 100,000 employees, though most of them aren't in the technology area. However, across many divisions and groups, there are a lot of developers and operations personnel who have tended to work in silos, managing their own applications and systems in disparate ways. In other words, doing software development the way most companies do it. Read the rest of Requiring Technical Debt Payments

I saw a post from Brent that Microsoft had changed the default memory guidance. At first glance I read this as they'd changed the default values, which would be interesting. However, this is a guideline, set to 75%. I also saw a few thoughts from Randolph West on LinkedIn, and quite a few comments. The comments were interesting in a few ways. It is easy to look at 75% and say that won't work for this server that's on my mind right now because I keep getting woken up. That might be true. However, the 75% number isn't a hard requirement. It's a guideline, a recommendation to ensure you have enough memory for the OS, but you're trying to use most for SQL Server. Feel free to adjust it if you feel the need. Read the rest of Guidelines and Requirements

One of the major concerns for using GenAI tools is who is reading the data you submit as a prompt, and will this data be used in future training of the model? In other words, could someone using a future model access the data I put in a GenAI chat? It's a valid concern, and not just because of the vendors. There is a lawsuit over the use of data by OpenAI, and a court has ordered all chats to be retained, including deleted ones. Since this is a lawsuit, there is always a chance that some of the data retained gets entered into a court document or even that it might be read aloud in court and captured in a transcript. Read the rest of Concerns over AI Chat Privacy

I remember the court case years ago when the US government wanted to access data in Azure that was physically stored in Ireland. I wrote lightly about this and linked to the article back in 2020. This has typically been more of a concern for the EU (and other countries) than the US, but I'm sure there are organizations in the US that use the cloud and don't want their data accessed by other countries' governments. Recently, a Microsoft executive was asked about this in the French Senate. The Microsoft response was that they  (Microsoft) cannot guarantee data sovereignty for French customers. If the US government served a warrant under the Cloud Act, a US corporation would have to turn over the data. Read the rest of Data Sovereignty in the Cloud

Ghostworking is pretending to be busy at work. According to this article, it's on the rise with a number of people looking for other remote opportunities at other organizations. Some employees might be just wasting time at the office, though I suspect there is a minority that are actually working at another (second) job. Maybe they are growing a side hustle or maybe they've even accepted another job, and they're spending part of there day on those tasks. This might be part of the reason that many managers want to get people back into the office. I think that's flawed as a)  most managers aren't great at their jobs and b) people still ghost work in the office. I've had numerous "clipboard carriers" alongside me in my career who spend an inordinate amount of time at the water cooler, coffee machine, or walking from place to place and are happy to engage in hallway chats. I've seen plenty of managers also not know how to hold people accountable for their work (or lack thereof). Especially technical people who find many reasons why problems are hard to solve. Read the rest of Ghostworkers

SQL Server 2025 is out in preview form. CTP 2.0 is available for you to test, and there are quite a few changes that have been added to the platform. Some of these are already in the cloud, but this is your chance to test them in your environment. This is version 17.x, though I don't know we've really had 17 versions to work with. In any case, there have been a lot of versions in my career. I've connected to and worked on all of these: 4.2, 6.0, 6.5, 7.0, 2000, 2005, 2008, 2008R2, 2012, 2014, 2016, 2017, 2019, 2022. No 2025 yet (other than install and a few basic queries), but that's coming. Read the rest of Your Favorite Improvement

I mean, you can ask for a raise. It's always an option, but is now the time to ask for a raise in this economic climate, where businesses can be unsettled and there are a lot of tech workers looking for jobs. I even saw a piece that noted many computer science graduates are struggling to get hired at the top tech firms. While that's not where most people work, it seems that often other CIOs/CTOs look to the big tech firms for guidance, and they may choose to hire fewer new staffers as well. This is on my mind at work after reading an article on asking for a raise that I added to the newsletter. It's a response in the advice column where a reader asks how to go about asking for a raise when they think they deserve one. It is unclear in which industry or level this person works, so I am not sure if I think the advice is good. Read the rest of Can You Ask for a Raise?

At SQL Bits, I was chatting with Brent about a few things, including AI, which we think is changing the world. I've got my set of AI experiments going, and I do believe we will fundamentally alter work and how we use computers in the future. Not sure if it's for the better or worse, but things are changing and will change more. Read the rest of The Next Great Thing

For many years, most of the SQL Server installations I managed or deployed to were Standard Edition. Even in large companies that had agreements with Microsoft, since each instance had a cost (even at a discount), we were careful about where we installed Enterprise Edition. These days with Microsoft wanting to charge everyone for every core, it makes sense to use Standard Edition wherever you can. Read the rest of Who is Using Standard Edition?

Often,  we work on projects that might span a significant amount of time. Weeks, months, even years can be devoted to working on one system, or the same system. We may find that our motivation rises and wanes at different times. We get excited and motivated to get things done, and also become discouraged or distracted when challenges arise. Not all of us, or not all the time, but it is hard to maintain a high level of productivity and motivation over time. For managers, it can be a challenge to keep a team moving over time and focused on achieving goals. Life gets in the way, people take vacations, staff changes, and other things are all issues that can distract a team. Keeping a team focused and productive can be a challenge for many managers. Perhaps especially challenging when someone hasn't received enough training on how to manage and motivate others. Read the rest of Carrots and Sticks

There was a time when I knew a lot about the various storage technologies available for a database. It was important when designing a server around the various requirements for size and performance balanced against the limitations of hardware. The rapid growth of solid state storage and the adoption of storage area networks have changed the game for many of us. We no longer care or think about storage. It's just a service that we consume in our databases, and while we might demand more IOPS capacity, we often don't worry too much about how that's provided to our systems. Read the rest of Storage Enhancements

This is my last day of work. Not forever, just for six weeks. I'm off on my sabbatical after today and won't be back until August 11. However, everything should run smoothly with Grant and Kellyn holding things down until I return. Have a little patience with them as this site can be a bit of a hectic whirlwind at times, and they still have other jobs to do. It's been a wild first half of the year. After very little travel in Jan/Feb, the rest of the year has been a bunch of travel, including most of May and June being on the road. With coaching responsibilities for two teams from Jan-Apr, I am ready for a break. No big plans, but I am looking forward to being at home, playing some guitar, working on a few projects while trying to be very unwired for six weeks. Read the rest of A Well Deserved Break

I ran across an article on the 7 types of tech debt that can cripple your business, which is a great title. It certainly is one that might scare a lot of CTOs/CIOs/tech management. I am sure that much of the IT management gets concerned on a regular basis with how quickly their staff can evolve their software to meet new business needs. The first two items have to do with data, which is understandable. Data is the core of how many organizations operate and move forward, and if you don't have the ability to easily work with data in a flexible way, you can struggle. Many of us technical people know this, but I find many non-data-professional staffers don't get this and are often unwilling to work at improving the situation. They things to just be magically better without changing how they do their jobs. Read the rest of The Technical Debt Anchor

Each time I compile and curate the Database Weekly newsletter, I find lots of Fabric content from the various sources I watch to compose the newsletter. Since I primarily deal with the Microsoft Data Platform stack, this makes sense. Most of the things I am interested in are related to Microsoft, and as a result, I tend to use sources that also use SQL Server, Power BI, Fabric, and related technologies. I do look for other related data items, but I am heavily MSSQL focused. Recently, I stumbled on a piece that contains Fabric Alternatives in AWS, GCP, and OCI. It covers some of the options on these cloud platforms at a very high level. A product name and short description, but it shows there are other choices. I found it interesting that Databricks is mentioned, but not Snowflake. I'm not sure why that is, as Databricks is on Azure (and other platforms) as is Snowflake, but perhaps the author doesn't consider Snowflake a peer? That seems strange. Read the rest of The Data Warehousing Choice

Part of my Redgate work is with customers who need to monitor their database servers. With estates growing quickly, both in scale and types of database platforms used, keeping an eye on everything can be challenging. Add in the lack of staff growing as quickly are the number of servers, and I find many companies seeking out monitoring tools to better help them manage the entire estate.. When someone evaluates a tool, one of the first questions from many people is about load. They are concerned about the load a tool puts on the system, which is always some amount. Most tools say they use less than 2% of total resources, some might hedge at 5%. Hopefully, there's no more impact than 5%, though that might seem to high, especially if you have a busy database server already. Read the rest of Multiple Monitoring Tools

Are you looking forward to SQL Server 2025? Or perhaps you think this is just another release, or perhaps you are not looking for new features or capabilities in your environment. Maybe you don't care about new things, but are looking for enhancements to features introduced in 2017/2019/2022. There is certainly no shortage of things that can be improved from previous versions (cough graph *cough). I ran across an article on the five things that one person is looking forward to in SQL Server 2025. It's a good list, and the things included make me consider an upgrade. Certainly, any improvements in the performance area, especially with all the investments made in Intelligent Query Processing over the last few versions, are worth evaluating. They might help your workload, or they might not, but if they do, then upgrade. Read the rest of SQL Server 2025 Excitement

I had to make a few changes to a SQL Saturday event recently. The repo is public, and some of the organizers submit PRs for their changes, and others send me an email/message/text/etc. for a change. In this case, an organizer just asked for a couple of image updates to their site. I opened VS Code, created a branch, added a URL for the images, and submitted my own PR. After the build, I deployed it. And it didn't work. Read the rest of Patching the Patch

When talking about DevOps, the goal is to produce better software over time. Both better quality as well as a smoother process of getting bits to your clients. There are a number of metrics typically used to measure how well a software team is performing, and one of the things is Change fail percentage. This is the percentage of deployments that causes a failure in production, which means a hotfix or rollback is needed. Essentially we need to fail forward or roll back to get things working. For most people, a failed deployment means downtime. I've caused a service to be down (or a page or an app) because of a code change I made. This includes the database, as a schema change could cause the application to fail. Maybe we've renamed something (always a bad idea) and the app hasn't updated. Maybe we added a new column to a table and some other code has an insert statement without a column list that won't run. There are any number of database changes that might require a hotfix or rollback and could be considered a failure. Read the rest of What is a Failed Deployment?

Many of us are faced with choices and decisions constantly in our jobs. How do we approach a problem? What should we do as a team to get the work done? How do we code or manage or test or do something else with a database? Maybe more importantly, how long do we spend deciding? Read the rest of Shorten the Debate

At an event recently, I had a chat with someone after one of my sessions. I had been speaking on DevOps and ways to better structure your team and build software. After the session, one person asked me if I'd read The Mythical Man Month and if I felt we'd gotten a lot better at building software since that book was published. I do think we have gotten better, way better, in fact. I caught another review of the book a while back from the Pragmatic Engineer. That view looked at what's changed in 50 years since the first edition, as well as contrasting the world today. You have to subscribe to read that one, but I'll give you a few thoughts from me on the book itself and the review. Read the rest of Reflecting on the Mythical Man Month

I've been reading an interesting book that looks at some of the ways that we can better build software in enterprises. One of the side notes in the book is that the tech companies have the funding and the ability to disrupt many other types of businesses, not just technology. Google, Amazon, Microsoft, and others have delved into other types of industries, potentially pushing others out. We see Amazon becoming as much a shipping and logistics company as they are a retailer. There was a unionization vote, which passed in 2022. Recently, another one failed. Amazon continues to fight these efforts, trying to prevent workers from collectively negotiating the terms of their employment. Read the rest of IT Unionization

At a recent event, I had a student ask about how to get started as a data professional. What types of things should they do? What platform should they work on or learn? Where should they focus time? What tools are available? Those are all good questions and many of you likely have your own advice. I'll give a few things to think about today, which are good for anyone that might want to get into the data field. I think this is still one of the better technical careers. I've suggested this to my kids, though only one of them went into a technical area. One is a therapist for autistic children and one helps run the ranch while pursuing a graduate degree in literature. Read the rest of Helping Students with a Data Professional Career