Allen Wirfs-Brock, a Mozilla Research Fellow, at YOW 2011, defined what he considers the current era of computing, and some exciting elements of where we are and where we are going in his talk “The Web Browser is a Transitional Technology”.
It looks like YOW 2011 had some fantastic talks to check out.
Author of “Invent with Python”, Al Sweigart, makes the case for teaching programming skills while enabling children to accomplish something, like making a game, not as an end in and of itself, in “Nobody Wants to Learn How to Program”. I believe this is mostly true, and the sooner we approach K-12 CS education similarly the better.
All about Linux: “Bash Shell Scripting”. A concise, quick to read and scan guide to shell scripting.
Good refreshers:
IBM developerWorks: Elliotte Rusty Harold: “Easier testing with EasyMock”.
Mocking in Java: jMock vs. EasyMock.
Steve Klabnik outlines some best practices in API design in “Nobody Understands REST or HTTP”, some of which I admit I need to follow more consistently. As he states in the end:
Seriously, most of the problems that you’re solving are social, not technical. The web is decades old at this point, most people have considered these kinds of problems in the past. That doesn’t mean that they always have the right answer, but they usually do have an answer, and it’d behoove you to know what it is before you invent something on your own.
Good article with clear to use tips.
Michael Hausenblas has an interesting way to think about Open Data in “Open Data – a virtual natural resource”.
I’m going to disagree that the ‘sun is setting’ on Rails-style frameworks, however, there is a lot in this to think about: caines.ca: “The Sun is Setting on Rails-style MVC Frameworks”.
There is a circular evolutionary path from thick client, to thin client, to thick client. Are we again moving to an age of thick clients with the browser or smart phone being their host? With the preponderance of so many platforms, I have my doubts, at least in the near-term.
James Shore’s post in 2006, “Quality With a Name” summarizes clearly what I try and express and practice in my systems design work.
This is something to not only read and bookmark, but print out to remind folks who are building systems what exactly is good software design.
A good software design minimizes the time required to create, modify, and maintain the software while achieving acceptable run-time performance.
If you’re interested how a number systems I’ve helped design have had such long lives and have grown from small teams to support large ecosystems, “Quality With a Name” is a great place to start
Recently he gave a presentation on evolutionary design that is a good watch.
I’m looking forward to seeing his presentation at Philly’s Emerging Technologies Conference.
codacorolla, a librarian, posted his thoughts to a Metafilter conversation about Califaornia cuts to library funding and spurs a terrific thread at Hacker News.
Read his entire comment and check out the conversation:
“The digital divide isn’t just access, but also ability, and quality of information, and the common dignity of having equity of participation in our increasingly digital culture.”
I’m proud to say there has been a movement in Philadelphia on supporting the mission of libraries, and rethinking how they support their ultimate purpose, and that whenever funding has gotten seriously threatened, people have stood up.
For my part, I’m in talks with my local library to host an after school program teaching MIT’s Scratch. Following that I’d like to initiate a Code and Coffee meetup there and maybe encourage the Blogger Meetups that use to take place to consider local branch libraries as places to meet.
Mark Nottingham gave me a few additional things to consider when building a version lookup into an API in “Web API Versioning Smackdown”. Product Tokens? Building it into the URI? HATEOS?