FoodLogiQ Software Engineer Publishes Book, Provides Expertise on Continuous Integration and Delivery
In our new blog series, “In the Spotlight,” you’ll meet many different FoodLogiQ team members who play an important role in our company’s success. Our first spotlight is on Jean-Marcel Belmont, a software engineer with a passion for automation and continuous integration. He is heavily involved in the open source community and frequently writes workshops on many different software development topics. Marcel maintains a couple of meetup groups, where he advocates clean code patterns and software craftsmanship.
A. The terms ‘Continuous Integration’ (CI) and ‘Continuous Delivery’ (CD) are often used when people talk about modern software development practices. CI puts a great emphasis on testing automation, requiring developers to send their code into a shared repository several times a day. That code is verified by an automated build, which is basically a test that allows teams to detect code problems early. At the end of the day, CI makes preparing for a software release much easier.
CD is an extension of continuous integration, as it ensures that companies can release new changes/updates to their customers quickly and in a sustainable way. This means that on top of having automated testing, you also have automated your release process and you can deploy your application at any point in time with the click of a button.
In theory, with continuous delivery, you can decide how frequently you want to release software updates, whether daily, weekly, or monthly. The problem with longer deployment cycles is that customers have to wait longer to see the new features in a software product and provide their feedback. In turn, developers must wait to hear from customers about whether the new features they are delivering are actually adding value to their customers.
With more frequent deployments of software, we can more quickly see if what we delivered feature-wise is useful. So to put this in perspective, if a developer works on a new feature in a three-week sprint, and then it gets deployed a couple weeks afterwards, the developer usually gets feedback about a week after the deployment. In total, that’s a six-week feedback loop to see if the developer delivered value.
Q. Packt Publishing approached you about writing this book. How did that come about?
A. Packt Publishing is the leading UK provider of technology eBooks, coding eBooks, videos and blogs; they specialize in helping IT professionals by providing them with effective learning tools and resources. Packt was looking for an author to work on a book project about CI and CD in order to help their readers understand continuous software delivery, and they had seen other pieces I had written and thought I might be interested. The writing and publishing was a six-month process, but it was very rewarding when I received the finished copy of my book.
Q. Marcel, what is your “Personal Why” for working at FoodLogiQ?
A. I work at FoodLogiQ so that I can use my talents to positively impact the world’s food supply chain. I do that through the use of software engineering best practices and development, and I like to share what I’ve learned with others.