// articles
The logbook
Field notes on software engineering, automation and quality — gathered across my assignments.
11 articles
Workbench: my Swiss Army knife for killing repetitive tasks
Workbench is the tool at the foundation of my whole internal-tooling approach. A single graphical interface that gathers the day-to-day repetitive actions and replaces a handful of tedious commands with a few clicks.
Read the article→SonarQube: Mastering Quality and Technical Debt
In sectors where reliability isn't negotiable, how do you make sure hundreds of thousands of lines of code meet the highest standards? SonarQube has become an essential ally on my projects.
Read the article→GUIs vs. the Command Line: a Case for Pragmatism
The command line is often worshipped. Yet in some critical contexts, a well-designed graphical interface drastically reduces errors. Why PyQt is my go-to tool for building these interfaces.
Read the article→Automated Testing: From Unit Tests to Non-Regression
A solid automated testing strategy is the only way to guarantee that a change doesn't break existing behaviour. How to structure your tests to ensure stability and quality on every commit.
Read the article→Fixing Bugs: When Debugging Becomes Rewarding
Ask a developer about their most frustrating task, and debugging often comes up. Ask about their best professional memory, and they'll tell you how they cracked that bug that had been taunting them for days.
Read the article→From Requirements to Solution: the Art of Specification
A clear specification is the cornerstone of a successful project. How to turn a vague business need into measurable technical requirements, and why this step determines the final quality of the software.
Read the article→From Code to Business Understanding
A true software engineer doesn't just write code. They start by understanding the business, the system, the end goal; this approach is what turns a developer into an architect of reliable solutions.
Read the article→In Praise of Laziness in Software Engineering
We picture the good developer as tireless, coding for hours on end. I believe a form of intelligent laziness, an aversion to unnecessary effort, is actually one of the best drivers of software quality.
Read the article→Automate to free your mental bandwidth
Why I systematically automate the repetitive tasks of my projects: less mental load, fewer mistakes, and more time for the engineering that matters.
Read the article→Continuous integration: from GitLab CI to Jenkins
Setting up robust continuous integration in an industrial environment, whether with GitLab CI or Jenkins, without needless complexity.
Read the article→Small internal tools that change everyday work
Over my assignments, I have built small internal tools that save time for the whole team. A look back at this tooling mindset.
Read the article→