I think what he’s saying here is that where you look for answers as a developer is heavily influenced by the domain in which you’re operating. Yes, you need to consider “best practices” (groan), and sometimes it’s a good idea to “think outside the box” (wretch), but most of the time you really need to concentrate on what is possible and efficient and makes sense in the current context. This is why when you want to learn about a technology you can read a book, but when you actually have to implement it you end up sorting through a lot of discussion groups and blog posts, and especially blog comments–the ultimate end nodes of the infocloud.

Just a neat blog I stumbled on in an otherwise anxious, code-heavy week of integrating things that were never meant to work together.