I have been doing pair programming for a while, and I would like to share a set of rituals that I use while doing pair programming. They are not the kind with hard boundaries, but you should try keeping the checklist in mind while talking to your pair.

A revision control tool is more than its interface, but also its ecosystem of tools and pool of professionals that can use it, and they play a central role in developers workflow that it affects how they think and work.

This post is a catalog of error handling patterns that I have collected while working with Go. I do not claim these are good or that you should use them. I report them here so as a reference source for debate if you find yourself debating error handling tactic with someone this list is a useful place that you can point to explain what you mean.

If you have been writing Go code, it is very likely that you have written or read a piece of code that looked as following:

These statements are profound. They are usually quoted as pieces of wisdom, in which the authors provide sufficient authority to prevent challenging.

Recently, I decided to embrace minimalism in more aspects of my craft. These are some random thoughts about it and the process I am living now.

I do not want to write a guide or a standard here about PHP programming. These are opinions that I have been thinking of and accumulating for a long time, and are based on experience, thus I hope they will help you about thinking the details of writing PHP code. If you disagree with them or think they are twisting some PHP design decision, fine. But if they spark on the thoughts on why you disagree with me, that is better.