If you know me, I know what you are thinking – “Floyd, you frequent many technology events annually in your travels so it is not a big stretch to have a geek-fest conversation with a few young open source developers”. I could not agree more! It is fairly common for me to talk with a mixture of young and senior developers collectively during professional conferences. The reality is this did not happen at an organized technology event. All of this GitHub and DevOps dialogue took place at a restaurant in Kathmandu, Nepal. The event was a meet-and-greet for family and friends of Prawal, the groom to be at an upcoming Hindu marriage. This collision of culture, code and technology starts when my brother hired Prawal eight years ago for an electrical engineering position in the Boston area. This led to an invitation for my brother’s family to attend the wedding, extended family counting me. Needless to say, I was more than pleased to accept the invitation and adventure.
What is my point you ask! Git continues to gain traction in the development world even in developing countries like Nepal. Our strategic business partner, GitHub, boasts 32 million developers using their social development platform modeled around a Git repository. I talk daily to programming managers and developers about how they have the need to deliver new features and functions to the business faster than ever imagined before. Innovative ways to engage customers or prospects through new touch points, web interactions and mobile applications. These new user interfaces often require integration with the critical business data that, in our world, resides on the IBM i. It is this clash in development workflow that is causing stress and fracturing of any current workflow process, tooling and lastly people. There is a tremendous need for a platform that is scalable, secure, reliable, yet quick that can manage software modification risk. This concept of DevOps to standardize workflow of software change on a common stack of tooling for business-critical source code assets could cause even more havoc in an already hectic world, if attempted without a depth of understanding of the challenges both real and perceived. In addition, you still need to provide the needed financial value in terms of implementing, training and return on investment. Delivering on all these promises is what makes DevOps very appealing to companies of all sizes.
Why Git? From the start, it was designed to take into account this new collaborative paradigm of development. It includes the needed productivity and independence of code modifications for today’s programmer, yet still provides the needed structure, security and compliance mandated by the business environment today. It provides the ability to function over disparate computer languages, developer demands, and distributed teams without sacrifice in providing the integration, speed and flexibility to drive the business and market changing innovation. It is a new way to work independently yet collectively and manage the ever-present failure and risk that exists in the IT world. Git coupled with a platform like GitHub offers unbridled benefits. Autonomous development, collaboration, dynamic code merging, scalability and controlled yet seamless visibility are just a few of the reasons for its massive adoption rate and cultural movement.