Engineering Excellence

Engineering Excellence (EngX) is both a culture and a collection of best practices, processes, and tools that facilitate [fəˈsɪlɪteɪt] the success of software development projects and improve the quality of the solutions that teams deliver to clients.

By the end of this series of articles about EngX, you will be equipped to:

• Identify the characteristics, behaviors, and motivations of an Agile engineer and the actions required to build an EngX culture
• Determine how your team and projects can benefit from committing to Engineering Excellence
• Identify the risks to a project of neglecting EngX practices, processes, and tools
• Recommend ways to implement the EngX practices, processes, and tools for a project

Hope you enjoy the journey!

Agile Fundamentals

Agile is a value-driven approach to developing solutions. It is focused on people, adaptability, and providing maximum value to customers.

Code Review

Without a code review process in place, our team might miss critical information and business logic, which can lead to rework and impaired code quality. However, if code review is introduced as a regular practice, it will enable effective knowledge sharing among our team members, help grow technical competence, and improve functional and structural code.

The Benefits of Code Review:

• Fewer Defects
  • Reviewer as an outside perspective to identify structural errors and functional errors
• Knowledge Sharing
  • Knowledge sharing guarantees all team members are on the same page and strengthens positive communication and cooperation.
• Consistent Standards
  • Consistency in a codebase makes code easier to read and understand, prevents bugs, and facilitates collaboration between regular and migratory developers.
• Compliance(合规)
  • Easier for the security specialist to check whether the code meets compliance requirements

Structural errors: dead code, logic or algorithm bugs, performance or architecture concerns, etc. Functional errors: when code does not work as expected

To experience the benefits, it’s important for your team to spend time on the process and follow code review tips and best practices.

The Risks of Neglecting Code Review:

• Lower Structural Code Quality
• Lower Functional Code Quality
• Lack of Knowledge Sharing
• Possible Rework
• Possible Technical Issues