According to Ben Horowitz "peacetime" and "wartime" CEOs require radically different management styles. I believe this concept applies to CIOs as well. As an effective CIO, you never just take a job. You are accepting a mission.

AI won’t replace humans, but humans that use AI will replace humans without AI. AI is largely incapable of doing entire jobs. However, it is great at doing specific tasks within broader roles. People who are embracing AI as part of their workflow are creating higher quality work faster than ever.

If you read the news covering artificial intelligence (AI) developments on any given day, you may feel pangs of dread. It seems like the technology has evolved so rapidly that it will be difficult to "catch up", let alone "keep up". However, the key is not merely to "keep up," but to strategically integrate AI in ways that enhance efficiency, innovation, and overall competitiveness.

Code is easy to refactor or rewrite. Changing code is computationally inexpensive. Not true with data. Data outliving code is a good problem to have, usually reserved for successful companies..

I wrotes these principles down in 2015. At the time they felt "visionary". Looking back now I love these principles even more, but they seem obvious and ordinary now.

Engineering teams love full rewrites because they incorrectly think of old systems as specs. They assume that since the old system works, all functional aspects have been settled. Design risks have been eliminated! They can focus purely on adding more features to the new system, or making changes to the underlying architecture without worry. However, the belief that new code is better than old is patently absurd. Old code has been used. It has been tested. Lots of bugs have been found, and more importantly fixed.