I stated that they are good jumping off points to use, especially early in prototyping, but they should not be relied on too stringently or dogmatically, especially as a project evolves and has its own unique blend of requirements. Patterns are a source of perspectives and potential learnings (understanding why a pattern exists usually points out shortcomings of a corresponding anti-pattern), but need to be taken with a grain of salt.