The bigger problem is that blog posts (usually) don't give you context for their advice. In some cases (eg. trying out a throwaway prototype to determine if Twitter is appropriate for your product), putting Twitter config in a global variable is perfectly appropriate. In others, it'll break production code. Unless the author is very careful to explain the particular situation where he did this and why, it's likely that you'll draw the wrong conclusion for your particular use-case.
