If you're really ambitious, you expect that you're going to be doing important things for most of your life.
This brings us to an interesting dilemma.
When to stop training and start producing?
You could always train more, learn more, study more, before you start building and producing. It's almost always going to be a justifiable decision, especially if you're young.
There's many schools of thought on this. There's the "just get into action now" school of thought, who start hustling and taking actions right away. This is usually a good course that leads to results, but I think sometimes the move-move-move crowd misses out by maxing out in a small area. They get to the top of the game, but they never researched and planned whether it was the right game to play.
There's the "of course you should study crowd" that encourages you to get a bachelor's degree, master's degree, and a PhD, or do the equivalent training and learning before getting into the field. Ironically, I think this falls into the same trap as the above - you come out with some excellent credentials and knowledge in a particular field, but maybe didn't do enough real world application to see if that's the field you want to play in.
Sometimes it's decided for you. If you play a sport, there's a defined season when that sport is played, and there's a defined spectrum of games. You train however much makes sense to you and your coaches.
But most of the world doesn't work like that. At any given time, you could make a sales call, or you could read a book on selling. At any time, you could submit a resume to get a job, or you could be working to get a new credential. At any time, you could be studying your craft, or you could be doing your craft.
Again, I lean more to the action side of the equation - start producing sooner than later, because you also learn from that. It shows you what areas you need to take action in by your mistakes.
But it was still a hazy thing to think about.
Recently I had a chance to re-read Stephen Covey's "Seven Habits of Highly Effective People" - and it strikes me that Covey is one of the only people that captured this dilemma really well.
He calls it P/PC balance - production, and production capability.
Production is getting results - doing things, accomplishing things, making money/resources, etc. Production capability is what allows you to do that - skills, contacts, connections, credentials, tools, maintenance.
In the end, there's no magical correct answer. Ideally you are both producing and increasing your production capability by training all the time. The exact amounts are set by you.
I'll say I come down on the produce side of the equation - you don't know how well your training is going unless you try to use it in the real world. And by trying, you also learn more, and best of all - you see firsthand where you need the most additional training going forwards.
I have pretty smart readers here. I bet some of you have thought your way through this one. What do you think? What choices did you make, when trading off between producing and training?
I see it as a problem of maximizing the P * PC product (i.e. amount of work accomplished), subject to a linear constraint a*P + b*PC = 1. It takes time to produce stuff (factor a) and it takes time to increase production capability (factor b) and there's a finite amount of time you have at your disposal.
Unfortunately this trivial concept is pretty hard to apply with precision in real life. It's impossible, extremely fuzzy at best to measure a, b, P, and PC. However, it's pretty easy to grasp that the amount if work accomplished is really small if either P or PC is small.
When to stop training and start producing?
Why not do both at the same time?
Here's a quote from an interesting article I read yesterday:
"Lots of the experts in the world will tell you that they didn’t practice much, but that is usually because they don’t consider doing what they enjoy as practice. The kid spending hours outside playing soccer with his friends doesn’t see it as practice, but it is. The designer sketching what he sees out his window does so because he loves it."
More here: http://www.drawar.com/posts/How-To-Be-An-Expert-Developer-or-Designer
There is certainly a balance. I used to be a perfectionist, tweaking my work which never quite got out there. I think there are a lot of people out there like me who get stuck in place because of that.
That's why I'm with you: there's a balance, but if you have to choose a side, choose producing tangible results. In the end, it's mostly a false dichotomy: by doing, you are also learning.
Depends on the field and nature of the task, since some require a lot more knowledge than others. Learning by doing seems to be a great way to go about building a web app for example. Not so if you're gunning to create a new programming language or a new operating system.
The distinction there I think is the difference between systems and products. When building systems, you start with architecture, and architecture is fundamentally hard to change once the building is halfway up.
As it happens, those involved in architecture, whether it be the architecture of a commercial office building, or the architecture of a video sharing site, are wrestling with immense complexity, and yet affect many people through seemingly trivial decisions.
To that group, study until you can somewhat reproduce current systems, and then practice and iterate until you've got a refined system.
It's a good question Sebastian. I think the answer is a continuous mix of both. I believe in learning by doing. Test the things you've learned by starting a small project. And every time you do any kind of project, try to encapsulate lessons that you can apply to future endeavors. Ultimately there is no value in training on its own - the point is to do. And yet, another way to think about your life is that everything is training to prepare you for what's next.
See my post: 21 Lessons Learned from 21 Weeks at a Startup
I think it ultimately depends on who you want to be.
If you want to have a lot of answers, then Production Capability might be a better path for you. Otherwise, if you want to have a lot of products under your belt, then obviously starting sooner will be better for you. You can always pivot to the other extreme when you're satisfied with what you have.
Most ambitious people do want both. However you're still more likely to favor one over the other. So go where your passion takes you, but still leave a little bit of room for the other. In my case, I want to be as knowledgeable as possible about many things. Obviously I still want to produce, but I tend to favor learning over production. (Even producing, but nothing practical, it's all for the sake of learning!) So whenever an opportunity comes to produce something of value, I force myself to stop learning a while and build it, knowing I'll jump right back into learning when I'm done.
I've been following your blog for quite sometime now and your recent post struck a chord with me. I've found that I have no passion. Instead, I have a passion for the passionate, in the abstract. When I'm working near people who love what they do, can see their grand vision and have a pathway to the future it inspires me. From a chef to a programmer, if I meet a passionate person, I immediately want to be them.
I've made numerous blogs covering different topics. I've started a variety of different groups at university. I've even switched hobbies from martial arts to programming to yoyos. Nothing seems to stick. It seems I need a mentor of sorts to make sure I stay on track otherwise, some voice in my head is "ooh! try this! no no no! try this!"
My main question is, how to continue? How do you know when you should cut your losses or when you're just being a pansy? Help me focus Sebastian!
I know where you're at and I've got a number of thoughts.
First and foremost, did you see Miguel Hernandez's replied? I wrote "Passion Emerges From Action, Not Contemplation," I asked for Miguel's take because he's a sharp guy.
Here's a link for you that may really help you to develop as a clear-thinking person: http://www.cs.auckland.ac.nz/~andwhay/postlist.html.
What is it? A list of Eliezer Yudkowsky's blog posts in chronological order over a period of about two years. It's nearly six hundred (600!) posts long; he challenged himself to write every day, for at least a large chunk of that time.
Eliezer Yudkowsky is a man who works with two extremely cool things. One, he works with artificial intelligence (AI). He has an extremely strong grasp of math and logic, and works on advancing the field. Two, Mr. Yudkowsky works with CFAR, the Center For Applied Rationality. It's an organization that aims to teach the art of rationality to willing students.
He also writes the fanfiction Harry Potter and the Methods of Rationality, as a sort of introduction to the art for people. HPMOR is actually quite educational and a very gripping story. if you're normally not big on fanfiction, I recommend giving it a shot just for what you can learn; I've heard some people say it's also a read that motivates them. If you like fanfics, or if you like Harry Potter, I think you'll enjoy it! Lots of little references, jokes, it's really quite captivating.
I've been reading HPMOR for a while, and known of Mr. Yudkowsky's posts for a while, but only today did I stumble upon the list of his blog posts, and realized how massive it is.