Over my 4 decades writing software, security (and "bugs" over a longer timeframe since network connections were rare early on in what I worked on), most organiz

Over my 4 decades writing software, security (and "bugs" over a longer timeframe since network connections were rare early on in what I worked on), most organizations I worked for either considered them unimportant compared to delivery, or followed a finger in the dike mentality: when you find a hole, just fix the hole and move on. What I found for myself that it made more sense to spend enough time on the architecture/design/whatever of the dike so that holes were unlikely plus always consider that even rare possibilities needed consideration. That attitude costs money, and often it's difficult to convince people to spend money with no immediate gain. I was able to do it right sometimes by taking advantage of how unknowledgeable leaders often are about technology.