"Gor is a simple http traffic replication tool written in Go. Its main goal is to replay traffic from production servers to staging and dev environments." Handy to know about.

"While collaborating with the geniuses at Bot & Dolly in beautiful San Francisco, Munkowitz was tasked to Design Direct a truly unique piece called BOX.. The piece was originally supposed to function as a Technology Demo, but Munkowitz and the team quickly realized it's visual potential and transformed it into a Design and Performance Piece… The resulting short film is a one-of-a-kind visual and technological achievement due to the very special combination of talent and gear behind the doors of the B&D facility…" Projection mapping and motion control all at once; very clever, sure. But it's the art direction of the whole performance (and the camera's dollybot is very much part of that) that really grabbed me – especially 'Escape'.

""Prisms" is fully algorithmic. There are no cuts, just one continuous generative animation. All decisions (camera work, movements, formations, etc…) are made by my system's interpretation of the audio track. My work was creating the system and then curating its output or, to put it another way, I just wrote a computer algorithm, and the computer did it all."

"Now that we know some of the problems, how does Curiosity solve it? The answer is: it does not. It saddens me but the game does not even appear to have realized what the problem with the design might be. The cleverness in the execution seems to stop after realizing that transmitting all the blocks at one time is a bad idea. Instead of looking at this as a form of interesting engineering problem nobody thought anything at any point…" Ouch. Great analysis of the problem, depressing analysis of the implementation. You'd really have thought game developers building a game around these very issues would have thought they'd have been critical to solve. Hey-ho.

"…the definition of a bot seems quite arbitrary, where do we call an application or a string of actions or scripts a 'bot', and where or when do we call it something else? Is the only reason for calling a scripted set of actions a bot, the fact that the script takes the role (and maybe the place) of a human being as a form of artificial intelligence, like they do for instance on wikipedia, in chatrooms, twitter or spamming us through mail (do they really set out to maximize their chances of success? – which is what often AI delineates)?
And what about the new generations of Twitter web scutter that does not seem to be intelligible in any human-sense kind of way, but do follow scripts and try to maximize something (followers, tweets)?" Bookmarked if only for use of the phrase "web scutter".

"I've often felt a sense of sadness that it's only the final piece that sees the light of day; there's a lightness to the experimentation that goes into the early parts of projects, when you're not worried so much about final implementation and instead can just play. We're going to start exposing some of this process, and this post is about the thinking that went into http://migration.stamen.com/, a recent project for Esquire Magazine." Lovely post from Stamen about the early stages of invention for this project.

Nice post about building your own maptiles in Tilemill. Something to return to when I have a location-specific maps problem to solve, perhaps.

Really interesting post about the architecture at Tumblr, which has changed a lot over the past few years, and is a fascinating selection of tools stacked together. Especially good on the reasoning behind tool selection.

"Prototypes for Mac turns your flat mockup images into tappable and sharable prototypes that run on iPhone or iPod touch." Nice.

"My dream cloud interface is not about booting virtual machines and monitoring jobs, but about spending money so my job finishes quicker. The cloud should let me launch some code, and get it chugging along in the background. Then later, I would like to spend a certain amount of money, and let reverse auction magic decide how much more CPU & RAM that money buys. This should feel like bidding for AdWords on Google. So where I might use the Unix command “nice” to prioritize a job, I could call “expensiveNice” on a PID to get that job more CPU or RAM. Virtual machines are hip this week, but applications & jobs are still the more natural way to think about computing tasks." Yes, this. And: lots of people _think_ the cloud works like this, but it really doesn't, yet. Parallelization/adding computing power is more practical, but it's not been made easy like a bunch of other things have (so far).

"We were a niche site and in the course of eighteen months had siphoned off about six thousand users from our massive competitor, a pace I was was very happy with and hoped to sustain through 2011. But now the Senior Vice President for Bad Decisions at Yahoo had decided to give us a little help." Maciej on what Scaling Pinboard Fast actually looked like. Some good anecdotes in here.

"I shouldn't even explain it- you should probably just youtube some gameplay footage if you're interested and watch the insanity." Gerard Way on quitting Force Unleashed – and hinting that he's going to talk more about other games he's given up on. That should be interesting.

Some well-worn tales here, but also some good new ones, particularly when it comes to query-profiling and all forms of caching.

"Marketing is a strategic function about delivering customers what they want. It isn’t a jazz hands and rubber chicken and t-shirts. It is the heart of successful companies…"

A few notes on Flickr's queueing systems.

Cultured Code do a large behind-the-scenes look at how they designed their Things iPhone UI. Lots of detail, lots of working shown. Even if you don't agree with the choices they made, it's excellent to see somebody sharing at this level of detail.