> choosing a specification that actually solves the problem without generalizing or over-architecting the solution I would not call it over-architecting, if yo

> choosing a specification that actually solves the problem without generalizing or over-architecting the solution I would not call it over-architecting, if you sacrifice portability, maintainability, *-ility too much. What exactly is "too much" depends of course.