Have you ever gotten stuck while writing a particularly complicated piece of code and figured out what was wrong at the exact moment you asked a colleague for help?

Explain your code to a duck (if it’s made of rubber, it will always remain handy on your desk) and your ideas will catch on quickly.

It may seem strange but if instead of reading the code over and over, you tell someone about it, your brain often reveals the mystery. The idea of ​​explaining the code to a rubber duck was popularized by the book “The Pragmatic Programmer”. The method works. This explains the logo.

But, what prompted us to create a site that encourages you to talk to a duck? We made several observations:

  • We often come across code that is not updated with respect to the article that explains it
  • In many cases, the projects associated with the articles do not have tests.
  • The quality of the code is a little known or neglected argument in favor of different factors that are almost never justifiable in rational terms.

The main idea of this site is therefore to present articles and methodologies which will be associated with projects with the same quality that is required of us in our work and to keep them up-to-date.

By extension, the idea is also to present articles about our job as developers and maybe even to present some books that we particularly liked.

The arguments reflect only our opinions and our way of doing but it is always our point of view and we are willing to change them because to progress you need to know how to listen and understand the opinion of others and accept that there are different ways of doing.


How to Evolve an Application to Make It More Robust and Maintainable - Setting Up the Test