If you’re a developer, you may be tempted to clean up apex code from time to time. This is because some other developers create what is called “spaghetti code”.
Spaghetti code is basically messy code that may work for a time, but incurs technical debt. It may not follow a recommended development pattern, and may be harder and harder to maintain.
In these cases, developers get excited about refactoring the code to tiny things up.
However, from a business perspective, this is not always a good idea. The investment and impacts may be larger than the benefits.
Consider this: not only does the developer need to update all the spaghetti code, but the QA team has to retest everything. The more you change, the more they need to test.
As a consultant building flows, it’s a good idea to like a developer. So when editing flows, don’t be so quick to replace older portions with newer features (such as the transform element).
Stop for a moment and think of the larger impacts. Keep in mind that every time you change something, the QA team needs to retest what was changed.
The takeaway
Think twice before updating flows. Sometimes the juice may not be worth the squeeze.