I love coding because it allows me to create what I want from my imagination. But it's not fun when software design is more complex and buggy.
Developers need to maintain maintainability by constantly checking the scope of impact when making changes to the code and continuing to test and refactor.
This movement has senior developers who catch the code smells, but it is always difficult to be conscious of impacting code changes.
We should easily know the impacting code changes to support developers.
The slowing pace of development
As a developer, you've probably experienced the frustration of a service becoming more complex over time, leading to a slower pace of development.
Even if it works fine when you add a feature, if the scope of the change is difficult to understand and the design is hard for future colleagues to understand, it will gradually become more likely to break.
Creating unintended relationships in a program is easy, so maintaining maintainability within a team can be a tough challenge.
Developing while looking at the impact map
The Inga plugin's Impact Map visualizes the modules and components affected by the developer's code changes in real-time.
The impact can be checked in the following development phases.
Individual development phase:
By integrating with the IDE, the Inga plugin empowers developers to develop while always being aware of the impact on the internal design. This control helps to prevent unintended negative effects, giving developers more confidence in their coding.
Team code review phase:
Since the team, not the individual, protects the design, reports can be posted to a pull request by CI so that the whole team can check the impact during code review.
Inga will contribute to productivity. If you sympathize with this concept, you can try it out without hesitation, as it is free. Also, since code analysis is performed entirely on the local machine, you can use it with peace of mind. We welcome feedback on both good and bad points. Thank you.
Top comments (0)