the right audience
15:56 < bmmpxf> dwins: iwilling and I are still having trouble getting the data in the postgis. please stand by. 15:57 < dwins> bmmpxf: what sort of trouble? should I lend a hand? 15:59 < bmmpxf> dwins: Just trying to avoid typing in the password lots of times 16:00 < dwins> bmmpxf: parens to the rescue 16:00 < dwins> (for file in *.shp; do shp2pgsql $file; done) | psql 16:01 < dwins> man I love punctuation
I think it’s just that I picked a book that was written for non-developers (from the preface: “We’re geeky, so you don’t have to be!”) and so dumbed things down a bit much. I didn’t immediately put it down because, hey, I want to be able to explain things to non-developers too! But after spending forty pages with half-a-dozen sidebar notes saying ‘sorry we included Hello World as an example in a programming text’ and ‘html is a thing you can write in any editor, but don’t use Word!’ I was a little overwhelmed. Why not just skim, you ask? This particular book has so few words per page that I found skimming pretty frustrating, it just didn’t work for me.
So, moral of the story: if you read something that’s written for a target audience that clearly doesn’t include you, you’re probably going to feel like you’re going against the flow. Similarly, if you’re writing a thing (as the OpenGeo team is right now with a serious reworking of the GeoServer documentation) you’re throwing away a lot of your effort if you don’t have the right audience in mind.