Scout APM helps PHP developers pinpoint N+1 queries, memory leaks & more so you can troubleshoot fast & get back to coding faster. I'm working on a new feature for our Spatie website: I'm adding a lightweight form of gamification for our ±10.000 users.
While you might find it still relatively easy to reason about this isolated (simplified) example, I think most of us can agree that yes, in fact, we're mixing several processes together into one: we're creating some kind of "god-class" that manages and oversees a complex process.
I understand why we get to this point: we'll always need some kind of entry-point in our code, no?
Events introduce an unavoidable layer of indirectness to our code that makes it more difficult to follow the "flow of our program".