Sometimes complexity is needed. I've worked on too many projects where it's just do whatever is easiest at the time to get it working ASAP. This works, for a w

Sometimes complexity is needed. I've worked on too many projects where it's just do whatever is easiest at the time to get it working ASAP. This works, for a while, but eventually that code base that no one really put any thinking into around design turns into a tyre fire. Maintenance becomes hellish, extending it becomes hellish and error prone. Finding and resolving bugs become excrutiating. So when people go for a more complex solution up front, it might not be complexity for complexities sake, they might actually be able to forsee issues in the future and want to avoid them. I wish more software development projects employed front loading the effort, either in terms of design / architecture / employing some sort of code analysis / quality control etc or even just thinking. Especially thinking. If the result of that thinking is more complexity, then it's fine. You're introducing complexity early, everyone can get used to it because it's going to make your lives in the future easier.