Disclaimer The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.
Lately, I often find myself repeating a little mantra:
Keep it simple Keep it simple Keep it simple
Ohhhhmmmmmmmmm.
This usually happens when it's too late, when I'm bogged down 5 layers deep in SQL or CAML, when Ive spent 3 hours googling for a solution to a problem and only found half answers in Polish.
Some observations:
I'm working towards a point here so stick with me. I'll be more specific. SharePoint.
SharePoint is big. Really big. "So big that you can't even imagine it" big. It's not bad, just big. Big things tend to be more complex. Complex is harder. Harder takes longer and therefore costs more.
At the other end of the scale is NotePad. Anyone who can use a computer should be able to use NotePad. It's functional, uncomplicated, stable(?) and I think elegant.
Here's some more observations:
My point is this. We should not be scared of complexity. Simlicity is an admirable goal but not when its at the cost of solving a problem. We need a way of managing and dealing with complexity. I'm sure there are many people much smarter than I devoting themselves to exactly this problem, but here is my small contribution.
My 20 Minute Rule
You can adjust the time up or down to suit, but my 20 minute rule is this: If I can't figure out how to use/do something in 20 minutes - without a manual - then it's too hard or complex.
This doesn't mean I give up, it just means I need to learn more before attempting it again.