On this week's Tech Tuesday, we had the opportunity to listen to our own integration specialist Mikael Drott and his work with generated code. In his presentation, Mikael listed some of the pros and cons of the importance of having a structured source of information as input to a code generator. And the significance of Starlify in the process.
We use our product Starlify to visualize the integration landscape and to store information about it. It contains things like internal and external systems, how one system or service relates to another in a specific flow/integration, IDs and names on everything, etc. This means Starlify is packed with well-structured information and documentation, waiting to get used in other places. But how do we do that? Through code generation!
Code generation is the ability to use data input and create code that you can use in other vital areas of your business. The main gain of generating code is that it will save you both time and money. And it enables you to invest your newly freed resources on more complex and time-consuming things - like integrations. *nudge nudge*.
Mikael listed the most important pros and cons of code generation. Take a look and see if you agree or disagree with him.
Get a "basic flow" more or less directly with new development/migration/rebuilding
Ensures that Starlify IDs are entered correctly into the logging
Standardization: Shared base of code between the teams, and it simplifies for new employees
Reliability
Someone adds support for a new language. And the rest of the developers can quickly start with the new language
Effectivity: Saves time and money which can be used to solve more complex parts of integrations
Support of the code generator itself
Adds a layer of complexity
Control
If you do, don't hesitate to contact us by email or just click the orange chatbox 👋