So much knowledge not being applied Most organisations have a lot of documents and data floating around that hardly ever gets revisited or used. They all have research, reading, and relevant information collecting dust. Stuff that should be informing the decisions and strategies of the company. Some of it sits unread in a knowledge base or a wiki. Some of it lies in the drives of individual employees who don’t have a way to share it productively. So much knowledge not being applied! Except that’s not how we work as human beings. If you haven’t read it, experienced it, and contextualised it, then it isn’t knowledge to you. Knowledge is a quality that people possess, not documents, and the only way to transfer it from one place to another is for people at both ends to apply themselves and make it their own. Baldur Bjarnason, On online collaboration and our obligations as makers of software knowledgedocumentationwork
Dependence is more profitable than education A customer who pays—in advance—for service contracts is a more stable income source than a customer who has fully mastered a product's use. Customer dependence is more profitable than customer education. What I find truly baffling are manuals—hundreds of pages long—that accompany software applications, programming languages, and operating systems. Unmistakably, they signal both a contorted design that lacks clear concepts and an intent to hook customers. Niklaus Wirth, A Plea for Lean Software The design concept documentation
revisiting architectural blogging An Article by Alan Jacobs blog.ayjay.org I have appropriated from Brian Eno and others the distinction between architecture and gardening, and have described my blog as a kind of garden. But lately I’ve been revisiting the architecture/gardening distinction and I have come to think that there is something architectural about writing a blog, or can be – but not in the sense of a typical architectural project, which is designed in advanced and built to specifications. Rather, writing a blog over a period of years is something like building the Watts Towers. Simon Rodi didn’t have a plan, didn’t even have a purpose: he just started building. His work was sustained and extended by bricolage, the acquisition and deployment of found objects – and not just any objects, but objects that the world had discarded as useless, as filth. You put something in here, then something else, you discover, fits there … over time you get something big and with a discernible shape. Not the regular shape envisioned in architectural drawings, but nevertheless something that can be pleasing or at least interesting to look at – an organic and irregular shape. A geometry of irregular forms. architectureblogginggardens