Auto increment is a no-no?

Hello. I must confess that I am rather new at this. During my courses, I was taught to place an auto increment as an id field in my tables, when in need to.

However, recently, I heard someone comment that this is to be completely avoided. But I do not understand why. Perhaps anon could point me in the right direction?

>>7
Natural keys are elegant solutions only on homework assignments.
In real life the requirements change halfway through the project, and they end up causing you more work while providing no actual benefit.
As a bonus the insertion order is very often useful.

>>7
Back to your college SQL class, please.

>>7
Surrogate keys are a symptom of bad design.
Really?  Because I can't think of any better solutions for implementing Enterprise-grade applications such as Shiichan, MOTHERFUCKER.