There are no people in ischeriad’s collective.

Huffduffed (25) activity chart

  1. Neues aus der Raummaschine

    Netzpolitischer Kaffeklatsch, kunterbunter Nerdkram und Shitstormberichterstattung.

    —Huffduffed by ischeriad

  2. Neues aus der Raummaschine

    Netzpolitischer Kaffeklatsch, kunterbunter Nerdkram und Shitstormberichterstattung.


    Tagged with donald knuth

    —Huffduffed by ischeriad

  3. The Phantom Merlin

    This episode of Scruffy Thinking features a conversation with Merlin Mann and Mike J Nichols. We talk about San Francisco, music, getting a job and… of course, Star Wars: The Phantom Edit.

    —Huffduffed by ischeriad

  4. 5by5 | Amplified #1: I Don’t Know How She Does It

    Jim and Dan kick off their new show with plenty of Mac talk, guitars, Canadian trivia, and more.

    —Huffduffed by ischeriad

  5. 5by5 | The Talk Show #88: I’d Get A Super Yacht

    5by5 - The Talk Show #88: I’d Get A Super Yacht

    —Huffduffed by ischeriad

  6. SXSW 2012: The Ultimate Bruce Sterling Talk

    This is Bruce Sterling’s closing talk from SXSW 2012 Interactive.

    —Huffduffed by ischeriad

  7. The SF Signal Podcast (Episode 118): An Interview With Sword and Laser Hosts Veronica Belmont and Tom Merritt - SF Signal – A Speculative Fiction Blog

    —Huffduffed by ischeriad

  8. Ep. 24: “The Wrong Mustache” - Roderick on the Line - Merlin Mann

    The Problems: Our great nation’s vein of Juggalos; out-of-period (OOP) vermin; small-cask Canadian hooker bacon; adventures in intellectual LARP-ing; underwhelming donut memorials (and their equally disappointing water features); preferred ladies footwear for dramatic airport escapes; John’s nationally-televised bass premiere; and the quiet release of some handy tail-losing techniques.

    —Huffduffed by ischeriad

  9. Excessive Enhancement: JavaScript’s Dark Side

    Are we being seduced by the animation and rich UI capabilities of modern browsers at the expense of the underlying platform of the Web?

    The Web has entered a new phase in its evolution: The proliferation of a JavaScript enabled audience with increased processing grunt in their devices, better and more ambitious JavaScript developers, and users with an appetite for sophisticated experiences, all seem to be helping to move the web in a rich and exciting direction.

    Good developers understand about graceful degradation, progressive enhancement, unobtrusive JavaScript and the like, so why are we seeing big companies building web offerings with little apparent thought for their impact on the Web?

    We’ll explore this by looking at what the Web was, is now, and might become. We’ll look at examples of exciting user interfaces and sophisticated interactions. We’ll also examine some emerging techniques for providing rich user interactions without hurting the web or killing kittens.

    Phil Hawksworth, Technical Director, R/GA

    Phil began his career building web applications for financial institutions such as Commerzbank, Deutsche Bank, and the London Stock Exchange in the late nineties. A focus on web architectures and real-time data delivery lead Phil to a variety of web development roles with particular attention to emerging front-end development techniques and JavaScript application development.

    After several years working on web applications and consulting on web best practices at technology companies such as Verisign, VMware and BT, Phil made the move into the agency world where he managed development teams and architected solutions on projects for clients including of eBay, Sony and BP.

    Phil Hawksworth is a Technical Director at R/GA and enjoys talking about himself in the third person.

    —Huffduffed by ischeriad

  10. CSS for Grown Ups: Maturing Best Practices

    In the early days of CSS the web industry cut its teeth on blogs and small personal sites. Much of the methodology still considered best-practise today originated from the experiences of developers working alone, often on a single small style sheet, with few of the constraints that come from working with large distributed teams on large continually changing web projects.

    The mechanics of CSS are relatively simple. But creating large maintainable systems with it is still an unsolved problem. For larger sites, CSS is a difficult and complex component of the codebase to manage and maintain. It’s difficult to document patterns, and it’s difficult for developers unfamiliar with the code to contribute safely.

    How can we do better? What are the CSS best practises that are letting us down and that we must shake off? How can we take a more precise, structured, engineering-driven approach to writing CSS to keep it bug-free, performant, and most importantly, maintainable?

    —Huffduffed by ischeriad

Page 1 of 3Older