Broken by design, bug or feature?

Categories: it
Perhaps you’ve already encountered this: a user complains about a bug of their favourite (or not) software, a developer states that it works as designed and declares it to be an enhancement request, the user is angry, because it’s "obviously" a bug and not an enhancement, how can any sane developer think that such a behavior is normal? Starting from there, the situation can escalate at will between user and developer, each accusing the other to be a clueless nincompoop.

Read More →

Why not rename master?

Categories: it
There is a current trend to rename all master branches in Git to main or something similar. I’m reluctant to follow the trend. Why? I understand the idea behind, that it is a reminiscence to some of the master-slave relationship, and renaming master into something different is a sign of solidarity. So far so good and I could live with this. The issue is that there are more than one meaning to the word "master".

Read More →

Fluidifying one’s IT, to not say make IT agile

Categories: it
IT consulting is an interesting job because you meet all kinds of companies, and can compare them. My job is also to analyze and improve them, in my case with means of Open Source and automation, but that’s another story. Anyway, most customers I encounter are suffering of a lack of agility because of too many processes, constraints, regulations, etc. Here you can talk ITIL, security and compliance, approvals at each corner of each process, etc…​

Read More →