Just like a salami: go slice by slice!
Switching to a new programming language is usually a difficult decision for a company. It is a painful process, it might be expensive and time-consuming and, if wrong decisions are made, you might come to a deadlock. On the other hand, there might be significant benefits in the medium term, for example, more satisfied developers, quicker and more efficient development projects, a better rate of return.
Technology switch projects are usually initiated by developers, whose work is made more difficult by the old system over time, so they do not like it. It frequently happens that there is no up-to-date documentation to the technology, old documentation needs to be dug out, or the technology is simply not supported any more. This makes it difficult to change a code, and modifications often break something else. It is not effective, and, on the other hand, might be very frustrating for the developers. In these cases mostly the technology switch is the best solution.
Although it might be an attractive solution to re-write a previous application from scratch, my experience shows that this is one of the biggest mistakes you can make. It is incredibly time-consuming to re-write a 5- or 10-year-old system, you might be almost sure that something will break, and the new system will know less. The old application – despite all its faults – is well-tested, has many features and is impossible to be reproduced within a few months.
So, instead of throwing out the whole system, choose a precisely defined feature, and re-write it with the new technology in a way that fits the other elements of the system. Moreover, it helps us to validate the new technology: What are the advantages compared to the previous system? How much quicker will this function be? How much will the quality improve?
If the first function had been successfully re-written, you may start with the next one. Just like cutting a salami, you re-write the system slice by slice. By the end of the project, only a negligible part of the codebase will have the old technology.
It makes sense to start the technology switch with a feature that:
So you will not only start the technology switch, but you will also make an outdated function more user-friendly – which means that you will enhance the value of the product.
Before you start re-writing a function, create an architecture diagram which shows how the system is constructed, what the main components are and which parts are affected by the technology switch. In the next step, check how the other parts of the system will connect to the new technology.
This knowledge is often missing at companies. In most of our previous projects, we were asked to help in connecting the old system to the new technology.
In my next article I will list the aspects that need to be considered when choosing the new technology.
Download our related case study that describes a technology switch project.
A Green Fox mára erős nemzetközi vállalattá vált és regionális IT talent poolt épít. Nemzetközi képzéseket indítunk és országhatárokon átnyúló lehetőségeket biztosítunk hallgatóink, valamint vállalati partnereink számára. Csehországban és Szlovákiában piacvezető szerepből építkezünk tovább.
A technológiai trendek által előidézett iparági változások a kihívások mellett lehetőséget kínálnak a vállalatok számára, hogy növeljék bevételi forrásaikat. Ahhoz azonban, hogy az élen maradjanak, a szervezeteknek lépést kell tartaniuk a fejlődő technológiával, alkalmazottaiknak pedig a szükséges készségekkel.
Would you like to know our partners better, where you can even start your new IT career after the course? We have great news then! We sat down with Aliz's Community Manager, Petra Palotás, and asked her what kind of workplace Aliz is and why it is good to work there. Read our article and get to know Aliz!
The popularity of low-code platforms is increasing in the whole world, and the demand for experts in this field is growing rapidly. Nikolett Tarjáni-Dobos left her dietician career to become a software developer and has been working as a low-code programmer in Germany for almost 2 years. She first heard about this field when she was looking for a job. Yet, she now feels lucky that this became her new career. But what does a low-code developer do and how does a working day go? We asked Niki about these topics as well as about the misconceptions around low-coding.
The benefits of low-code, or platform-based development are widely recognized by more and more companies, however, there are still many questions around the technology. That’s why we organized a roundtable session where we discussed the platform’s potentials, including the fact that low-code can be the perfect entry point to an IT career.
How is it possible to give more impetus to IT development and HR processes at the same time, even though this field is understaffed? How can you fill the gap when you need specialists of a company-specific technology who are ready to join a project as quickly as possible? The corporate bootcamp, which provides specific skills in close cooperation with a company, responds to these challenges.
The pressure for growth experienced by IT companies is now having an impact on the labour market. The active involvement of women in the IT sector can not only play an important role in alleviating skills shortages; it can also contribute to the development of a more diverse workplace, stimulating teamwork and productivity.
In cooperation with our corporate partner, Morgan Stanley Budapest, we are launching an exceptional scholarship program in April 2022. Within the framework of Java Academy corporate boot camp, we are choosing 15 talented students interested in Java and server-side programming and giving them the chance to restart their careers as back-end developers – for free.