-
"Hacking is disruptive, and whether you code software, write books, or film movies, I believe bringing anything new into the world is a disruptive act. By being novel and compelling, the new is likely to replace something else and that something else isn’t being replaced without a fight." Great stuff from Rands.
-
"Sugar is a Javascript library that extends native objects with helpful methods. It is designed to be intuitive, unobtrusive, and let you do more with less code." Looks nice – and suitably Javascripty.
-
Sunrizer – basically, a tiny JP8000 clone.
-
Multi-touch instrument thing.
-
"DM1 is an advanced vintage Drum Machine. It turns your iPad into a fun and creative beat making machine."
-
Curious scale-based texture performance instrument.
-
"This script installs a patched version of ruby 1.9.3-p125 with patches to make ruby-debug work again (#47) and boot-time performance improvements (#66 and #68), and runtime performance improvements (#83 and #84). It also includes the new backported GC from ruby-trunk." Speed boosts for Ruby 1.9.3.
-
If you have MacPorts installed, OpenSSL runs into issues when you install rubies through RVM. This helps.
-
"Where you see gadget, I see process. Moreover, where you see prose, I see poetry: for the UK will continue to have no manufacturing all the while it has lost its collective sense of the poetry of production. The ignominious application of production line metaphors to (the actually very creative) industrial life has helped alienate people from the process of making: whereas Lean Manufacturing instead helps to reconnect workers with the project as a whole, by seeing waste as a thing that erodes value, and that corrodes the relationship between customer and producer by making it unnecessarily fragile and contingent." There's lots to recommend in this piece. I'm not sure I agree about software, even ignoring my vested interested and perspective, but there's so much else of value in here. I think this paragraph spoke most to me, though.
-
"When a product is connected to the network it has two brains. A little local one that can perform cheap calculation, and a big one in the network that can do potentially anything at all: massive facial recognition, searching all of Amazon, advanced artificial neural networks, whatever." It's great that Matt's writing so much again – but "little brain, big brain" is a great explanation of the concept.
-
",,,he showed me some pictures of what looked to me like a cross between a flying saucer and Doctor Evil’s hideout perched atop a glorious mountain range.
I knew instantly that I had to go there and see it for myself." Spectacular photography; what a building.
-
"The hackable, digital synth": cheap, build-your-own virtual analogue. Interesting.
-
"I've been working on a sketch wherein some data is downloaded from an HTTP server and is then processed on the Arduino (printed, as it happens, but I don't think that's important). In my original sketches, I was occasionally seeing transfers fail midway through." James is running into issues that might be relevant to me.
-
"The Shruthi-1 is a hybrid digital/analog monosynth. Its hardware design is deceptively simple, but the sonic range is wide: sometimes grungily digital like a PPG-Wave, fat and funky like a SH-101, videogame-y like a Commodore 64, weird and warm like an ESQ-1 ; but more often than not, truly original." Looks nice, not expensive at all.
-
"The easiest way to share localhost web servers to the rest of the world" Good lord, that's wonderful.
-
"Melville’s searing, wayward novel about obsession and the nature of evil becomes a twin-stick shooter for consoles. The twist? The playing field is 5000 miles wide, and there’s only one enemy." Christian is brilliant. (I'm pretty sure my links are full of 'Christian is brilliant' annotations)
-
"Or, in a diffirent formulation of the legendary author of Sim games Will Wright, "Playing the game is a continuous loop between the user (viewing the outcomes and inputting decisions) and the computer (calculating outcomes and displaying them back to the user). The user is trying to build a mental model of the computer model.""
-
"Micro-frameworks are definitely the pocketknives of the JavaScript library world: short, sweet, to the point. And at 5k and under, micro-frameworks are very very portable. A micro-framework does one thing and one thing only — and does it well. No cruft, no featuritis, no feature creep, no excess anywhere. Microjs.com helps you discover the most compact-but-powerful microframeworks, and makes it easy for you to pick one that’ll work for you." Ooh, nice.
-
"It’s okay if they don’t completely understand how a program works after they’ve played with it a little. Very few ideas are completely original. The more material you give your students to plagiarize, the wider the range of derisive works they’ll make from them." Perhaps my favourite point in this very good piece. (Though I've found GameMaker way less of a "kit" than it makes out). But yes: no-one wants to learn to program (for its own sake). People want to learn to make things for screens; programming is incidental.
A Year of Links: Your Questions Answered!
04 March 2012
Following writing about my books to catalogue each year of my bookmarks, several readers had questions, which (rather than responding to in a comments thread), I thought I’d get around to here.
- Matt Edgar commented on the thickness of the spines, and what they represented in terms of my time/attention each year. All I can say is: I got a bit better at the process (more on this later) as time went on; I got quicker at both reading and writing. Also, during my time at Berg (2009-2011), part of my job was writing and researching, so the size of those volumes is in part because I had deliberate time during my work for reading and bookmarking.
- James Adam asked if the body text is from Pinboard or the page. It’s usually a combination of both, with the majority being a salient quotation.
If you’ve ever seen the format I use for my links, it tends to be a long quotation followed by a single line or two. James mentioned this because it seemed like a lot of writing. To which my answer is: it is and it isn’t. It’s a lot of words, but most of them aren’t mine.
To explain, it’s probably worth talking a little about how I bookmark:
I have the Safari extension for Pinboard installed. When I’m reading a page I like, or have found useful, I highlight a particularly salient quotation and click the extension button. This loads the Pinboard form with the contents of the clipboard loaded into the body copy field. I then wrap it in quotation marks, and perhaps add the first line or two of commentary that comes into my head. Then, I fill out the tags – as fast as I can, with the first thing that comes into my head. This tends, for me, to be the most valuable way of tagging.
The time-consuming part is reading the articles; I try to make bookmarking as lightweight as possible.
Bookmarks are published to this site via Postalicious.
So: whilst it looks like a lot of content, most of it is not mine, but it is copied/pasted into Pinboard. Really, though, I’ve got this down to a fine, swift art.
- In answer to Joel and Dave: I used Lulu for printing. I simply uploaded the completed PDFs to them for the inners. The covers were made in Photoshop, a bit by hand, and a lot by maths (because I wanted to use the same typeface on the cover that I do in the book.
- Justin Mason asked about cost. The first book, which is the pamphlet at the bottom for 2004, is about 30 pages, and cost around £2. The largest volumes – 2008/2009 – cost £7 or £8. 2010, which is volume 7, and my first proof of concept, was about £4.50. It was about £30 for the lot, plus delivery, though I saved a bit through some canny Lulu discount codes that I had.
And, finally, a big shout-out to Les Orchard, as the first person who wasn’t me to get the code up-and-running and make some books!