Clean architecture is a software design pattern that separates domain logic from other concerns such as persistence and caching. It aims at keeping the domain objects and domain logic separate from other functions in the system. However, implementing it into actual software projects might cause some issues, like content switching. Context switching is the problem of switching from one task to another task that requires a different skillset or knowledge. It is a common problem when implementing clean architecture. This article explores the bad parts of clean architecture from the authors experience with it, and suggests ways to avoid common pitfalls.
