Like most developers, I occasionally get bemused by some project management strategies; putting the cart before the horse is no exception.
Putting the cart before the horse is an anti-pattern under which features that never need to be built are architected, thus wasting time. The particular setting this annoys me is in technical meetings discussing a long-term technical plan where a project manager will discuss a feature and immediately demand the technical details of how this feature could be implemented.
Firstly, it's important to note that good developers should go away and have research time to come up with a solution. A developer is only made stronger by the ability to research their intended solution, to break out with their development team, to look online for other people facing similar issues, and then to come back with a unified, well-architected solution.
I spoke at the inaugural Lead Developer conference in London, and there was one quote that stood out to...