Right things done right

We always want to do the right thing right, right? There is only one way to do that, increase the efficiency and effectiveness. First we need to understand the difference between the two, since a lot of people including my past self confuse the two. Even though these work hand in hand one does not imply the other. That is you can have a company which is effective but not efficient.

Efficiency is about functioning in the best possible manner with the least waste of time and effort. It usually can be expressed as a percentage of the input and output. Effectiveness has to do with the end product or result. Essentially being effective is about doing the right things, while being efficient is about doing things right. 


In the above diagram there is only one quadrant we want to be in: top right. It is where right things are done right. I was going to argue as to why it is more important to be effective rather than efficient, because being effective will help you survive. However life is too short for second options, your only option should be to thrive. The main question is how to make sure you get to the top right quadrant as efficient and effective as possible. Then once you get there you need to make sure you can stay there.

The answer probably lies in your processes, tools and resources. The better they are the better you are. However adding processes and tools is a double-edged sword. Adding processes and tools is anti-agile. In agile we should value individuals and interactions over processes and tools. In essence any tools and processes should enhance and enrich interactions and transform people into individuals. Adding more processes and tools will slow you down and probably make you less efficient, but not having any will result in chaos. As always this is a balance of the cost curve against the benefit curve.

I would like to close by proposing 10 guidelines to help increase your efficiency and effectiveness, whether you are a company or individual:

  1. Be honest
  2. Get feedback and stop to reflect – on things you are doing right and wrong
  3. Automate slow processes
  4. Keep it simple
  5. Buy the best tools money can buy
  6. Work with the best
  7. Plan and set targets
  8. Deal with conflict asap
  9. Have fun
  10. Invest in knowledge

Clean Code

You I recently read a book by uncle Bob, which is a must read for every developer. It’s called Clean Code and it completely revolutionised the way I think about code. In particular when coding I am now much more careful about meaningful names, numbers of parameters to pass to a function, the number of lines of code per function, use of comments, error handling and tests.

Why should code be clean?

Before we get to that I think we should start by asking the question what is code? In reality code is just documentation. Yep, that’s all we do, write documentation all day long. More than anything code is the best and most unambiguous specification document of the solution.

We have all been in this situation: It’s the start of a new project and your sprint velocity is really high, you are completing a lot of features per sprint … but then all of a sudden everything slows down. This normally happens because before you write code you need to read the written code. If the code is in a bad state, it is going to take you a lot of time to read the code.


To be honest this is something you can’t avoid. You will always need to read code to write new code. The only thing you can do is make the experience of reading code better for everyone.

What is good Code?

Let us start with an easier question. What is bad code? We can all notice bad code when we see it. Basically its code which isn’t readable. Then, by definition, good code is readable code.

In good code you can read through the code, starting from a high level and going down to the next level. Each level should introduce the next layer of abstraction. When a developer is reading the code he should say: “Yes, this is obvious … yes this is also obvious”.


In the above diagram we see the classical 3 tier architecture however notice that the higher you go the more high level the modules are. The user interface does not know that there is a reporting database, or that for some reason, the photos are not saved with the user data. The user interface just calls some classes from the user and reporting module and displays the data. Also within the actual layers you should start at a high level and to the lower level. Thus the public methods will very high level and the private classes will be at a lower level. The same thing should happen even in the classes. The public methods are at a high level while the private methods are at a lower level.

Let’s Code

Sam had to write some code to get an employee record:

public Employee getEmployeeData(string email, out string error)
  // check email
  if (!email.Contains("@"))
    error = "email is not valid";
    return null;

  // get user by email
  var employee = Employees.Where(x => x.Email == email);

  // check if user exists
  if(employee == null)
    error = "Employee with email: " + email + " was not found";
    return null;
  else if(employee.Count() > 1)
    error = "More than one employee found with email";
    return null;
    error = "";
    return employee.First();

Sam’s code isn’t too bad. However it does have some potential flaws. First of all the method is too long. Its going to take some time to read through it. I also see an example of DRY (don’t repeat yourself). The comments are a classical example. Why did Sam think that writing “get user by email” is more clear then a lambda expression? To me the lambda expression was far more descriptive and helped me understand more what is going on. There is a wrong choice of names. The variable name “employee” is too generic

Method Signature

This is where Tom comes along and sees this code. Obeying the Boy Scout Rule he starts to refactor this code. Let us start by the method name: “GetEmployeeData”. The word “data” seems to be redundant. Everything is data, so we can eliminate that word. The next thing we notice is that method name is a lie. We are not just getting employee data, we are also validating the e-mail. A more appropriate name would be “ValidateEmailAndGetEmployee”.

The next thing is the number of parameters. We should think about who is going to be calling this method. Given that this method is getting the employee by email I would expect to pass the e-mail. However I don’t expect to pass anything else. For some reason the developer is also passing in an out parameter to record errors. In object oriented we have exceptions and these make the code much cleaner.

Helper Methods

The first 6 lines of the method are just there to check the email. So in this case we should split the code into smaller functions. This also help us to eliminate the comments which just make the code longer and more ambiguous.

Final Code

public Employee validateEmailAndGetEmployee(string email)
  return getEmployeeByEmail(email);

private void validateEmail(string email)
  if (!email.Contains("@"))
    throw new EmployeeException("Email not valid");

private Employee getEmployeeByEmail(string email)
  var employeesWhichMatchEmail = Employees.Where(x => x.Email == email);


  return employeesWhichMatchEmail.First();

private void ErrorIfMoreThenOneEmployeeIsInList(IEnumerable listOfEmployee)
  if (listOfEmployee == null)
    throw new EmployeeException("More than one employee got returned");

  if (listOfEmployee.Count() > 1)
    throw new EmployeeException("More than one employee found with email");

I think you agree that this code is much cleaner. First of all the method and variable names describe better what is happening. The next thing we notice is that the first method is quite high level and just contains references to helper functions. The helper functions keep on decreasing the abstraction and going down to the implementation. Like this the developer reading the code can immediately assume what every method is doing.

Okay… I think that is too much information in one post. Basically we briefly discussed the following topics:

  1. Why we should invest in clean code
  2. What the bad code looks like
  3. Boy Scout Rule
  4. The proper use of function and variable names
  5. Using comments
  6. Helper methods
  7. Error handling

Till the next post go to Amazon and buy the book.