Last week a particular topic resonated through the community: the mental toll the different architectures bring on developers. The issue is especially prominent for complex architectures such as VIPER, which is known for having many similarly-named small files per each screen.
shared his experience, which triggered many others to come forward. Dozens of developers shared similar experiences last week.
Any task required routing through six classes, and I found myself physically exhausted when I had to interact with it.
I have struggled with VIPER myself in exactly the same way.
Let this serve as a reminder to all of us. Not that VIPER is a bad architecture pattern, but that architectures are not only about clean code or testability. They’re also about people. It’s us humans who have to be able to understand the codebase, reason about it, and work on it - productively.