An object is not what you think it is
Building an object means starting with its behavior. The data it encapsulates is derived from that and constitutes an implementation detail.
Building an object means starting with its behavior. The data it encapsulates is derived from that and constitutes an implementation detail.
When a simple interaction with my neighbor Huguette reminds us that not everything can be understood through technology…
In a legacy system on which many other systems depend, fixing a bug is not always recommended. It’s better to isolate it and keep it.
“Clean Code” is a reference book: reading it cover to cover would make little sense. You need to read it, experiment, and come back to it often.
Looking back on a year of writing: the format that has emerged, the feedback I’ve received, and the deep motivation behind these posts.
You call a library, but it’s the framework that calls you. The difference is inversion of control.
It is, after all, somewhat paradoxical that perfection has become a dirty word. Don’t abandon it, but strive toward it through continuous improvement.
Rather than making estimates, which are as accurate as a broken clock (which is right twice a day), break your work down into smaller tasks.
Engineers, too busy wondering if they’ll measure up, overlook a more fundamental question: What is the purpose of their work?
Bloom’s revised taxonomy offers a detailed description of the levels of knowledge. Here’s a personal example to help you better understand it.
If you’re thinking about creating a custom framework, think twice: some have tried it, and they’ve had their share of problems!
Working on software quality means working on architectures, paradigms, and methodologies, particularly clean code. The programming language doesn’t matter.
A simple account from someone who had the audacity to try to book a train ticket via the SNCF Connect website.
While TDD is a wonderful tool, it is not suitable for all development projects, as it risks falling prey to the “law of the instrument.”
Let the people who use this expression sit down at the keyboard and show us what they can do…
The Mikado Method involves mapping out the dependencies of the refactoring, then refactoring starting from the leaves of the resulting tree.
Whatever your exact role (Lead Dev, Tech Lead, VP of Engineering, CTO…), be demanding but know how to be considerate of your team.
Structural typing is limiting when it comes to defensive programming. Fortunately, it is possible to emulate nominal typing (branding).
A distinction must be made between development errors, which are handled with exceptions, and user input errors.
Separating the IT function from the business units it serves is a fundamental mistake, because IT is viewed solely through the lens of its cost.
No articles match.