In ways you didn't anticipate A Quote by Patrick Hebron www.noemamag.com I always have a hard time wrapping my mind around some of the classic user questions: What is this thing for, is it for novices or professionals, etc? I do my best to avoid these questions, because the best thing you can possibly accomplish as the maker of a tool is to build something that gets used in ways you didn’t anticipate. If you’re building a tool that gets used in exactly the ways that you wrote out on paper, you shot very low. You did something literal and obvious. All sorts of ways to use the machineHacking is the opposite of marketingStretching the productThis tactile form of doodling toolssurpriseux
scribe.rip An Application scribe.rip I hadn't realized that Medium had made JavaScript a requirement to be able to read any Medium post - I'd had JS disabled for ages on Medium just because of all the extra cruft they added. But now, without JS, you only get the first few lines of content, and the rest is loaded entirely with JS - which is...stupid. Scribe fixes all that and focuses entirely on the author's content. Why Would I Want to Use This? You believe in an open web You believe more in the author than the platform You don't like the reading experience that Medium provides You object to Medium's extortionist business tactics You're concerned about how Medium uses your data Other reasons wwwblogging