Last week, director James Toback appeared on Alec Baldwin's excellent podcast, Here's the Thing. They talked a lot about the benefits of having full creative control over projects, but the big takeaway for me was on being forthright about your intentions. Toback paraphrases Karel Reisz's way of working:
Decide what you want, and then make your wishes clear to everybody you're working with.
I think this is fantastic advice.
via fffound.
via Type Hunting.
via Nick Crocker.
This week's 99% Invisible includes a short piece on the Strowger Switch, the 1878 invention that allowed telephone calls to be connected without a manual operator. Poignantly, Roman includes a bit about the inventor's reaction to the plight of those operators whose jobs would be eliminated due to his invention. His response, I think, is perfectly appropriate, and reminds me of this chart from McKinsey's report on disruptive technologies. From Roman's piece:
La Porte Indiana became the first place to have automatic operator-free telephone dialing. In a speech at the unveiling of the La Porte telephone exchange, the cantankerous Strowger addressed the issue of the 'hello girls' - the operators who would lose their jobs because of his automated switch. "I am often told that the the telephone girls would be angry with me for robbing them of their occupation. In reply, I would say that all things will adjust themselves to the new order. Water will find its level. The telephone replaced the messenger boy, as this machine now displaces the telephone girl. Improvements will continue to the end of time. Strike where they may."
The 116 images onboard Voyager 1 (the Golden Record) are absolutely fascinating. They tell a weird and compelling story about humanity and the way we understand and process the world. Below are a handful of them, found on Web Odysseum.
I would love to write something more interesting here, but really you should just listen to this episode of Radiolab and read the excellent Wikipedia entry for the Golden Record.
via ffffound.
Chuck Klosterman from his 2013 book "I Wear the Black Hat: Grappling with Villains (Real and Imagined)." The key (to me) is the second paragraph; emphasis mine. (n.b., the text below is transcribed (carefully) from the audiobook. Punctuation may vary.)
And the worst part is that there is no other option. If a father stops his son from embracing the online universe, he is stopping him from becoming a competitive adult. It's like refusing to teach him how to drive a car, or boil water. You may worry about al the ancillary consequences, but you can't take away the experience. Avoiding the internet is akin to avoiding everything that matters. This is even true for adults. An author I know once explained why writing became so much more difficult in the 21st century: "The biggest problem in my life," he said, "is that my work machine is also my pornography delivery machine." The future makes the rules.
The future makes the rules, so there's no point in being mad when the future wins. In fact, the easiest way for any cutthroat person to succeed is to instinctively and relentlessly side with the technology of tomorrow - even if that technology is distasteful. Time will eventually validate that position. The only downside is that until that validation occurs, less competitive people will find you annoying and unlikeable. The future will retire undefeated, but it always makes a terrible argument for its own success.
The argument is inevitably some version of this: You might not like where we're going, and tomorrow may be worse than yesterday, but it's still going to happen whether you like it or not. It's inevitable. And this is what people hate. They hate being dragged into the future. And they hate that technocrats remind them that this is always, always, always happening. We tend to dislike cultural architects who seem excited that the world is changing, particularly when those architects don't seem particularly concerned whether those changes make things worse. They know they will end up on the right side of history, because the future always wins. These are people who have the clearest understanding of what technology can do, but no emotional stake in how its application will change the lives of people who aren't exactly like them. They know the most, and they care the least, and they kinda think that's funny. Certainly, this brand of technophobia has always existed. As early as 1899, people like H.G. Wells were expressing apprehension about a future "ruled by an aristocracy of organizers, men who manage railroads and similar vast enterprises." But this is different. This is about the kind of person who will decide what the future is.
OMFG this is great!
Basically, this guy did an informal (but blind, controlled, and apparently statistically serious) experiment to determine which variables affected people's feelings about a cup of coffee. The short of it:
A few takeaways (emphasis mine):
My longest running experiment centers on coffee grinders. A common belief among coffee pundits is that good coffee depends on good grinding. Specifically, coffee ground with a burr grinder purportedly tastes better because it grinds the beans more uniformly and doesn’t over-heat the grounds like traditional blade grinders. The experiment I setup tested this claim by brewing coffee using a burr grinder or a blade grinder and scored which of the two cups subjects preferred...Based on this analysis, subjects did not show a statistically significant preference to coffee brewed from a blade grinder or burr grinder. Therefore, I opted to save a few hundred dollars and not invest in a burr grinder based on these experiments.
And:
Another variable I was interested in understanding was the impact of different brewing methods on flavor preferences. I wanted to know if house guests preferred coffee brewed via drip-extraction versus coffee brewed with the Aeropress. I setup my experiment as previously described and scored the number of house guest who preferred each brewing method. The objective of this analysis was similar to the burr grinder experiment, but this time I wanted to compare preferences between two different brewing methods...I observed that 15/20 or 75% of subjects preferred coffee from the Aeropress...Thus, there is reason to believe that the Aeropress may, in fact, produce better tasting coffee than drip-extraction.
And:
I’ve examined other coffee variables using a similar experimental approach and found only a few factors that had any measurable effect on coffee flavor in isolation. For example, variables like bean freshness or bean purveyor has little effect on flavor...Until I obtain convincing evidence that support investing additional money in brewing accouterments, I see little reason to deviate from this system. In the words of Carl Sagan, extra-ordinary claims require extra-ordinary evidence.
This is exactly the kind of study I want to do with wine. I'd also love to expand upon Bunsen's coffee experiments to include Moka pot, French Press, and - why not - Folgers.
With thanks to Marco Arment for the link.
I've been working on a few product ideas that would be 3D printed from titanium or stainless steel, and the methods by which 3D printed parts are specified has been on my mind throughout the process. The following passage, taken from the IDA Science and Technology Policy Institute's 2012 report "Additive Manufacturing: Status and Opportunities" sums up my feelings quite nicely. Note: "AM" refers to "additive manufacturing, which is a slight superset to the processes casually described as "3D printing." Emphasis is mine.
AM technology has made significant strides over the past 25 years, but technical challenges related to materials, equipment, and applications remain. Many of the challenges described in this section, which have commonly been discussed in workshops or publications, are the focus of ongoing research in government agencies or industrial organizations. In some cases, the topics may be underfunded by the private sector and could benefit from new or additional Small Business Innovative Research funding.
Information is needed on material properties for different processes, but who would maintain such a database and which data should be publicly available are unclear. Before the AM industry can fully transition to offering viable manufacturing solutions, specifications are needed that provide mechanical properties data for available materials, as well as more detail on how parts made from these materials perform (Campbell et al. 2011). Engineers and designers cannot design without fully understanding the properties of the materials used to manufacture the parts being designed. If the properties for AM materials are not available, designers will not consider additive manufacturing as a method of manufacturing. With so many AM processes and materials currently available, the creation of comprehensive specifications is a resource-intensive endeavor, requiring the involvement of research organizations and system and material manufacturers (Kinsella 2011).
Worth noting: despite knowing the difference between yield strength and ultimate tensile strength, I am not an engineer. But having access to full material data - as well as data on how parts made of that material perform - would be incredibly useful, even to a dullard like me.
via Timoni. Original text on GitHub.
I’ve had a few really great ideas over the years of really awesome things I’ve wanted to work on, and sure, you get people saying “yeah that’d be awesome to have!” But then I couldn’t find anyone to work on it with me. That’s a huge indicator. It’s easy to get people to agree with you, but if you can’t convince them to donate their time to make the vision a reality, it’s a massive signal that what you’re doing isn’t great.
Friday was Rubyday.
On Thursday, Zach and I had banged out about a third of the Codecademy Ruby class. It was a good primer on Ruby syntax and basic usage, and I'll be completing it this week. But we wanted to get a little web dev practice in, and so on Friday we went through the "Getting Started with Rails" tutorial on RailsGuides.
The tutorial is great. My method is to hand-type (not copy/paste) every section of code. I keep two BASH terminal windows open and got the Sublime Text command line tool running so I can quickly create files and edit them without touching my mouse. There were a few anomalies in the tutorial that I had a little trouble with, but googling solved them in short order (It seems that the guide is written for Ruby 1.9.3, and the syntax for 2.0.0 requires a few changes).
By the end of the day, I had created a simple blog app and was hosting it locally. I should note that I don't totally understand the structure of all of what I did, but I got a bit of debugging in, and just typing the entire thing out really did help develop a basic feel for the framework. I think it's also worthwhile to go through simple exercises like this, just to understand how little you know about the basic tools (e.g. blogs) that you get used to using on a daily basis.
The net effect of the week: Every week should be like this. Which is to say, every week is hustle week.
Of course, shit will get in the way. This week I need to be out of town for a couple days, and that'll inevitably throw me off a bit. But I will finish the Codecademy Ruby class. And I will make progress on my seatpost project, and I will move on to the Ruby On Rails Tutorial book. This last one is the most significant of the three, but I would hope to complete it in a matter of a week.
:Sigh:
You know, for three years I worked alone building bikes. It was an incredibly lonely, frustrating time of my life, and in the end I allowed those factors to prevent me from learning all the relevant lessons that were available to me. I didn't hustle hard enough; I had a hard time learning things quickly enough. I'm learning more quickly now, and hustling harder. And though the burn will remain slow for a while, I'm betting that the blaze that results will be quite a bit more satisfying.
Hamish McKenzie, writing on Pandodaily about Spotify and the future of content providers.
I’ve said it before, and I’ll keep saying it until the publishing world has fully adapted to this ongoing tectonic shift in media: In a world in which digital content is increasingly being distributed via all-you-can-eat platforms like Spotify, Netflix, and Oyster at the same time as social networks like Twitter, Facebook, Reddit, Digg, and email are pushing content to people rather than the other way around, and as we increasingly consume media on one-thing-at-a-time mobile devices, the “bundle” doesn’t matter nearly as much as it did in the print or Web 2.0 eras.
Homepages are becoming less relevant.
Stories have to stand on their own.
Content owners have to get used to the idea that their carefully curated packages are being blown to bits.
Amazon's Jeff Bezos at the Aspen Institute in 2009. Via The Motley Fool (emphasis mine).
If you look at where we are today, it's half luck, half good timing, and the rest has been brains. So in some ways, I think we have not been tested. You know, we were unprofitable for so long, and people predicted our demise for so long, that we did develop thick skins - which I think is very valuable for invention, because often times invention requires a long-term willingness to be misunderstood. You do something that you genuinely believe in, that you have conviction about, but for a long period of time, well-meaning people may criticize that effort. When you receive criticism from well-meaning people, it pays to ask, 'Are they right?' And if they are, you need to adapt what they're doing. If they're not right, if you really have conviction that they're not right, you need to have that long-term willingness to be misunderstood. It's a key part of invention.
Amazon's Jeff Bezos, quoted by The Academy of Achievement in 2008. via The Motley Fool (emphasis mine).
So, it really was a decision that I had to make for myself, and the framework I found which made the decision incredibly easy was what I called -- which only a nerd would call -- a "regret minimization framework." So, I wanted to project myself forward to age 80 and say, "Okay, now I'm looking back on my life. I want to have minimized the number of regrets I have." I knew that when I was 80 I was not going to regret having tried this. I was not going to regret trying to participate in this thing called the Internet that I thought was going to be a really big deal. I knew that if I failed I wouldn't regret that, but I knew the one thing I might regret is not ever having tried. I knew that that would haunt me every day, and so, when I thought about it that way it was an incredibly easy decision. And, I think that's very good. If you can project yourself out to age 80 and sort of think, "What will I think at that time?" it gets you away from some of the daily pieces of confusion. You know, I left this Wall Street firm in the middle of the year. When you do that, you walk away from your annual bonus. That's the kind of thing that in the short-term can confuse you, but if you think about the long-term then you can really make good life decisions that you won't regret later.
from While Out Riding, via Joe Cruz.
Programming languages are like girlfriends: The new one is better because *you* are better.
Derek Sivers, in his 2007 O'Reilly post: "7 reasons I switched back to PHP after 2 years on Rails."
from A Conversation on Cool.
The best question is the one that gets the most interesting response, whether it answers the question or not.
The best interviewer is the person who elicits the most interesting response - not the one who asks the most interesting question.
The best interviewee is the one who is able to both yes-and the interviewer (it's not about agreement, it's about agreeability) and provide the most interesting response to the question at hand.