{"id":7484,"date":"2020-08-12T15:43:15","date_gmt":"2020-08-12T13:43:15","guid":{"rendered":"https:\/\/www.codemotion.com\/magazine\/?p=7484"},"modified":"2020-09-03T10:27:19","modified_gmt":"2020-09-03T08:27:19","slug":"speeding-up-innovation-with-arun-gupta","status":"publish","type":"post","link":"https:\/\/www.codemotion.com\/magazine\/frontend\/web-developer\/speeding-up-innovation-with-arun-gupta\/","title":{"rendered":"Speeding up innovation with Arun Gupta"},"content":{"rendered":"\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\tTable Of Contents\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t
  1. The three stages of innovation<\/a>
  2. How do you measure the innovativeness of your company?<\/a>
  3. Smaller changes are better<\/a>
  4. Move from Monolith to microservices to innovate<\/a>
  5. Why Change one small thing at a time?<\/a>
  6. DevOps: How to get there<\/a>
  7. The value of distributed optimized capability<\/a>
  8. Cloud native principles and innovation<\/a>
  9. What is serverless and why is it important to innovation?<\/a><\/ol>\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\n\n\n

    Arun Gupta is a Principal Technologist at Amazon Web Services<\/span>. He is responsible for the Cloud<\/span> Native Computing Foundation (CNCF) strategy<\/span> within AWS<\/span> and participates at CNCF Board and technical meetings<\/span> actively. He works with different teams at Amazon<\/span> to help define their open source<\/span> strategy<\/span>. Arun spoke at Codemotion<\/span> about technology<\/span> as a means to speed up innovation<\/span>. These are just a few of the things he had to say, watch the video below for full impact<\/span>: <\/p>\n\n\n\n

    [jwp-video n=”1″]<\/p>\n\n\n\n

    The three stages of innovation<\/h2>\n\n\n\n

    According to Arun, there are three stages of innovation<\/span> in enterprise<\/a>:<\/p>\n\n\n\n

    1. Speed<\/strong>: You want to build something really fast, really quickly, put a stake in the ground, fail fast and recover.<\/li>
    2. Scale<\/strong>: You want to build something, let’s try this. Something really large, something that scales very well so that you can reach the masses.<\/li>
    3. Strategy<\/strong>: A more deadline-driven stage “where these companies who are server huggers know, they want to hold on to the data centres. They’re migrating to data to cloud. And these are deadline-driven, because essentially, if you think about, you know, there is two three year lease for a data centre, and when that is expiring, that’s the time you start thinking about it, does it really matter to me? Do I want to keep my data centre or do just move to the cloud?<\/li><\/ol>\n\n\n\n

      How do you measure the innovativeness of your company?<\/h2>\n\n\n\n

      Arun asserts that for developers<\/span><\/a>, innovation<\/span> can be measured in time to value. This means “that I, as a developer<\/span> built a feature, how long does it take for me to have that feature being realised by customers<\/span>?  Does it take months? Now I pushed a feature six months later as part of a monolith is going to be available to my customers<\/span>, or does it take days? No, maybe it spins out on a weekly cadence as a weekly bill that goes out. Or you have something called as a continuous delivery pipeline where every change you push automatically builds your software and releases it to the customers<\/span>. The faster your release cycle is, the faster your customers<\/span> can realise it.”<\/p>\n\n\n\n

      Smaller changes are better<\/h2>\n\n\n\n

      In terms of software<\/span>, we have realised over the years, that the smaller the better, the more the focus it is, the faster it builds, and the faster it drops.<\/p>\n\n\n\n

      Thre are however, key components<\/span> that you require for in building those lots of small changes:<\/p>\n\n\n\n