A video and a post from some friends of mine:
Jon Moore: Video: “Every discussion about REST Ever”
Michael Bevilacqua-Linn: “Unicorns and Strong Typing”.
A video and a post from some friends of mine:
Jon Moore: Video: “Every discussion about REST Ever”
Michael Bevilacqua-Linn: “Unicorns and Strong Typing”.
The team at Mozilla posted a great piece documenting their idea and design process for what may be a new feature set in Firefox: “Save For Later”.
Absolutely one of the best posts on what I consider to be the responsibilities of my work and what I aspire to practice, John Allspaw has written required reading for anyone looking to become a Senior Engineer or anyone who wants to grow into a better one: “On Being A Senior Engineer” (via rc3.org).
I’m reading “Systemantics” by John Gall and find myself at times laughing to myself and at times wretching in scenarios I recognize all too well in my work. His humor, which is straight out of “The Hitchhiker’s Guide to Galaxy”, helps with the pain. This might end up next to “The Mythical Man-Month” on my bookshelf and as a book I recommend to any coder looking to to progress from simply writing code, to solving problems.
Related:
laetus in praesens: Why Systems Fail and Problems Sprout Anew: Commentary on the principles of ‘Systemantics’
According to CNBC an unknown program triggered 4% of trading activity last week:
The program placed orders in 25-millisecond bursts involving about 500 stocks, according to Nanex, a market data firm. The algorithm never executed a single trade, and it abruptly ended at about 10:30 a.m. Friday.
Someone testing in production perhaps?
I recently read about no starch press’s “Super Scratch Programming Adventure!” from a post at boingboing and had to purchase a copy. The book looks as terrific in person as it does in the discussion at boingboing. My daughter was happy to see the book when it came in the mail. I’m looking forward to starting to read it with her and try some of its projects. Check it out.
Transcription: “Oh, The Methods You’ll Compose”.
When a coder sits down to start banging out code
The first thing to start crowding his cognitive load
Is whether his program will do what it should
Correctness, he says, is what makes my code goodIt’s the function that captures the coder’s attention
Behaviors and inputs and outputs are mentioned
As if the one good that a coder can bring
Is to spin the right wheels on some Turing machineAnd compiling and linking and running are great
(We need to do these to put food on our plate!)
But the shocker that might leave you scratching your head
Is that actual code is less written than readWe spend more of our time in maintaining our stuff
Than we ever spend writing the simplest of cruft
Which means that unless you’ve got something the matter
You’ll try to learn just a few code style patternsSo coders and countrymen, lend me your ears
As I teach you some lessons won hard through the years
From that Beckian book about implementation
And patterns that derail code suckification
Algorithmically challenged (love that name for a blog!) put together a great list of resources to learn Scala on the Web. New for me was a massive list of links posted to Stack Overflow (one for the bookmarks).
Jon Moore: It’s a Great Team When….
It’s a fantastic privilege to work with the team I do. We’re a cast of characters, everyone is a contributor, fighting for each others success. Leadership plays a role in that. Mission plays a role in that. And so does a belief in one another. I’m actually looking forward to going back to work after a vacation.
How rare is that?
BBC ran a piece introducing a C64 to a couple groups of children to commemorate the day.
Related:
Wikipedia: Commodore 64
ars technica: A history of the Amiga
c64.com
Commodore USA