mrowland

> no matter the project goal, your leadership team (the people in your reporting chain who care about the project) will always have basically zero technical context about the project compared to you.

This is not universally the case, and I've been much happier when I find teams and orgs where this is not true.

Good leaders understand the details. Find them. Be one.

"Weeks of coding can save hours of design"

On a personal level, children are optional; on a societal level they really aren't.

Here's my math:

15 weeks / semester * 2 semesters = 30 weeks. $5000 / 30 weeks = $166 / week. At $8 an hour, that's 20 hours a week; at $10 an hour it's 16 hours. (Ignoring taxes, which are low but still push the hours needed higher.)

This is not accounting for summer jobs, but my original point was that having the student contribution at that level will make some students take a paying but dead-end summer job over an unpaid internship or other opportunity that would benefit them more in the long run. (Another reason unpaid internships are questionable ethically...)

I've had on-campus jobs throughout college, and making $5000 from those jobs alone would require working somewhere in the neighborhood of 15-20 hours a week. Certainly possible (and many do it), but at that point it starts to have a pretty noticeable affect on your schoolwork and personal life.

Agreed. Student earnings requirements aren't much of a problem for CS/engineering students (who can get paid summer jobs related to their field), but they are difficult for students trying to get into industries where unpaid internships are effectively a requirement. You would think Stanford would have made a change to this as well.