So you have adopted agile at some level of your organization, that’s great. How do you think you are doing? Many organizations implement agile process without a way to gauge its effectiveness.
Being a bit of a process geek, I was excited to read Jake Knapp’s new book, Sprint, which covers the refined innovation approach that is used at Google Ventures.
Having worked on the creation of digital and also physical solutions, I was intrigued at Nir Eyal’s book, Hooked, which is about hoe to build habit forming products.
I’ve been a fan of Charles Duhigg since hearing him on the Entreleadership podcast talking about his book, The Power of Habit, which I thoroughly enjoyed.
Business travel is far from glamorous. It’s a big collection of frustration and unpredictability. This story is just one example.
At its core, an organization that is successful at DevOps is one that has mastered the science of automation. The first core tenet of DevOps is directly connected to this automation process, Infrastructure as Code.
Defining What DevOps is not can provide some clarity and perspective on the topic and help you better understand what DevOps is.
DevOps is a set of best practices for collaboration and coordination between development and operations to enable continuous delivery. What is continuous delivery? I'm glad you asked.
I've ran across a few books that excelled at making me a better developer, irrespective of a specific technology. The kicker is that some of them weren’t even directly about development.
Every minute of the work day is an opportunity for investment for us as developers. During this time, we can make a conscious decision to grow in our craft or instead chose to stagnate.