"Design critique is not a place to be mean, but it’s also not the place to be kind. You’re not critiquing to make friends. Kind designers don’t say what they mean. ‘Kind’ is not about the work, and design critique exists to make us better, but mostly, it’s to make the work better." Mark Boulton talks about the value of crits. I was introduced to the vocabulary and tone of the design/art-school crit at Berg, and find it useful, though I daren't think what 18-year-old me would have made of it. Stressing that it's not personal, it's about the work, and that that is contained within a magic circle, is really difficult, and it's really important.

"The process of going back and forth from painting to the computer became a continuous cycle. Midway through as I became more and more familiar with the outcome of how the actual texture would appear on the screen when tiled, my painting process became more specific to achieve the desired texture, color, darkness, stroke, range of value that I wanted for each feature on the map." Lovely stuff from Geraldine on painting, textures, and process.

"Skateboarding, metal work, solitude, machining, precision, and practicality. That's where Roy began." Lovely interview with a chap who makes custom jeans, on his own, simply because he decided one day he wanted to – and then he got good at it. The photographs of his workshop at the end are lovely.

Not a bad list, especially for sites needing hardcore, tight, front-end work, and that are going to face load.

Mitu makes a series of interesting connections here, though the conclusion she came to isn't quite the same as mine – which is in the comments. But there's a mass of starting points here as to notions of the "abstract", and what it might mean for games. Something I shall be returning to, for sure.

"Consider the process of writing the Readme for your project as the true act of creation. This is where all your brilliant ideas should be expressed. This document should stand on its own as a testament to your creativity and expressiveness. The Readme should be the single most important document in your codebase; writing it first is the proper thing to do." I like this: after all, a README is basically the story you tell about your software. Why not write it before the software exists?

"This information describes how Free Range operates, both as a business and as a culture.<br />
<br />
We're open-sourcing our business, from the site to the contracts to the philosopy. Value does not come from these things, but from putting these ideas into practice. These ideas are not assets – we, the people, are.<br />
<br />
Fork this." Free Range have put their manifesto and operating principles onto Github.

Stanford's iPhone development course.

"Is writing ever NOT collaboration? Doesn’t one collaborate with oneself, in a sense? Don’t we access different aspects of ourselves, different characters and attitudes and then, when they’ve had their say, switch hats and take a more distanced and critical view — editing and structuring our other half’s outpourings? Isn’t the end product sort of the result of two sides collaborating? Surely I’m not the only one who does this?" Something else that's been on the pile (to link) for a while now.

"The craftsman as hero is a consistent motif in Ruskin’s artistic and social theories. To him, mechanisation and division of labour dehumanise workers, enslaving them to execute exactly the specifications of others. The only way to recapture the humanity in labour is to put the designer back in touch with the tools of the craft and to unleash the creativity of the maker." A lovely metaphorical piece from Matt Edgar, reminding me of how much I need to brush up on my knowledge of the Arts and Crafts movement, if only because of how much I appreciate their sentiments.

"At some point, I begin to feel that I am carrying entire Latin American forests home with me. Also, I am afflicted with a terrible need to stop and write things down, at almost every corner, slowing my passage through the city and impeding motion. I am locked in this ridiculous two-step, unable to travel more than half a block before sitting down and writing out more, papering over the last thirty feet, dripping more ink onto the street: this absurd project, this incomprehensible, incompletable urge, this terror of forgetting and compulsion to record." Beautiful writing from James, which has been sitting on the "to link" pile for far too long.

"Here is an extraordinary piece of film. It is a live outside broadcast of a British army simulation of an attack on a train in Britain. It went out at prime time on a BBC programme called Saturday Night Out. And it happened in 1956."

"Maps are having their F-64 moment, right now, which is important and wonderful but I don't think anyone really wants to live in a world with an infinite depth of field. It's an appealing idea but then something like the Hipstamatic comes along and we all get irrationally weak in the knees, all over again." As usual with Aaron, I could quote most of the article, but in this case, I'll pick my favourite piece of writing, rather than perhaps the most succint quotation; just read the whole thing. (And: I wish I could code or even write like this).

"By decoupling their data to minimize exporting, they said their polish actually became fun, not to mention efficient. I think many projects would benefit from finding a way to similarly decouple their tunable data." Yup.

"This is the S2H replay; an activity monitor/pedometer thing that does a similar job to the fitbit. Except it feels way more like the future than the fitbit because it's cheap, fashiony and simple. And you they'll actually deliver one outside the US." I like "fashiony" as both an adjective and a watchword. The S2H sounds pretty nifty, too, and Russell's write-up is great…

"Get an accountant, abstain from sex and similes, cut, rewrite, then cut and rewrite again – if all else fails, pray. Inspired by Elmore Leonard's 10 Rules of Writing, we asked authors for their personal dos and don'ts." Huge, two-part article (presumably from Saturday's Review) with a great deal of advice – some sensible, some common sense, some insightful, some entertaining – on writing. And: much of it applies to other creative disciplines, too.

"Schell took this game-life integration to the extreme, describing a world chock-full of sensors, where you could earn experience points from a toothpaste company for brushing your teeth, or points from health insurance companies for walking to work instead of driving. Companies and even the government would have a vested financial interest in engaging consumers and citizens through game-like elements. It would be a world fraught with "crass commercialism," Schell said, but it would also be a world of opportunity for game designers." Hmmmmn.

"I'm imagining that Curling is project management: sweeping in front of the stone to both clear a path and influence the direction, but without touching it; a good curling strategy is to both knock the competition out of the way and get closer to the target, sometimes with different stones; …plus you can drink and smoke while you play"

"The pattern we see here is to keep crises small and frequent, as Ed Catmull of Pixar says in an excellent recent talk. When describing the difficulty Pixar's artists had with reviews ("it's not ready for you to look at"), he realized that the only way to break through resistance to reviews was to increase the frequency until no one could reasonably expect to be finished in time for theirs. The point was to gauge work in motion, not work at rest." I liked this quotation, but as usual, the rest of Mike's post is great.

"Goblin Slayer is a quick, easy to play boardgame of heroic adventure and underground combat for two players." Tabletop dungeon-crawl boardgame with nice little board structure and not bad artwork.