515 karma · joined July 15, 2011
While according to Harvard itself: "The total 2013-2014 cost of attending Harvard College without financial aid is $38,891 for tuition and $59,950 for tuition, room, board and fees combined."
Unless summer+part time work is a lot more lucrative than I am aware of, the only way this would be true is if the students (or their parents) were financially well-endowed. A student that doesn't have rich parents is going to be incurring a fair amount of debt or spending way too much time working instead of studying.
Edit: Harvard is generous with its financial aid, so the author's message is more accurate than I understood (at least for Harvard). Learned something.
The Globe article's title and the original title of the HN post focused on the electrical shocks, implying that people would prefer doing something very painful rather than think silently. I can't read the article itself, but the Science Editor's summary included this:
In fact, many of the people studied, particularly the men, chose to give themselves a mild electric shock rather than be deprived of external sensory stimuli.
Doesn't sound terribly unpleasant. That changes a lot in terms of the headline's conclusion, at least for me.
The cDNA part baffled me and many molecular biologists I know back then (and still does). I tend to think that either 1) the court didn't understand the science or 2) they did but were unwilling to destroy an industry so they found a loophole.
I hear the same tired arguments about fostering communication and the serendipitous meetings that spark great ideas. However, every single day and for at least 50% of the day, everyone in my open office either grabs headphones or runs away to another spot in the building when they need to get work done individually.
When I bring up objections, I'm told that I can work remotely or wear headphones. I don't see how forcing people to seek all sorts of ways to find privacy is any great recommendation for a purely open plan. If you spend the majority of your day talking and listening to others, I don't see how you can actually get programming done.
Edit: At this moment I can overhear conversations about opening day in baseball, April Fools day, SAP, reporting about inventories in Epicor, the weather, CNN, 3 people scheduling meetings and having phone conversations and one person trying to talk to our network provider. Not to forget, there are 2 people in the hallway complaining about personal issues and getting coffee. And an elevator that keeps beeping every few seconds. I can't wait to see what great idea all this is going to generate in my head.
I know it's not pure, but Java does force you to think in an object-oriented way. And there are problems where that's an advantage.
I spent way too much time watching the systems reboot after I understood that the dialogs were active. Very nice collection. Curious how this was done. Screen captures, recreated from videos?
Sorry, still not clear to me what you mean. Please clarify.
Consider the converse to your statement: It can sometimes be advantageous to spend all your time learning as much as possible about the way things are normally done while approaching the job from your own strengths and knowledge.
Nope. The converse of what I said would be: It can sometimes be advantageous to spend all your time learning as much as possible about the way things are normally done before trying to contribute to projects.
"you may delay contributing if you wait until you reach that status before trying" Certainly. However, contributing is also an important part of learning, and you are unlikely to get to expert status if you delay in contributing.
Yes, exactly. Fits with what I'm saying.
I'm sure you'll have something to say, so I'll leave you to have the last say. Thanks for the discussion.
I'm just saying that it can sometimes be advantageous not to spend all your time learning as much as possible about the way things are normally done at your new job/activity and approach the job from your own strengths and knowledge. In that way you may surprise yourself and others with solutions that they hadn't thought of because they couldn't see outside their box. You will become an expert eventually (if you want), but you may delay contributing if you wait until you reach that status before trying. And although you may look foolish or stupid if your naive idea was wrong, in my experience you don't get fired for trying. You just get embarrassed and then spend your time steeping yourself in the field's dogma :) It's just an observation ...
In the context of the article, having minimal knowledge (just enough to understand the problem), also affords you with the opportunity to learn more on your own and develop your own views before someone tells you how to think. While I can't back it up with level of evidence you're asking for, in my experience it's still a good strategy to go with. I realize this is drifting away from the original topic. Sorry about that.
This is an often overlooked opportunity. Learn as little as you absolutely need so you don't get mired in the dogma. Some of the best solutions for problems come from people who have not yet become indoctrinated in the "standard" methodology. They approach problems with a fresh perspective and can come up with new solutions that everyone else who's been there a while missed. This opportunity is short lived, since everyone inevitably learns all the standard ways, so it is very apt for when you join a new company.