Menu ⇓
  1. ↪ Aaron Parecki: @benwerd Awesome, I've been using an 11" Air for a couple years, I'm a huge fan! I'm switching to the 13" Pro now... http://t.co/RXQM7VZRyG

    Aaron Parecki @benwerd oh cool — I’m upgrading to the 13" retina pro this christmas, good to know it’s a good machine! Certainly a significant upgrade from my trusty old non-unibody MB

  3. Feedback Loops

    The larger the gap between one major feedback loop and the next largest of any given stage of an activity, the more assumptions must be made about that stage.

    Example: planing a hurdy gurdy top to thickness.

    Tasks, feedback loops in order of duration (timings are approximate from memory):

    • Every millimetre of planed wood, ≈150ms audible and physical feedback
    • Every ≈1cm of planed wood, ≈500ms visual feedback loop seeing the shavings protrude from the plane (or not, which is equally valuable)
    • Every ≈10cm of planed wood, ≈3s visual+physical+audible feedback loop of one complete shaving detaching
    • Every ≈20cm of planed wood, ≈5s visual feedback loop seeing freshly planed surface, erosion of pencil marks
    • Pause every ≈10 plane strokes, ≈20s physical feedback loop picking up the top and flexing
    • Pause every ≈20 plane strokes, ≈1 minute precision visual feedback from re-measuring the thickness of the top with a caliper

    The gaps between feedback loops become larger as the durations become larger, as do the assumptions which are made about the task at each level until the next feedback loop arrives. I suspect that experience level also affects both the value gained from each feedback loop, increasing the actor’s knowledge of the system and increasing the amount of time which can safely be left (i.e. the amount of assumption which is safe) before more feedback is required.

    Two observations: the existence of vastly longer feedback loops of experience accumulating which affect the shape of existing loops, and that the smallest feedback loops are broadcast by the environment (audible feedback, physical resistance) but longer ones require active participation (testing the system).

  6. ↪ Brian J Brennan: @BarnabyWalters nahh nothing like that, it's actually pretty tame. But the GET request would potentially create a resource.

    Brian Brennan ah, okay. I was thinking of using SSE-style responses to a POST request as a way of offering real-time feedback about new content creation without having to set up redis and a websockets server.

  12. Post-game-night research: did medieval Croatians have shoelaces? Going by the few bits of 13th century art I can find photos of, no — but that could be down to lazy artists.

  14. ↪ @|p^): hey @BarnabyWalters thought this might interest you http://t.co/sDMaFLAfea if you don't know about it already of course!

    @w03_ thanks, I have indeed heard of Noflo! Haven’t experimented with it much yet due to their focus on the backend framework. I’m working on a similar thing, focused completely on experimenting with programming UI: waterpigs.co.uk/intertubes

  15. psysh.org is the REPL shell we have been waiting for. How to start an interactive shell with a given context:

    <?php
require 'vendor/autoload.php';
$app = require 'src/app.php';
Psy\Shell::debug(['app' => $app]);

    Supports readline, pcntl, registering custom commands, automatic semicolon insertion, clean+concise string representations of evaluated values. Amazing work Justin Hileman!