big red STOP signs
So once upon a time…
I created very complex schemas. I did Databases to 4th or even 5th level normalization. Breaking it of course when needed for speed but always starting out “clean” then profiling once I had the actual data to optimize for performance. And if any one wants to (stupidly) compete on that level… I did EDS style systems with all the funky military codes. And sometimes, I had to deal with people that make it so complex to where a monster was a 27 level table join.
I understand complexity. I understand the basic, sometimes biological, need for it. Yes I used to sort my closet and room obsessively: clothes from shorter to longer while shoes underneath ran in the opposite direction.
When we all started doing computer stuff 20+ years ago, this was completely necessary and was a good thing. But things have changed. It used to be we were programming robots on how to cross the street. We used robots because it was all we had and we could automate them. But robots, well robots are dumb. Sorry I love robots too but they are only as good as we can directly tell them to be. Instead now we have people.
We don’t have to tell people how to cross the street. They won’t read those instruction manuals. For people, we put up a great big red sign that says STOP. That makes them aware of red means danger I should look around access and go on from there.
These new online community groups, need the same. They do not need strict complex schemas. They were break them – even if they understand them. Think normal vocabulary and young people eg urban dictionary. I don’t blame them honestly. I also don’t care if your stuff breaks because of it. I needed to break it – it DIDN’T FIT.
Make things to stretch and break. Make things flexible. Make things simple.
We are creating for people not robots now.
Yes this is why I am a huge fan of microformats.org they are doing a great job of bridging that gap.
o yea and I’m with Jimmy Wales – I hate the term “crowdsourced” implies lack of intelligence and implies business resource. I also prefer Community Created.
![Buffy vs Edward: Twilight Remixed -- [original version]](http://i.ytimg.com/vi/RZwM3GvaTRM/default.jpg)
June 25th, 2009 at 9:32 am
Silona – Would tend to agree with you. Viewing this vast landscape of social media solutions and solution providers one can appreciate the level of complexity that can create paralysis within an organization on direction or even adoption regardless of cost.
I have found there are very simple solutions that can be enabled quickly with ease of use for non-techies (most of the users). True there are limits in some cases to features/functions, design and flexibility.
“Different strokes for different folks,” as they say. Whether you’re American Express or the local YMCA, an organization should begin by identifying its (potential) members’ needs then progress to their wants. Keeping it simple, then, becomes more manageable and less complex.
June 25th, 2009 at 11:11 am
Point taken about artificial complexity. The reason you had to do 27 level table join in the first place is because of limitations in the database system you had use. Relational databases are now so pervasive, they’ve altered the way programmers think about data. Like looking at a cubist painting, data programmers view the world in a tabular format.
But there are places where tabularism (RDBMS) breaks down–it’s not perfectly descriptive. For one thing, it’s not always possible to know the schema before you get the data.
June 27th, 2009 at 5:09 pm
Point taken on crowdsourced; the crowd isn’t a machine, or a resource in the usual sense of the word (“human resources” always made me bristle). Will adjust my vocabulary.
(Community curated?)
June 30th, 2009 at 7:39 pm
Community contributed? the problem is that oftentimes, the contributions are stolen property. To me, this area doesn’t need a new name, since it’s existing for a very long time. It’s called collaboration.
By the way, have you read “The Wisdom of Crowds”?
June 30th, 2009 at 10:19 pm
I haven’t read “wisdom of crowds” but seen his presentation too many times to be able to have the patience to read it. I also remember having problems w it too but too tired to remember them right now. Brain toasty from attending tooooo many thinktanks, conferences and summits right now!