Hear, hear! Posted it as I've been raving about ion (particularly s-exp support) to non-amazonians, but credit goes all to them.
It's particularly interesting to see the fixes and improvements from the actual open source cleanup effort getting to (many) Internal production services.
I've read recently the book that the article references - Why Humans like Junk food - and it's a fascinating read - despite being poorly written.
Putting theories behind food appreciation, like Vanishing Caloric Density, the Umami flavor (MSG, garlic and Friends) and flavor familiarity (vanyloids are present in breast milk) - on the context of foods your familiar with, changes your perspective when you're tasting any kind of food, allowing you to deconstruct what are you experiencing: "Ho, I like this because it's greasy, and it salty, and it has loads of umami from the garlic".
It allowed me to deconstruct a common action, changing it from an immediate appreciation to a more rational, pondered thought process.
Reminding me of my favorite hunger hack: got into kitchen, chop onion or press garlic, toss into oil, fry. In ten seconds, I go from "dinner sounds like a hassle" to rooting through the cupboards, salivating madly.
The application looks good with interesting articles at the time of writing.
As a note though, I opened the link because I thought it was related to Monocle magazine (http://monocle.com/) which also provides high quality content (albeit not community-sourced). Maybe reviewing the name is in order?
As a reader of Monocle, I thought the same. Being that they both play in the publishing content world, I'd think Monocle the magazine would come down on the OP legally. Aside from all that, I'm eager to check it out.
High five to my fellow Monocle readers (subscribers?) ;-) Just as a FWIW, I'd totally love a Hacker News-style site for Monocle-esque topics (i.e. the blend of culture, design, business)..
Starting by congratulating Tesla in their system, which should win some converts, but there's something bothering me with it.
An automobile network that's also owning their "refueling" network concerns me with the usual lock in concerns. What'd append when other brands want to offer the same service? A multitude of recharge posts all accross the land space each under their car brand flag? Figuring that there's only tesla and ford on this city, instead of the Nissan charging station that I need?
This particular solution seems very specific to Tesla (or even only model S), is there any standard or independent initiative for battery-exchange stations?
Interestingly, the idea of a car company owning the charging station network was presented by Cringely on his column years ago. [1]
Just listened to the podcast the other day and was struck by how similar Tesla's model is to what he presented. The entire segment is around the question of "how would Steve Jobs run a car company".
The point about prioritizing clearing road-blocks for your team cannot be underestimated, but, in my experience, with a serious caveat:
- Unless your SURE you have the time, do not put the technical task onto yourself, try to redirect.
I've made that blunder over and over again: saying "heh, I'll hack this little bit up tomorrow", and in the middle of planning, helping other people and so forth you postpone, losing the blocked developers attention and focus.
Other than that, great write-up on my job description :)
I can't upvote you more than once, so I'll add an "amen" and a personal experience.
A while back a company where I'd been doing contract web dev work had a dual account/project management role come open and offered it to me. I'd done some client-facing work for them before and freelancing on my own, so I thought "How hard could it be?"
Two things I didn't know when I said yes:
* how much work there was for the small team in place -- and because I wasn't replaced as a technical resource, the team had just gotten smaller
* how different development and management work are in terms of headspace. It's very hard to do both simultaneously, because one job requires a lot of immersive concentration, and the other requires near continuous back-and-forth to discuss, track, and push a lot little pieces of information where they need to go.
So... I'd end up having to find non-office hours to do development work, but still had to be "on" and available during normal office hours.
I managed to keep it up for about six months. Kindof. Wouldn't recommend it, though.
