Oh, the Places You'll Go
daltoncaldwell.com
daltoncaldwell.com
I'm sure no one could have predicted just how successful it would become, but he did put an enormous amount of thought into the messages he was sending. This NPR interview with the author of a new book about Dr. Seuss is very interesting:
http://www.npr.org/2011/10/05/141085044/gustav-tadd-and-todd...
He made a lot of war propaganda early on in his career, and it seems that this is one of the things that had a profound impact on him and the later books were partly an attempt to make up for that.
--
This point is pretty spot on. I can imagine that when you're doing something that is percieved in hindsight as "great"; if you spent all your time doing it thinking about how "great" it was, you'd probably make all the wrong choices because you'd be all worried about making it look "great" in hindsight.
How much muscle memory did Zuckerberg have? Couldn't have been that much as he was so young.
I think this post is missing a larger point. You don't need to get to the point that "creating and shipping products is muscle memory". You just need to ship products. We've all seen the examples of Rovio (60+ products before a hit) or Id (4 products before hit?). And there's probably also plenty of examples of first product hits as well. Seems like important part is shipping. Not being a master of your craft.
Of course maybe that's not what people want to hear and I certainly would like to know tips that would make it more likely that the things I ship, write, create will be well received and popular but I can certainly name many products, libraries, app that are not the product of "someone with a finely honed craft."
And so that's the true story. It's not that people who do great things don't have an interesting story because to them it's just a normal day and they're so awesome they don't recognize it. It's that greatness comes from doing. The more you do the more chances for greatness.
"Great" things also depends on your timing and what the competition is doing. (Remember Job's Newton?) Bad timing could be having the right product at the wrong time. Good timing a little earlier than the competition in some cases. As well as luck. And also honesty and how you deal with people you work with, suppliers. And this only scratches the surface.
I mean even with respect to sports the winner in any given year is dependent on the quality of the other teams or individuals playing, right? The second fastest man would be the fastest if the fastest didn't run that race.
"It's that greatness comes from doing. The more you do the more chances for greatness."
And in a sense the key to the VC business. If you put your money behind enough possibilities (with some reasonable vetting) some of those ideas will succeed. I mean if they could predict better the ideas that would hit (even assuming the timing was right and there was nobody else trying the same idea) they would have a much better success rate than what the currently have, right? The success rate is not great actually.
"I certainly would like to know tips that would make it more likely that the things I ship, write, create will be well received and popular"
One of the problems with reading to much about what others say (on HN or elsewhere) is that you get a watered down version of the world since there are always different points of view. (Horse by committee is a camel?) No single vision directing things. To many points of view. Something that I am able to achieve given my skills, knowledge the way I was raised and a million other variables might not be the right approach for you. Just like you may be able to walk up to a random woman in a bar and pick her up with a line and an approach that wouldn't work for me. Just like Jobs could make people do things by his words and his presence, his looks, his voice that (insert smart but dull person here) can't.
Facebook ships every day, and in the early days they shipped continually because they were editing the code on the live servers (no revision control even). I doubt that anyone would have called the very first version of facebook "great", but they've shipped thousands of times since then, and now they have product with a billion users. And of course Facebook wasn't his first product either -- remember the Facemash story?
In general, I find that a close inspection of these success stories only uncovers a hidden backstory where, in fact, the protagonists are developing "muscle memory." And this doesn't necessarily mean that they were building a startup, were the best in their field, or even went through the commercial marketplace! It means only that they accumulated the right mix of skills and experience to see - and then reach - success.
Clearly Zuckerberg was, at the bare minimum, used to whipping up CRUD-style web sites - and had even started taking on contract work - before he decided to start on Facebook. He didn't wake up one day, say "social networks, what a great idea," and learn PHP and MySQL all at once. He arrived at a position where it was natural to work on one as an extrapolation from his existing experience, an incremental leap out of the comfort zone.
Just "doing" is not equivalent; lots of people "do" every day, but don't grow or challenge themselves.
Its basic message is to embrace failure. You're going to fail, things will be difficult, and you probably won't be great at everything. All of that should absolutely not deter you from trying what you want and living the life you want to live.
A friend gave me this book when I quit my salary job 3 years ago; I've read it to my 2yr old boy many, many times.
That's a vague statement, but I interpret "muscle memory" to mean "have a good default toolset" in this context.
It makes a lot of sense to have a default toolset -- tools that work well in a lot of situations that you understand very well, which together cover most of the problem space you work in. That frees you from getting lost in the weeds trying to decide which tool to use each time. However, it still very much matters what tools are in that default toolset.
It takes a lot of effort and study to understand and choose the right set of default tools. If the options are MySQL and Postgres (or ruby/python, etc.), you need to pick only one as your default choice, otherwise you get distracted trying to make that decision for every project. It's not so much whether the technology overlaps or not, it's whether you perceive the applicability to overlap. For instance, if you perceive MongoDB to be useful as a primary datastore, it can't easily coexist in the default toolset with a SQL system; but it can if you perceive MongoDB to be more of a caching layer or for special-purpose processing.
Of course, you should recognize the signals when you're dealing with a different kind of problem that may require a non-default tool.
I don't. In sports, we use "muscle memory" to refer to on-the-fly adaptations that athletes have to perform without conscious thought. For example, a basketball player sees his defender lean too far in one direction, and he automatically knows when to stop, jump and shoot in order to avoid being blocked. The shooter did not have to consciously think "Oh, he leaned that way, so I need to correct this way." That's too slow. The right thing to do is ingrained from hours of drilling and live practice. My sport of choice is Brazilian jiu-jitsu, and I see the same thing with myself all the time. When I feel my opponents weight shift, I don't consciously think about how to flip him over. If I do, he'll already have moved. I just know what to do, based on years of drilling and live training.
So, I extend the metaphor to software to rather the opposite of what you said. Always applying a default toolset is the opposite of on-the-fly adaptations. "Muscle memory" for solving software problems is being able to reason about what you know you can handle without having to pick a technology up front. It's having an intuition of what what the technology allows you to do. You're not thinking in terms of technology, you're thinking in terms of solving the problem and being able to easily classify things as "I know how to handle" and "I don't know yet how to handle."
The benefit of software over sports is that we have the luxury of time; we have the time to check our intuitive guesses through rational evaluation.
http://www.youtube.com/watch?v=ahv_1IS7SiE
Enjoy. Or get moved. Whatever works for you.
Muscle memory comes from doing something many times. Watch the new barristas at Starbucks and compare how they use their hands to vs experienced barristas. Or a plumber. Or a physician. Or a programmer.
It takes time. Unless I am understanding what the OP is saying he seems to be implying that you can "just do it" and be in the zone that allows you to avoid thinking about "which programming language you are using".
When someone asks me a question about something that I have years of experience in I have all the answers immediately without thinking and I know the questions to ask and the nuances and can even correct the wrong information being given to me. That took years reading, learning and experiencing things. It doesn't come overnight. Along the way the learning process did involve "junk filling" my head.
Obtvse - https://github.com/natew/obtvse
Simple - https://github.com/orf/simple
"What is fascinating to me is that Great creation stories all sound surprisingly similar. Something along the lines of “yeah we went in the studio and put down some tracks, and they sounded pretty good, and we had to redo a couple of things, and then when put out the album.”"
Do we have any info on the process that the people who didn't create "great" music used? Perhaps many of those used the same process. And what is the definition of "great" music anyway? Is it music that wins awards, or, the most popular music, or music that is critically acclaimed or music that is downloaded the most?
There's a bit of a switch from a last shot question to a "what do you think of your team" question. Intelligent thoughtful and specific answers to questions about specific plays are quite common (e.g. Tiger Woods discussing his shots after a match).
What is common is that athletes may be less articulate than your typical office professional when describing those events. This interview with Wayne Rooney regarding his goal of the year hits some of the issues: http://espnfc.com/us/en/news/1071240/beautiful-game-beautifu...
BTW, the best Dr Seuss book is "One Fish, Two Fish."
Page didn't always rock. No doubt he had to figure it out like everyone else, but when he did he was clearly a Great song writer and riff maker. And that's Great with a capital G.
However, two types of questions are interesting (at least for me -- of engineers and entrepreneurs; not really that interested in athletes or musicians, but I think it's general).
1) How did you solve this specific problem or decide to make these specific tradeoffs (micro)
2) How did you get to this point (macro) (this has to be asked in a more specific way, unless the person is a really skilled or experienced interviewee
When someone asks me this (or questions like it, since I don't type that many semicolons these days) I always reply "Stop looking at the trees. See the forest".
I'm not sure this makes me any more popular, but if you see semicolons (or parens, or whitespace) you are not reading the code. Sometimes, this has to be pointed out.
Agree and it feeds into the idea that you need to have some grand plan in your mind at all times. When you read stories about people in the news they are always presented as very clearly being "a" or "b". "He always knew he wanted to be President" or "He wanted to be a ball player but ended up being President". Anyway the question can in some cases even be annoying and make you feel defensive. I dated a girl once who insisted on knowing what it was I liked about a particular dish. Why is it important why I like pizza? I just like pizza. Think a minute (if you are a straight guy) about why you like tits. Go ahead. Not sure about you but I can't answer that question. I just like the way they look. Is that an adequate answer? It triggers some thing in me that makes me feel good. I think it's easier many times to describe what you don't like, than what you like. I like air conditioning because high humidity makes me feel yucky. So air conditioning helps me avoid a negative feeling.
I think the key is like you detailed. In the specificity of the question.
When I manually drag the text pane over to the left (sigh), it overlaps the buttons transparently, then eventually redraws over them.
Oh yes, and I added the Doctor Suess book to my Amazon wish list.
thinking is not bad ... you can think and still make great things, greatness doesn't have to be spontaneous or reactive ... it can be well thought, laid out and planned
just think about it .... and oh, the places you'll go :)
That caught my attention. Mostly the biggest obstacle in front is ourselves.