I think some of these changes in attitude are a natural result of progression as a developer. For instance, when you're just starting out, having a good project manager or business analyst talk to users is valuable, but as you get more experienced you can do a pretty good job of it yourself. Likewise DRY is a good principle to remember when you're starting out, to prevent bad beginner mistakes like writing 1000-line methods instead of breaking the problem down into smaller pieces. But as you get more experienced writing good modular code becomes second nature and instead you become more aware of the cases when the DRY principle gets used to justify over-engineering.