A few things that could be poetry An Article by Wesley Aptekar-Cassels notebook.wesleyac.com The right combination of street signs, viewed from a artful vantage point Words on bit of packaging, torn to reveal and conceal as needed The output of a command line tool, perhaps unexpectedly Overheard words, drifting along, liberated from their initial context A form, at first appearing bureaucratic, revealing humanity on deeper reflection An idea, if you consider it divine enough poetrychancewordseuphony
Rewarding Curation An Article by Wesley Aptekar-Cassels notebook.wesleyac.com Something interesting about the design of Twitter is that it doesn’t have much of a way of rewarding curation, only authorship. ...I’m inclined to think that the mechanisms of distribution of information are very important, and I think figuring out ways to reward good curation is probably an important thing. ...I don’t really know what the solution is here, but I do think that finding and curating good links and bits of information is useful, and something that should be rewarded more than it currently is. organizationcollectionscontent
How Websites Die An Article by Wesley Aptekar-Cassels notebook.wesleyac.com I recently started compiling a list of defunct blogging platforms. It’s been interesting to see how websites die — from domain parking pages to timeouts to blank pages to outdated TLS cipher errors, there are a multitude of different ways. It leaves no sign of its past self behindThis obsession with permanence
A grossly obese set of requirements Who advocates in the requirements process for the product itself—its conceptual integrity, its efficiency, its economy, it’s robustness? Often, no one. As often, an architect or engineer who can offer only opinion based on taste and instinct, unbuttressed as yet by facts. For in a classical Waterfall Model product process, requirements are set before design is begun. The result, of course, is a grossly obese set of requirements, the union of many wish lists, assembled without constraints. Usually, the list is neither prioritized nor weighted. The social forces in the committee forbid the painful conflicts occasioned by even weighting, much less prioritizing. Frederick P. Brooks, Jr., The Design of Design Requirements proliferationA Plea for Lean Software features