Every engineering organization faces the same fundamental question: how do we balance speed with safety in our development workflow? GitFlow promised us structure and predictability. Trunk-Based Development promised us velocity and simplicity. Yet most engineering teams I met find themselves caught in an uncomfortable middle ground…
The journey of a startup studio developing its first product while bringing to life an MVP delivery system expected to be lean and fast. A set of lessons learned and anti-patterns collected from the trenches of building a product from scratch. Finally, the realization that in scenarios of extreme uncertainty, money and time shortage, no legacy, and few early adopters, can lead to counter-intuitive actions that will help you fly. This will either broaden your perspectives or drive you insane.
Every year I look forward to judging on the national tournament for the FIRST® LEGO® League (FLL), a robotics program designed to get kids excited with STEM. I always get more than I give back and somehow this contagious energy ends up loading my “batteries”. However, by the end of the day, via a stressful scoring process, there is a clash between Meritocracy and Pedagogy that drains all the energy.
Outsourcing capacity planning increases business responsiveness by taking out complexity and reducing IT spending.
Over almost 20 years, I have been involved in a multitude of software development endeavors. Out of sheer luck or just time passing, together they seem to show an “evolution“ worth sharing. Even if not systematic and according to a scientific process, experience does provide insight and I hope lessons to be learned.
With a year rich in cyber security threats and a growing bubble for ransomware and IoT-driven DDoSs, insecurity is on the rise. Three steps to help you set the direction towards a more secure organization providing the tone for the tactical decisions that will need to be made along the way.