More information I agree
Code reviews and code standards

Code reviews and code standards

Programmeren

Building sustainable web systems thanks to code reviews

Programming web applications is a team sport. The foundation is created by good internal agreements, laid down in code standards. This is the only way an entire team can maintain a portal or application, and it simplifies (continuous) extensions.

Work delivered is checked against code standards in an automated way through the build server, as well as in a code review performed by a team member. After all, any feedback is processed by the programmer.

What are code reviews?

A code review is a manual check on code delivered, performed by a fellow team member. Basically, it is a peer review completed by a co-worker who checks whether they understand what’s happening in the new or modified code, and if it’s in line with the agreements we’ve made as a team. A code review is always requested before the code is actually added to the web application so as to ensure less errors.

New code is always added through version control: software that provides insight into a web application’s versions. Every time a programmer adds or modifies code, it results in a new version in version control, and a team member is automatically asked to review this new version of the code. It’s very efficient!

Why code reviews are useful

  • The end result is of much higher quality
  • Sometimes, a fresh perspective results in better ideas or a more efficient solution
  • Learning on the job: less experienced team members can also work on this and learn a lot from others in a short time
  • The initial investment of time will result in considerable time savings when new extensions are added in the future

Code reviews enable the members of our programming team to constantly provide each other with feedback. Major benefits are that the web application is of much higher quality and team members reinforce each other

Peter Paul Keulers | IT manager at Way2Web

Code reviews: what do we check?

The main questions are:

  • Does the code contain patently obvious errors?
  • Considering the original requirements, are all assignment requirements met?
  • Does the code delivered match the agreed-upon code standards?
  • Does the set of automated tests need modification, or should it be added?

What does PSR mean?

PSR stands for PHP Standard Recommendation. It’s one of the code standards we use at Way2Web. Meeting this PHP standard means the code delivered matches web standards and is better maintainable. After all, it has a logical setup and is easier to interpret for programmers who were not involved in the original realization. Besides PSR, we also use code standards for SASS, CSS, and JavaScript, among other things. This way, we make sure our code base is sustainable and future-proof.

Are you ready for the next level?

Digital transformation presents fantastic new possibilities and opportunities. Both for our company and yours too. As an IT specialist and entrepreneur, I would like to discuss this further with you, without any obligation, of course. Shall we make an appointment?