Given, When, Then

Gherkin and other languages and frameworks directed to Behaviour-driven development [2] made mainstream the distinction between the different parts of a test: Fixture or setup (Given); Execution or exercise (When); Assertion or verify (Then). We developers don't like to write tests. We like to write code, real code! When imposed with the need of writing… Continue reading Given, When, Then

Expertise takes time

Once I borrowed a book about Fortran (yeah... I'm that old) and during the weekend I read it and did a few experiments. I was able to do quite a lot with it already.  I have to be honest, it was not my first nor second programming language and it was not that different from… Continue reading Expertise takes time

No Silver Bullet refired

Software development is plagued with the Recipe syndrome: "Please tell me how to do my job". From the utopia of some technology will increase productivity drastically to a prescriptive methodology to make every project successful, everyone is hoping for a silver bullet to kill their beasts [1]. Can the Software Development unpredictability be tamed by… Continue reading No Silver Bullet refired

Legacy companies

Software companies and companies with in-house bespoken software regularly struggle with nightmarish software systems: cryptic monoliths every development team fears and no one understands. Consecutive investments fail to destroy its legacy monsters and to prevent other systems to follow the same path. Legacy state seems an unavoidable progression for software system, except for some "lucky"… Continue reading Legacy companies