What good is experience?
justinkan.com
justinkan.com
Typically, you have to live out the words of the advice before honestly coming to understand them. Advice -- especially great advice -- is often received as theoretical, removed from specific context, and thus filed away in the deepest recesses of the mind. It doesn't come back to top of mind until a specific situation is encountered, and the advice is suddenly recalled. Then it clicks.
Theoretical advice is generally incomplete unless/until activated by personal context. Advice isn't a substitute for experience, but rather, a framework through which to process experience.
I find this applies to education as well, and it may be why people sometimes feel their academic education wasn't valuable (or, conversely, why people are sometimes surprised that 'qualified' people aren't as proficient as a degree might imply). For example, I could implement bound methods in Python long before I truly understood what the word 'bound' actually referred to and what implications it had, even if I could use them properly and had some vague sense of some binding existing.
It was only after i screwed something up, lost money or ended up not exactly where i wanted did i think back and say .. so that is what s/he meant. Then only after the fact can i take positive action towards the advice previously given and rectify the situation
One of the things i sometimes wonder is, is it just me that can not take advice unless i live it or does everyone else experience it ?
Reason i wonder this is i see people take advice and avoid getting themselves in a jam and i just wonder if they interpret advice differently and possibly have the ability to play out the different situations in their head better and hence can see what the advice really means before they actually need to live it.
(And yes, I am in a best-coder-in-the-room situation. Straying from the topic a bit, where does one go not to be that? I don't have the skills (or the appetite for risk) to found a startup. I've wondered about the big-name tech companies (google, twitter), but my limited experience so far has been that the bigger a company, the worse. It seems like by the time I've heard of a potential employer they're already past the point where they'd be fun to work for)
1. there's a huge difference between "oh, i can pick up rails in a week" and "7 years of rails experience". being super smart is insufficient for certain employers. you want the guy making foundation technical choices to have already learned from his mistakes
2. if you're in your twenties, and you're the best coder/entrepreneur/whatever you know, your hubris is blinding you to your potential, should you work with people more experienced than you. this is not to say you can't win the startup lottery when you're young, but your long term expectation is higher if you learn from others before you do.
One thing that I'd be sure to think about is that more experience isn't just in years, it's in hours spent, and how well/quickly one learns to find and connect the dots to get that picture of experience.
We love college kids like you :D
Unfortunately, the reality is that most companies equate experience with years; just look at the typical job postings as an example of this mentality.
In case you are the smartest person in the world, the advice is still a reasonable thing to do: How will you ever know you are the smartest-in-world if you don't try to find smarter people?
On the other hand, you'll probably never know for sure, as it is wasted effort to compare yourself with literally every other person in the world. So pretending not to be the smartest person in the world is a totally sensible thing to do even if you are.
So let's replace the notion of "smartest person" with something better defined, like "most successful at playing chess, as measured by their chess rating." In that case, we know who the best in the world is, it's Magnus Carlsen. It would indeed be a waste of time for him to seek chess matches where there was somebody better than him, but it is in fact good advice for everybody else to seek to play against better opponents.
However, the strongest players all find that inevitably, they are nearly always stronger than their opponents. For example, the #2 in the world, Levon Aronian, is stronger unless he plays Carlsen. Every grandmaster finds that the large majority of his games are against weaker opponents.
So if you're really "smart," it's good advice to try to surround yourself with "smarter" people, but don't beat yourself up if you find it hard to do--it's an inevitable consequence of mathematics that the "smartest" people will tend to surround themselves with less "smart" people, at least if you're only measuring "smartness" in one way.
If so, then please don't nitpick advice which is good for everybody else. Magnus Carlsen can do that for himself.
When you really are the smartest person in the world, and everyone knows it, you could seek out seek out students and teach them to be the smartest person in the world. I have heard it several times in different ways but the gist is this, 'If you really want to learn X, teach someone how to X.' I don't think the quote is exactly right but I hope the intent comes through.
The 1st version is rife with hacks and inefficiencies, but it works.
The 2nd version builds upon all the learnings of the first version, but is bloated because every little lesson learned is applied.
The 3rd version is where the experience and data gained from the first two iterations really starts paying off. The code is more efficient and the team knows what is truly important and what isn't.
P.S. Has anyone else heard this anecdote before as well? I've tried tracking down its origin to no avail.
I've read The Pragmatic Programmer, and early-on, it mentions "broken windows" principle -- fix errors as soon as you notice them, or else they'll get more difficult for you to fix as time goes by. And like broken windows are like a green-light for a neighborhood to decline, unfixed hacks similarly invite poor quality code.
In practice, do "working" and "working well" end up being sort of the same as suggested by the broken windows principle? Or Is "make it work" refer to making a quick prototype, and "make it right" refer to filling out substantial functionality?
The reason for this style of thinking applies to projects that you don't really have a clear path on how to implement them. A good example would be building a humanoid robot. Along the way you learn what works and what doesn't and you end up with a project that works, sort of. Now that you have a better understanding of the problem you re-architect the entire project, if needed, to make it easier to maintain long term.
Of course, this is just a rule of thumb. You don't have to wait till the end to re-architect a project. You could treat each major sub-module as a project of its own and apply this same thinking.
[0] http://nathanmarz.com/blog/suffering-oriented-programming.ht...
If there's one skill thats invaluable in any industry, it's a track record; of problem solving experience. An education simply won't give this unless you're possibly in some extended research role.
If you are lucky enough to get an education, it's another foundation to work from, but it will not make up for experience resulting in a track record.
Assuming this post refers to the track record of positively learning from our experience; we see the world does kind of run this way. Can't always fake it till you make it forever.
Having a bit of both:
Experience and track record of results will always beat education. Why? Education and theoretical stuff isn't in the real world often enough.
Experience, resulting in track record of successfully overcoming challenges is very, very valuable.
> Experience and track record of results will always beat education.
I see these as two very separate things. Why do you compare them?
As I started to gain experience and learned about what sort of things worked and what didn't, a boss of mine gave me a wonderful piece of advice: even if you're 100% sure that the answer to a question is no, give yourself ten or fifteen minutes to think it over a bit before responding. What you may have seen in the past may not apply anymore, and if you give yourself some time to think about a proposal you may be able to recognize some really novel or useful ideas.
Could you please clarify?
In my experience, when people take something we all agree is impossible and start doing it, it is usually because they've redefined the problem in such a way that forward effort can be made. Termination checking comes to mind. It isn't that the impossible becomes possible (mostly), it's that we find a smaller or different domain in which progress is possible and useful.
It must be hard, because so few people seem to do it. The history of humanity would look different if we didn't all seem to have to repeat the same mistakes.
I suppose at a hypothetical extreme you could be a Chinese Room-like puppet of the advisor. But in real life you have to generalize at some point. Behind the words of the advice is the understanding, which is the hard part. Understanding doesn't even necessarily follow from one's own experience. It takes the hard but irreplaceable work of reflection. One can try to reverse engineer understanding from advice, but regardless we can say that while experience may not be necessary, advice is not sufficient.
(In some vague sense of work-dimensionality: advice < understanding <= experience.)
We need to hire a couple programmer/analyst. No threshold experience level was required, because we want the best talent. After interviewing a dozen or so candidates, it occurred to me that someone with average intellectual horsepower, never seemed to mine the maximum value from the experience that they had. Why?
Either (i) they seemed to just store their experiences as a look-up table and then access it as a proxy for genuine creative thinking ("sure, i've seen that problem before, and we solved it this way ...." Granted, sometimes this expedient is just what you need, but it's undesirable if one's cognitive repertoire is limited in this way; or (ii) they failed to abstract that experience into broadly applicable principles. (I suspect this is the failure that is responsible when someone says "he/she has does not have five years of experience, they have one year of experience, five times." Without abstraction, unless your memory/recall is essentially perfect, it's difficult to actually use your experience to gain leverage over a new problem.
It gives you the understanding that something is a good or a bad decision sooner than somebody who hasn't had this practice.
Yes and no. You need to have some experience to understand the advice and interpret it to your situation. Everyone provides advice from their perspective, which is absolutely useless to you, unless you have the experience to convert that to your situation and learn from it.
Experience tends to pre-empt innovation: I really don't think this is caused by experience, I think it is caused by habit. I know a lot of people who have experience who have said to me "We did X, Y, and Z at my previous gigs, but I've been thinking...." Don't fall into habits and keep the sense of what if and experience provide a heck of a platform for innovation.
Experience takes time to get: yep - especially if you don't listen closely to the people who have already taken the hit.
You know some things to be impossible: more along the path of habits overshadowing experience. I had a huge amount of experience with Sybase databases. I knew some things were impossible given how they worked, but it didn't stop me from exploring when the next version showed up. Don't allow yourself to build a set of superstitions that overshadow changing conditions.
Screenshot: http://i.imgur.com/6SCgN.png, no addons in use.
http://cl.ly/3A0j1O0d180e2p3O1K02 from http://www.amazon.co.uk/Its-Not-How-Good-Want/dp/0714843377/
EDIT: Wow I never realized Obtvse came AFTER Svbtle. Controversial indeed. This is damn interesting.
Of course, now look at:
Is there any doubt what the value is here? That is an awesome front page. If you can clone that, you have better things to do with your time than pick fights with other developers.