I also thought of software when reading Antifragile, but my take on it is slightly different. For one, software per se is extremely fragile. Variability in in

I also thought of software when reading Antifragile, but my take on it is slightly different. For one, software per se is extremely fragile. Variability in inputs can easily break it. New browser version, someone presses buttons in a different order, Y2K, and everything comes crashing down. However, the overall system that includes the software and the team maintaining it can be antifragile, but it's not automatic. The team is like the immune system that fights off bugs; if it doesn't follow good practices, it can lose its ability to do so. For example, a policy of writing automated tests against bugs to make sure that do not reappear is antifragile (like creating antibodies). Another relevant point: nothing is antifragile without running an energy deficit. It costs money to keep software working, even without adding any features.