You ain't gonna need what?

One of the defining characteristics of the Rails movement has been its willingness to throw out the rules by which software developers and consultants have typically worked. Those rules typically produce big, overblown projects laden with features that no one ever uses--but which sounded good during the project specification phase. Build the simplest thing that could possibly work, and add features from there; say "You ain't gonna need it" when partway into the project, stakeholders come along with strange requirements based on what they think they might want.

(continue reading)