10 pages tagged with "team-work"

What is pair programming? Let’s first establish what pair programming is: Two people working together on the same problem at the same time. It is not about one person showing off their skills in front of another, nor one person afraid of making mistakes due to an impostor syndrome.

I have heard multiple times, from various people, the idea of panic towards deploying on Fridays. How good is that idea of banning the day before weekend from delivering new value to our clients or customers?

Coding is not just another job. In the right environment, writing software can be really fun and, even more, it can be your personal hobby as well! So… you might be focused on coding, coding and more coding to level up your own career skills.

One of the most complicated challenges for everyone is avoiding misunderstandings and being aware that other people don’t think the same way as you do.

We all have been junior developers at some point. This is easy to know because it is at the very beginning of your carrier. Your responsibilities were narrowed down by other peers who were looking after you.

The term was coined as a metaphor to illuminate Parkinson’s Law of triviality.

People within an organization typically give disproportionate weight to trivial issues.

Dunbar’s number is a suggested cognitive limit to the number of people with whom one can maintain stable social relationships, in which an individual knows who each person is and how each person relates to every other person.

Team Topologies focuses on how to set up dynamic team structures and interaction modes that can help teams adapt quickly to new conditions, and achieve fast and safe software delivery.

Let’s talk about the benefits of Pull Requests and Pair Programming, and my thoughts on these after some years of experience with them.