Ostoskori 0

Code review

Don’t bin your code if you can still fix it! Conducting a code review allows you to bolster your technology and spot weaknesses in time.  

Each row of code is one more row in need of maintenance. Do you know what your code actually contains? 

Organising a code review provides assurance regarding the state of your company’s technology and enhances software maintenance, performance, reliability and security. In other words, a code review provides an opportunity for spotting the proverbial low-hanging fruit – and picking them for future use.

 
 
 
 
 

When should a code review be carried out?

A code review is needed when the state of the codebase is unknown. This can happen in connection with:

  • mergers and the need to ensure technology compatibility

  • receiving a legacy system from another operator

  • a decline in system knowledge and management

  • losing a critical supplier or expert

  • a desire to move the system to the cloud without knowing if it’s a financially smart move 

  • wanting to find better ways of meeting the needs of customers and end-users

  • a need for external insights, ideas, support and skills.

 
 
Rakettitiede-violetti.png
 
 

What does a code review include?

Rakettitiede’s code reviews assess the client’s native software and technology platform. 

A Rocket architect and the client carry out discussions to uncover any risks and development potential related to the systems. The focus is simultaneously on the details and the whole as well as the architecture and lifecycle – not to mention business-related aspects. 

A code review can be organised at the low price of €5,000 excl. VAT.


Focus on critical questions

Rakettitiede ikoni

The purpose of a code review is to find answers to business-critical questions, not to carry out an evaluation from A to Z. 

A typical review will include the following:

  1. Outlining of questions

  2. Investigation

  3. Recording observations

  4. Discussing the observations; and 

  5. GOTO 1.

Most reviews are carried out in week-long cycles. Keeping a leisurely pace is important, as this gives the client time to react to observations and manage any issues.

Observations and proposed actions are documented continuously, not in a separate final report. 

The client applies the results either independently or with a partner of their choosing. Any operator can be employed for making subsequent changes.

 
 
 
 

Don’t bin your code if you can still fix it – contact Rakettitiede for a maintenance plan!

 

Marietta Johansson

Rocket Accelerator
+358 40 520 3100
marietta@rakettitiede.com

Timo Jaakola

Rocket Accelerator
+358 50 540 0230 timo@rakettitiede.com

 
 

Drop us a line or two – we’ll respond at the speed of a rocket

 
orange-banner.png