One of the annoyances found in the #PHP codebase I'm currently busy with is finding many traits that are used in one single class. Those traits have literally zero other places they could be used at, so... why? Just because someone else did it, you don't have to the same thing. Also, don't do that if you think it just may be needed in the future. Do it only if that's really, really needed now.
@oliver the answer is oftern - bad design. I'm in a similar project, where traits are used to organize common functionality AND to organize different functionality within a single class. The very description shows the issue, but there is some people issue usually to explain why should we go full OOP.
I also click on the "premature optimization"- people don't get it that keeping your impact at any point to the minimum is what business will benefit the most.
Add comment