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
Building Momentum An Article by Dan Mall danmall.com Fight the Waterfall Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting. Share Work-in-Progress Early and Often When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum. processworkcollaboration