Clean code: Why and how?

by Gorka Guridi

Clean code does not just refer to the aesthetics of the written code. Writing bad code delays the project deliveries, increases the budget for bug fixing and over time can create problems where shouldn't be any. Writing a good and clean code can improve the stability of the software, increase the reusability of the code and make developers work as one. Clean code is the monkey wrench of team performance, settling up the bases to decrease the effort of understanding the code written by others (and yourself).

We will try to cover why clean code is important, what are the properties of a clean code, small concepts to help to achieve it and some tips based on my experience as developer.

Drupal level: Intermediate, Language: English

About Gorka Guridi

Organization: Cameron & Wilding Ltd.

Profile on

I started working with PHP around 2004, around the time PHP 5 was released. After working on several proprietary frameworks joined the Drupal community on 2010. I started developing websites for agencies, and growing in experience until I got the opportunity of moving to Philippine to be in fully charge of the asia websites development of a betting company. Early adapting OOP principles to develop custom modules and code integration over Drupal, mixing up the advantages and stability of the CMS with the flexibility, reusability and atomicity that OOP approach provides, creating wrappers to help the team minimising the duplication of code and increasing the unit test coverage of the solution. Currently based in London (UK) and working for Cameron & Wilding Ltd. as a Drupal Architect/Technical Lead. My focus is to architect new website solutions, organising teams and ensure the quality of the code, deliverables and processes.