There's no speed limit. (The lessons that changed my life.)
sivers.org
sivers.org
By combining courses from the Architecture, Film, and CS departments, I created a 'Digital Media' degree which doubled my salary in the graphic design department I was working in at the time. (My responsibilities stayed exactly the same). Since then no potential employer has asked about it, but it set the precedent for paying me more money.
Lessons learned: 1) You don't have to follow the same path as everyone else. 2) For plenty of places, the fact that you have the paper means more that what's printed on it.
That is what I like about this community as well. There are no artificial barriers to learning or to getting anything done. You don't need credentials or permission. It is in your hands.
Actually I think the barriers are still high. People are still hung up on credentials, and a team of startup founders from Harvard or Stanford always gets free publicity from the media and probably more investors as well.
Traction solves all other problems. Make something people use.
I truly doubt Zuckerberg would have been able to convince people from Harvard to use Facebook back in it's inception without being from Harvard himself. Harvard is a seed market because it's Harvard. Podunk state college is not a seed market because people back then would rather have used one of the better existing solutions such as Friendster back then.
The only reason that I and many others joined back then was because of it's exclusivity. We would have used Friendster, Livejournal, or maybe even joined Myspace for the sake of a superior product.I am quite confident that Facebook would have died in it's infancy had it been created in some state college.
The whole exclusivity in the beginning was the sole reason that it was able to make it this far.
Tumblr's David Karp dropped out of high school.
So may be 3months/3days is a little off balance, but you do need downtime.
Not to mention, those 3 months aren't necessarily wasted doing nothing - just different things. I did this through my mechanical engineering degree in college, and spent the rest of the time hacking on code... guess that paid off :P
The vast majority of the people I met while I was there were simply were not seasoned enough to tackle anything of considerable scope. Yeah, they were technically coders, but most had little experience outside of their CS courses and maybe a little bit of extra hackery on the side. Someone who was fluent in HTML, CSS, JS, and, say, PHP, was practically non-existent... and the ones who were there were the aforementioned "alphas", who were more interested in shopping for cofounders on their project than joining someone else's. In short, Velocity was 10% seasoned coders looking for partners (and not finding any), and 90% dreamers with no significant talent or experience to contribute to anyone's project. I'm making this sound very harsh, but I was very disappointed in the calibre of people they were able to recruit.
In a startup environment, especially one that's operating purely as a small team of founders, you cannot have "the Java guy", everyone has to wear a large number of hats - and this talent pool simply did not exist in Velocity.
I can't help but think the whole concept a dormitory-as-incubator is somewhat misguided. IMHO it would be much better served for everyone to simply have a streamlined collaboration system where entrepreneurially-minded people can find each other, and to provide basic resources (how 'bout some servers instead of flashy phones?) to help them get there. Think JobMine, but for student projects.
Oh, and one more thing: Waterloo is a town filled with tech startups, yet Velocity's only backers seem to be large corporations. This is unproductive - you don't need talks by big-company VPs about how they admire our spirit and independence... we need talks by startup guys who are in the thick of it themselves.
As far as the big corps vs local startups go, new Velocity management seems to be taking big steps towards fixing it.
Honestly, Velocity as it is right now, is just a convenient place for my existing team to collaborate. I don't really have any expectations of picking up new people since they're 1 in 1000 at Waterloo.
Net net tho, things are improving and I look forward to people playing rockband less and actually doing something useful :P
Now, I realise that they practise more than I do. It's even tougher for them, because there is no easy way to judge how much better they have become. And they have to do all that they do with people constantly judging them.
Engineers, scientists, mathematicians - we have it real easy. Our talent is an easy one to develop, it's an easy to make money from, and it's easy to get good. Artists & Musicians who manage to be successful have achieved a lot more than engineers who manage to become successful.
The effort he puts in just to graduate each year is more than I have put into my entire career so far (including uni)!
Like Derek, John and John finished their Berklee education early, but in their case it was by recruiting the rest of their band and dropping out to get started. That was in 1985. Their first major commercial success (in the sense that applies to progressive metal bands with cult followings) was 1992's Images and Words.
Source? (Not that I doubt what you're saying. I want to read more from where that came from)
I like to think I chose the two hardest majors in the school, but the music major was two orders of magnitude more difficult for me. I'm sure there's people for whom the opposite would be true, but I think an attempt at objective ranking would put the music degree as harder than the physics.
Mastering the basics is hard enough... being able to apply this knowledge creatively takes it to a whole other level.
Additionally music is recognized as a legitimate, serious form of artistic expression. Complete strangers can have deep conversations over people they've never met and techniques they don't understand. If you bring up programming as an art form, a lot of people will just laugh. Start talking about closures and their eyes glaze over.
One thing though is that the barriers of entry into each category is different, music requires a lot more time and devotion and going on to make money can be more difficult because you aren't hired just by the fact that you have a bachelors concentrating in music.
This is somewhat true of engineers as well, but you can certainly get an engineering job where you don't need to exercise your creativity.
That's really all I can say. I agree with this so much. (Wow, I'm articulate!) I just wish it were easier to do.
Personal story: I'm in high school right now. Many of the courses I'm taking are very... high-school-y. Low on content and high on busy-work and hand-waving. Some, though, I find are actually well taught; namely, my Statistics course and my Multivariable Calculus/DiffEq course. The teacher for the Stat course posted all the homework he plans to assign (all out of the book) online; while the teacher for Multivariable hasn't done that, he assigns the same homework every year, so I managed to get his homework from previous students. Currently, I'm done with my statistics course and 3/4 through the multivariable course, where both of them should be full-year courses. It just feels amazing to be learning at my own pace - the class speed in high school (and, I guess, college, and perhaps life) is catering to the lowest denominator. I know that I, and many of my classmates, could easily double or in some cases triple that speed.
Looking back, I wished I had slowed down. Being years ahead has certainly put me ahead of my age group, but there's a huge amount of value you miss when you dump all your effort into academic learning.
My advice is to take 20% of that passion and speed and put it into learning about people and social interactions. The high school theatre class I took has been more valuable in the real world than number theory or compilers.
TL;DR - Been there, done that. Found out that being well rounded and socially engaging is a force multiplier on being deeply technical.
This is probably a result of my own college experiences. I coasted through high school pretty easily (eg, doing tomorrow's calculus homework in class while it was still being explained). Then I went to a pretty good college, with a bunch of other people who were skilled enough to coast through college.
I got my ass handed to me. We all got our collective ass handed to us. It was humbling. It was also glorious. A year-long back-of-the-room calculus class was turned into a very engaging first 2/3 of a half-semester calculus class. Then, a year's worth of math at that pace was compressed again into six weeks of summer school thick enough to kill a man. I didn't put in extra effort learning beyond my classes, because the classes themselves kept me up til four in the morning.[1]
So, in short, I agree with the title of the post, you should be learning/acting at your level, not below it. However, I disagree with the main corollary of the post, which is that school is insufficient to reach that level, and you should buck the system because it's not good enough. There are schools good enough. I think it's better to find the appropriate system than to buck a normal one, because you have a much more support.[2] Slamming through four math courses in a month is a lot easier when you have four professors and a dozen peers who are all on the same page as you. You also happen to learn a lot about teamwork and collaboration that you might not by going solo.
[1] Which is not to say that every waking second was spent working; I covered 6 seasons of Deep Space Nine and 4 seasons of Babylon 5 in a year. Rest is more important than sleep.
[2] The better support is also self-reinforcing of the quality of the peers. If there are students performing below the bar, a school that can raise those students up doesn't have as great a need to lower the bar for them.
I always hear two sides of the argument that a) a la Mr.Sivers, oh you need to learn how to play fast, memorize all of these scale/chord patterns, and every single guitar-player style from Blues to Jazz to Folk to Pop, or b) you shouldn't worry too much about playing or learning too fast, but concentrate on the music; enjoy yourself, find your own style and get in the zone and slowly you'll understand how to improvise, compose and tab by immersion rather than memorizing patterns. (Because if you try to learn or play too fast, you get frustrated quickly that you aren't doing well and concentrate too much on the mechanics of note perfection that it affects your performance). Some books I read recommend daily practice sessions of only 20 minutes per day, but consistent daily practice.
I'm sure I'm painting a totally false dilemma but curious as to how some of the pro musicians out there takes are.
EDIT: Since we are on a programming forum and I assume that the advice is geared towards developing for startups, IMO, the best way to learn how to program is to learn by working on your own project and ruthlessly plagiarizing off of other people's open-source code base. Because you are motivated to finish the project because it's something that motivates you and you are forced to look deep down into the stacks because you almost always have to customize/hack 3rd party code to do something your way.
Scales and chords aren't patterns per se -- they're the fundamental building blocks. They're the equivalent of syntax in a language. Not knowing them well is like having to think about where the semicolons and/or braces go when you're writing a for loop. Being familiar with chords/scales allows you to think about music at a higher abstraction level.
You can make exercises less boring (and more effective) by varying the way you play them. Vary the rhythm you play (triplets, etc), switch between legato/staccato, and so on.
The Deep Practice section of The Talent Code (http://www.amazon.com/Talent-Code-Greatness-Born-Grown/dp/05...) may provide more inspiration for how to practice effectively.
My fiance is learning to program, through the excellent Learning To Program (http://pine.fm/LearnToProgram/). She's taking at a comfortable pace so she doesn't get bored or frustrated - but she's doing it for fun and enjoyment, to round our her skill set (she's an architect), not with serious intentions of programming as a career.
All evidence points towards the fact that it takes human beings 10k-20k hours of practice to really master any skill. You'll never master music if you're practicing 20 minutes a day - and you won't be a great programmer until you've put in years of solid coding. But if you're just doing something as a hobby, it's more important to avoid getting frustrated (and giving up) then mastering it.
The first day of class he handed out our coursework for the semester. I asked if it was OK to hand in homework early. He said it was. The next class I handed in the first 3 days of homework. The following I handed in 3 more. The third class I said there didn't seem to be much point in my being there, did he mind if I just handed in the homework?
A few weeks later when I walked into another course I was taking with a lot of the same people a lot of them started congratulating me. I was puzzled. They explained that one had asked whether I was dropping the class since I hadn't been going and so they heard that I was actually taking the final exam that day.
I did the follow-up course the following month. :-)
Another time I taught my brother the basics of differential calculus in about half an hour or so. Well enough that he was able to go into a course that had that as a prerequisite and he managed to ace that course.
So yes, the difference between what we are asked to do and what we can do is pretty large.
I try to remind myself constantly that the icons of business and technology that I use as examples of extreme success probably don't spend much time on social networks.
HN is the last one that I frequent, and I've been cutting back my activity here too.
What I learned from this was: 1. Set microgoals. (Or, in my case, have them set for you.) When you break down a project into steps, you can do each one in one go, not allowing yourself any distraction during a step. Better to take breaks between them. I don't know a thing about programming, so I don't know if you can find any hour-long steps, but that's what I'd recommend. 2. Try to do an insane amount of those micro-steps each day. Like, four times what you're used to. The danger is discouragement, but: 3. Save an easy task for the end of the day. As a freelancer, I face a lot of rejection. That's normal (but honestly my pitches are particularly bad). So I try to save some simple, non-failable task for the end of my work time, so I don't finish with a sense of failure. 4. Find someone who loves the shit out of what you're doing. There will be someone. You just might have to find an amateur who's really impressed with what you're doing. If your work is technical, talk to some journalists or other creative types. Vice versa is true too. Explaining things to an interested noob is satisfying, builds your self-esteem, and will probably lead to brainstorming. You don't need someone who can point out flaws. That's for later.
That's all I got for now.
I would argue that most high school students find their studies meaningless, but not because they are bored by the triviality. They think it's meaningless because they don't comprehend the practicality of it all. They get stuff just to get it done, to avoid getting spanked for bad grades, or to satisfy their ego. So our school system shoves these topics down the students, with the hope that shoving hard enough and enough times will do the trick. But from personal experience, I've found that when I revisit something that I once learned, I usually look it up in reference either from the internet or from a book. The interesting difference is that this time, when I truly comprehend the importance or relevance of it all, I learn it in much less time.
Teaching kids what they aren't ready to learn yet is inefficient. Standardized pace, rigid curriculum impede students from learning what they want, and at their own pace (which will probably always be faster than the standard pace if the student is interested).
This problem extends into university education. I think all students should learn like that, at their own pace, and take some evaluation, not necessarily a test (I have ADHD, so I'm biased against tests), at the end. Then we can have quantifiable knowledge without forcing students to go through a rigid curriculum at a set pace. This hopefully would also mean no more banking on getting into good universities, rejections, and entrance exams determining education worthiness. Education would truly be open and accessible to all.
Spending 2.5 years finishing college and 1.5 years doing something else is no better/worse then spending 4 years finishing college. It only matters that you lived a good life during those four years. I believe "There's no speed limit" is bad general advice. It's good for the driven overachiever types, which I believe are a niche. But for most people it focuses them excessively on future payoffs and makes them miserable when the don't/can't overachieve.
It's the difference between working all the time so one day you can own your very own rosegarden(and likely never do) and taking the time to stop and smell the roses today.
This is very useful when it comes to management, and a great way to encourage someone to grow and develop : expect a lot from someone, and find a way to communicate that you're completely confident they can achieve those expectations.
Any one seeking to master any field should go through the litmus test that experience provided him as early and often as possible. No parallel to learning at the hand of an accomplished practitioner.
But seriously. Maybe the message would then be: there is no curfew.
Pop is hard.
(I still don't like it.)
If your IQ is off the charts, maybe. Try studying chemistry sometime. There the standard pace is to weed as many as you out in the first few semesters as they can. The women are the first to go.