I think I might have a slightly more apt analogy, though I do understand yours and pretty much agree.
To immediately jump to the "chemical imbalance" problem/solution is like if you have a web app that's performing really slow, so you hire a consultant to take a look.
They tell you that you need to horizontally scale your app in order for it to perform better. In many cases, this would actually work (for a while anyway), but it probably doesn't explain the real issue.
In reality, the problem could be that you wrote your app to do way too many things per request rather than picking and choosing which things are going to be treated as first-class. Perhaps there's even one little thing that's O(n^2) and it simply is going to take a lot of time to work out.
To immediately jump to the "chemical imbalance" problem/solution is like if you have a web app that's performing really slow, so you hire a consultant to take a look.
They tell you that you need to horizontally scale your app in order for it to perform better. In many cases, this would actually work (for a while anyway), but it probably doesn't explain the real issue.
In reality, the problem could be that you wrote your app to do way too many things per request rather than picking and choosing which things are going to be treated as first-class. Perhaps there's even one little thing that's O(n^2) and it simply is going to take a lot of time to work out.