Most places I've worked at avoid drift by doing a development refresh from production (with necessary scrambling of identifiers/CC#s/etc, if necessary). At worst, a sprint is only a few changes off from the production version, which is corrected by the next refresh.
I've rarely, if ever, worked at a place where production didn't come down to dev at some point to stabilize drift. Anywhere that was a concern, drift was outright avoided by enforcing the chain of deployment.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA