Brilliant thought and aptly named and described. Amazing how naming a concept can clarify it immediately.
Interesting middle ground:
- Internal wikis that require a request be sent to the owner for an account. Please justify why you want to able to write to this wiki.
- Workers just daring enough to create wikis, but not enough confidence to improve them with their daily gleaned nuggets.
- Internal web with documents and articles, but no search capability.
My old basketball coach used to call this “day late and a dollar short”.
Larry O’Brien’s response is completely appropriate, so I link to it rather than the original post. If you’re older than 30, then you can identify with this…
One of his primary jobs was to challenge the team to sign up and commit to aggressive schedule and scope targets that would meet the customer needs. His behavior was very much aligned with a contract negotiation stance. Get them (the team and me) to commit to a goal (the contract) then come back at the end for the prize (delivery). The middle game was simply wrapped around the details and not of much interest to him.
Very nice observation in this little gem about Transparency…
Scott Meyers published a short and succinct guideline on an aspect of interface design. One nice thing is that the design principle that he describes can be applied to C++ class interfaces as well as user interfaces and he gives examples of both.
