Methodology

Methodology

The case for writing (isolated) test cases #3

Divide and Conquer Since three out of four small businesses fail, my recommendation is to start a large business. Legacy Code and SOTA "Legacy code" is often used to characterize old software systems inflicted with a crucial maintenance debt that accumulated for years. But legacy code can happen very soon in a project. The best intentions, plus a misaligned or degrading SOTA (State Of The Art) can change your greenfield project into a legacy code factory in a matter of 3 to 6 months, before…

Lire la suite
Methodology

Le refactoring c’est tout le temps, et c’est normal. (épisode 3 – appel à un ami)

Trop de doutes, Charlotte a besoin de conseils. Marc est indépendant, il est très fort techniquement et très gentil, ça va bien se passer c’est sûr. Elle a toute confiance.  « Marc mon ami, tu pourrais me faire une revue de code ? « J’ai beaucoup avancé et j’ai besoin de tes feedbacks pour continuer.  « Je me pose quelques questions sur des endroits bien précis, mais le mieux je pense c’est que je te laisse regarder. — D’accord, pas de soucis, je regarde ça.…

Lire la suite
Methodology

The case for writing (isolated) test cases – #2

What is legacy code? "Code without tests is bad code. It doesn't matter how well written it is; it doesn't matter how pretty or object-oriented or well-encapsulated it is. With tests, we can change the behavior of our code quickly and verifiably. Without them, we really don't know if our code is getting better or worse.” “To me, legacy code is simply code without tests.” Michael Feathers, Working Effectively with Legacy Code "The code has no tests." Such a report often strikes me as a…

Lire la suite
Methodology

The case for writing (isolated) test cases – #1

Should we write unit tests or integration tests ? "There is hardly anything in the world that someone cannot make a little worse and sell a little cheaper, and the people who consider price alone are that person’s lawful prey. It’s unwise to pay too much, but it’s worse to pay too little. When you pay too much, you lose a little money — that is all. When you pay too little, you sometimes lose everything, because the thing you bought was incapable of doing…

Lire la suite
Methodology

Breaking down Continuous Delivery on Power BI

Context In this blog post we want to share with you how we implemented DevOps practices in a data visualization tool (Power BI) during a delivery project. What was the aim of this project ? To make it short, we had to automate the process of collection, transformation and visualization of the data for a large organization with entities spread across the world. The foundation has to be built using software craftsmanship practices leading to a cultural change in the development process. The output was…

Lire la suite
Methodology

Super Apps development model explained !

Introduction If you ever stumbled, lately, on a tech article talking about Super Apps, it would probably mention that they were first invented  in 1999, by Mike Lazaridis, the founder of Research in Motion (RIM), the manufacturer of the BlackBerry device. Mike has defined Super Apps  as applications which make use of all the BlackBerry resources available. From usage of notification pop ups, context menu integration right down to being able to access any application from within anywhere on the device. Deep integration across the…

Lire la suite
Methodology

SLO: The unexpected power of metrics

When operating a product or building an infrastructure, it is normal to ask yourself the question "Is my application working well?" In general, it is common to have two answers in these kind of cases:  Use monitoring to check if the application is working properly. Set up an alerting system to be aware of possible problems in the system However, we rarely wonder if alarms are relevant in my specific context (ex: when a container restarts) or if the metrics on my pre-made dashboards will…

Lire la suite
Methodology

A Journey To build a Business-Driven Data Science Capability

Introduction We live in a world in which data is becoming a key business asset, playing an increasingly central role in the success of a growing number of companies. Data and the ability to transform data into business will become critical in all sectors in the coming years. A good mastery of data and its exploitation can be an important competitive advantage. This means that companies need to equip themselves with the technological and human resources to develop a skill set capable of leveraging data,…

Lire la suite
Methodology

New Year’s Resolutions: Shed those excess pounds (from my Google inbox)!

TL;DR → Smart links to quickly clear out your Gmail inboxes Do you know your Do you know your current GMail storage usage?   How much is dead weight? To ring in the new year, I decided to finally buckle down and clear out my GMail inbox. I spent a total of 10 minutes and, just by cleaning out old emails, my inbox dropped from a size 16GB to a mere 4GB!  There are more than 650 people at OCTO. If we all do a little…

Lire la suite
Methodology

Thoughts about Scaled Agile Frameworks and how to consider them

Comment choisir son framework d'agilité à l'échelle ?

"What if we scaled agile to the entire company..." This is a phrase heard more often than not in companies that becoming more mature at Agile. But what does this sentence mean exactly? What does the idea of ​​"scaling up" imply? Are there solutions that can be applied quickly? Quick overview: Did you say Scaled Agile Framework? What triggers an Agile transformation "at scale"? SWARMing, what is it? A strategy for using scaled agile frameworks ==> Read the entire article (free) <==

Lire la suite