He totally changed that part.Īnother huge part that he changed was, he changed the way that wars are fought. He came up with a way to change that, and it changed the way that every fighter plane around the world, not just in America, was designed, and how they’re designed still to this day. He came up with a formula and different way of being able to measure how velocity, and how banking, and some of the other terms that I don’t really understand around fighter pilots and around planes, but just avionics in general. One of the first things that he did, and was really known for, is he changed the way that fighter pilots and the way that fighter planes are designed, and how they’re measured as well. The way that he approached solving different problems. It’s really about his career and the way that he solved problems. He didn’t really ever see any combat experience there. He was fighter pilot back in, I think started out in World War II. I probably should have gotten to it a little bit faster. I’ve been wanting to do it, kind of been putting it off. I’ve also seen it recommended a couple different other places. It’s been on that list, and I’ve been making my way through that list. I got into the book following Ryan Holiday’s, I think it was books, maybe 25 or 20 different books that are biographies that everyone must read. I did want to tell you how I got into the book. I’ll talk a little bit about that here in just a second. I’m sure somebody’s referenced something in there called the OODA loop. You use it every day, and you probably learned about it in any of your business courses or any of your corporate meetings that you’ve been in. How is this going to relate to technology, big data, you know, software development?” Let me just say, it absolutely applies. You’re probably thinking, “Okay, wait a minute. Today, I’m doing a book review on Boyd: The Fighter Pilot Who Changed the Art of War. Hi, Thomas Henson here with, and today, we’re going to do a book review on Boyd: The Fighter Pilot Who Changed the Art of War. Transcript How a Fighter Pilot Created DevOps The faster we can iterate through these loops the better our applications will be for our users. At the end of this loop the feature/enhancement is pushed to production where its usefulness is tested which starts a new feedback loop. Finally, we develop the solution based on the user story (Act). Then, we add the user story to our development schedule (Decide). Next, we create a user story how to solve the problem (Orient). First, we find a problem to solve (Observe). In Agile software development we try to mimic these steps in our iterations of work. The point of the loop is to go through these steps repeatedly faster than your foe. Observe, Orient, Decide, and Act (OODA) is the feedback loop coined by John Boyd.
0 Comments
Leave a Reply. |