Russell Anthony
Sep 8, 2018 · 1 min read

Thank you for your response Fanis. This brings up a good point that I didn’t mention in my initial post: another huge factor to consider in maintainability is consistency and the precedent set by your team.

Unless the team agrees that an existing precedent is “bad” or wants to try doing something differently, it’s usually best to follow the patterns already set than to trailblaze and do things differently just because you think your way is better. What’s “good” or “clean” is always an opinion at the end of the day, and it’s usually beneficial for us to swallow our pride and do things the way the rest of our team does it, so that it’s easy for any current or future engineer to maintain what we’ve built.

    Russell Anthony

    Written by

    Chief Hasselhoff at Kingsmen Digital Ventures