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
Why we stopped breaking down stories into tasks An Article by Adam Silver adamsilver.io The Scrum process says to break down stories into tasks to make estimation easier, encourage collaboration and to be able to show more granular progress during a sprint. But after a few sprints, we decided to do the next sprint without creating tasks. As a result we drastically increased our velocity and never went back. Here I'll jot down some of the reasons we decided to do this: Breaking down stories into tasks is time consuming The tasks we came up with invariably would change as we worked on the stories Tasks are repetitive Tasks were often carried out in parallel Our estimates didn't improve It decluttered our task board It encouraged collaboration throughout the sprint While we started our process by following Scrum to the letter, we soon realised that breaking down stories into tasks was something that wasn’t worthwhile for us. In the end we realised that it was overplanning and poor use of our time. In the end we used that time to get on with the work and deliver at a significantly faster pace. Why We Don't Do Daily Stand-Ups at Supercede agile