This is day 321. No drilling through bulkheads. We are going to be software developers in the next 15 years. All of us. I know that it's hard to believe, but I think that is where we are headed, not because everyone will suddenly Learn Python or spend their days building applications, but because more and more of our work will involve humans, directing and guiding systems to produce the results that we want. And that sense we will all be doing systems development, whether we call it that or not. As that happens, I think we're going to have to relearn some very old principles. One of the most important is something that I started calling the watertight ship principal. A large ship is one vessel but inside that vessel or compartment separated by bulkheads. Those walls exist for a reason. If water gets into one compartment, you want to contain their rather than spreading throughout the entire ship. Each compartment has a purpose and the Integrity of the ship. Depends on respecting these boundaries. I've learned this lesson in places far, removed from software. Take my laundry, for instance, I hate laundry, but over the years, I've developed a system that makes it tolerable. Dirty clothes get deposited into five different baskets and each basket has a purpose. One of those baskets is dedicated entirely to socks. Its whole job is to manage socks. Socks go in there, they get washed together and I have a place to keep track of them throughout the process. This dramatically reduces the Mr. Mysterious disappearance of socks. It seems to plague every household. This system works but it only works. However, if I respect the boundary, I cannot let my work out clothes into the sock basket because it happens to be convenient. And that cannot throw a shirt in there because I'm standing nearby. The moment, I start making exceptions the system begins to break down. Socks, start, migrating, and eventually sucks then disappear. The compartment is no longer watertight in that instance. The same thing is true with corporate finances. I have a car dedicated to business expenses and the rule has to be absolute. Personal expenses, do not go on that card. It cannot be most of the time or unless Simon a hurry or this purchases a small and I will remember to fix it later. The moment, I start making exceptions like create work Downstream. Now someone has to categorize the transaction reconcile. It explaining it corrected and remember what happened months later. a clean system becomes messy because I drilled a tiny hole through the bulkhead This is becoming even more important in the age of AI because AI makes shortcuts incredibly attractive. You are building something automating a process or creating a new system and suddenly realize you can save 20 minutes by connecting two things directly. You can bypass a step, let one system reach into another. Or make a little exception that seems harmless at the time. AI will help will happily help you do it and because it can build so quickly, you may not even feel the cost at first. The problem is that systems have memories. Even when we do not the shortcut Remains, the exception becomes precedent and the temporary connection slowly turns into permanent infrastructure. Eventually you have no idea why anything works the way that it does. I received a very literal, reminder of this the other day when we suddenly had ants in the house. I became curious about how they were getting inside and started tracing their path until eventually I found their entrance. I had created it. Months earlier actually, a year earlier. I've been working on some project and needed to run a cable rather than finding the proper route, I took the easy way out and drilled a hole. eventually, the project was abandoned and the cable just disappeared, but the whole remained Apparel. The ants were more than happy to make use of the infrastructure that I had left behind without realizing it. I had built them, a tiny Highway directly into my bathroom. That struck me is a pretty good less than about systems. Every time we punch a hole through a boundary because it makes today's task easier, we create a path Something else may have eventually discover that path dated begins flowing through it, dependencies develop around it and people start relying on it. Long after we have forgotten why we created it, the whole can still be there. The modern Warrior is going to live inside, increasingly complicated systems. AI will allow us to build those systems faster than anyone in history would have possibly imagined, which means discipline becomes more important. Not less. A tight ship runs like a tight ship because the engine room stays clean. The compartments have purposes and the boundaries are respected water debris, clutter and conveniences are not allowed to slowly compromise the entire vessel whether you are building software, managing finances, organizing your laundry or running a company or simply just trying to keep the ants out of the bathroom, the principle is the same Build your compartments, respect their purpose and no matter how tempting the shortcut appears. Remember the rule No drilling through bulkheads.