Technical debt is also known as design debt or code debt. It is “a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.”
“When two are served, you may begin to eat.”
Here’s a longer explanation from Nathan Brackett:
The elegance of Futterman’s Rule does lend it a hint of spirituality. One eats one’s food while it is hot, observing dinner as a natural continuum (instead of the top-down, “no-one-eats-until-the-chef-is-ready” hierarchical model that dominates most households). At the same time, no one eats alone (it is only once two people are served, and a social base is established for those with food, that one may begin to eat). If form follows function, the Rule is built to travel. So give it a try. And if you like it, tell a friend.
[For participants at GOA Learning Design Summit who will be attending my keynote: I hope you will learn from my slides, from my commentary, from each other, or from the links below (they complement my presentation). I’m going to rely on you to go where you need to go to learn as much as you can during the 90 minutes we spend together.]
First read this. It’s about something I call the Google Quotient, and it will help you to make the most of my presentation.
The invention of the AeroPress coffee making device. Quick synopsis from the article: “This is the story of how Adler and Aerobie dispelled the notion of industry-specific limitations and found immense success in two disparate industries: toys and coffee.”
Some background on the Fosbury Flop.
“Steal like a leader” comes from Steal Like an Artist. In my opinion, Kleon’s blog and Twitter feed are their own genre . . . the micro-MFA in Creativity.
The Wikipedia page of Japanese video game designer, Gunpei Yokoi. It mentions his philosophy, one of the great titles of any philosophy: “Lateral Thinking with Withered Technology” or “Lateral Thinking with Seasoned Technology.”
Unsplash, the great photo site.
Startup 101: A Reshan Richards x Montclair Kimberley Academy collaboration.
Telly Olsen’s May Term interview with freeform radio legend Vin Scelsa.
Experts on the future of work and job training. Where I found the Litto quote.
Montclair Kimberley Academy’s May Term program.
My most popular blog post of all time — on moving people to Bcc: as a form of leadership and manners.
The great Calendar Automator.
Outstanding article about the shift to longer classes at Montclair Kimberley Academy. If you’re considering this move, reach out to the author of the article.
Scroll down to # 4 to see a full articulation of meeting terminology.
Manager’s Schedule vs. Maker’s Schedule. A classic.
Quick (and not so quick) look at SAMR.
Polarity (and its maps) explained.
Information at the point of need. Scroll down to the examples.
Closing survey: https://goo.gl/forms/gkXor16dUeLkaPTp1
Bonus: A letter my daughter packed in my suitcase and instructed me to open right before today’s presentation: “We could never be unconnected.”
Here’s Aaron Dessner describing, via press release, the process that led to his new album with Justin Vernon.
I don’t think the record would exist without the community that came together to make it. . . . We took the music to a certain point, and then we reached out and sent it far and wide, inviting friends to contribute any and all ideas. We’ve viewed the record and the process from a community standpoint. We’re incredibly excited about it, as excited as we would be for any album we might make in another situation that’s more conventional. But this feels like something new—the process felt different and the outcome felt different. [source: Pitchfork]
File under: New model for working / art-making.
Ryan Holiday has got me hooked on a new daily read — Marginal Revolution, the blog of Tyler Cowen and Alex Tabarrok, both of whom teach at George Mason University.*
I’m sending this post about “grib” to my writing partner, Reshan Richards, since we love simple, low-tech collaborative tools. I like both the concept (grib as bookmark) and the final admission (“I do recognize that the productivity gain here is small. And much of that gain simply may come from the feeling that ‘I have a system’ rather than from the properties of the system itself.”) Pragmatic, honest stuff.
This sounds pretty good to me.