Yeah, I hadn’t heard a name for this concept before, so I just made that one up. It covers things like ‘Persistence Ignorance’ and ‘IoC Container Ignorance’ and things like that.

I think these ‘ignorance’ concepts can be grouped under a single principle which I hastily dubbed ‘Framework Ignorance Principle’.

Framework Ignorance Principal???

Sorry if I’m making a fool of myself but never heard of this one before.

Maybe a line or two on what it is and then maybe I can give a shot at putting in some more research and blogging about it? :)

I want what you’re asking for to be an additional call-to-arms. Established bloggers need to get outside their comfort zone and teach more. We have lots of opportunities for this, whether it’s Agile Austin’s workshops, ADNUG’s Code Camps, etc. It does seem that we are spoiled in Austin with the number of opportunities.

Agreed that blogging is saturated, but it provides a nice first step towards leadership. It’s also a first step in community participation. You have to form an opinion to post (unless you’re a tool shill), so blogging creates a catalyst for critical analysis.

It has indeed all been said before – except for brand new stuff. Even though it’s all been said, it’s all far from understood.

If the communication effort is to achieve its potential, the last mile has to be crossed on-foot, and in-person.

Your TDD coding dojo is an example of what I’m talking about.

Blogging is fine, but it’s saturated. Time to up the ante. What the tech world needed when there were few bloggers was more bloggers. What the tech wold needs now that you can’t swing a cat without hitting a blogger is more teachers. Correction… more teaching. Less blogging, more teaching – even if done on a blog (but better if done out in the wild).