While I completely agree that micro-optimizing microseconds early on is bad, we also have to be careful not to use 'premature optimization' as an excuse for writing sloppy code. There's a big difference between premature optimization and basic developer competence. For example, avoiding an obvious N+1 query problem or selecting only the database columns you actually need isn't premature optimization—it's just knowing your tools and avoiding obvious architectural waste.