When a team of developers works on projects, they need to agree on code conventions, standards, best practices… Wait, do they have to? What are the developers giving up on in order to deliver uniformly-formatted code? In this post i defend the idea that code conventions and standards come with a high price, and that there might be a different way of working together.
It’s an accepted trend nowadays: according to many TDD and BDD are useful tools with many advantages, and to others they are not. In this post I will not start that old debate again. I will however expose to you one great, possibly overlooked advantage in having extensive test/behavior/specifications coverage: a better team collaboration.
As developers, we strive to write the best code in the shortest time possible. However our work environment itself can sometimes prevent us from reaching those goals…
You know how it is: you go to pull the latest version of the project, you run the application and… nothing works anymore! One of the latest commits broke the application, and it’s not as obvious as a compilation error… Love is NOT in the air!