Tag: collaboration

What is the purpose of this code?

There are only two hard problems in Computer Science: cache invalidation and naming things. – Phil Karlton We name and name and name. We name variables, functions, arguments, classes, source files, and the directories. Proper naming makes the code easier to read. Intention-revealing names The right name tells you why the variable, function or class

Continue reading

Who do you write the code for?

You can probably come up with a bunch of answers: the computer, the client, the cloud, the company… But first and foremost you write code for other developers. And for your future self. I mean, the computer will understand anything you write (as long as it compiles). And it’ll behave in the exact way you

Continue reading

A bunch of individuals doesn’t make a team

A team sport Last year I’ve finally obtained the certificate of competency authorizing me to operate sailing yachts so I’ve spent a part of my long vacation on a boat. I love sailing. Sailing is pretty much about the experience and learning the right skills. Every moment on the water is different, and it’s important

Continue reading

If you were hit by a bus tomorrow would your project be dead in the water?

If you were hit by a bus tomorrow… If you were hit by a bus tomorrow (knock on wood) would your project get stuck? I still remember when one I worked on did. Well, I wasn’t exactly hit by the bus, but from the project standpoint, it was close enough. We worked on an important

Continue reading

What should you know about a human side of code review?

Imagine yourself sitting in front of a compiler, tasked with fixing a small bug. But you know that as soon as you say “I’m finished,” another developer – or worse, your boss – will be examining your work. How do you feel? Anxious or encouraged? As software engineers, we take pride in our work (as well

Continue reading

To meet or not to meet? Understanding the hard language of expectations…

Recently I wrote how to deal with requirements in the process of a software development. Requirements are often customers expectations but those aren’t always the same. And not only your customers have expectations. In reality, every person included or interested in a software project has her/his own interests and expectations. And even as a simple developer you

Continue reading