A Commencement Speech For 2013 CS Majors
blackbearnh writes "Most commencement speeches are long on platitudes and short on practical advice. O'Reilly blogger James Turner has tailored a speech aimed specifically at the current batch of graduating CS majors. Among the advice that the 35-year industry veteran offers are to find a small company for your first job, but not one that is going to burn you out. Also, keep learning new things, but don't fall into the trap of learning the flavor of the day technology. Quoting: 'Being passionate about software is critical to being successful, because the field is a constantly moving target. What will net you $130K today will be done by junior programmers in five years, and unless you're constantly adding new tools to your belt, you’re going to find yourself priced out of the market. ... You are rarely going to get an opportunity to have your current employer pay for you to learn things, so learn them on your own and be in a position to leverage the skills when a new project comes along. But if you have a passion for technology, you'll already be doing it, and enjoying it without needing me to tell you to."
Be resourceful. Find ways to do your job without complaint or constantly and chronically asking for the next task to be done.
Do these two things and your will be prosperous.
(sits down to great cheers for having ended the speech in 30 seconds)
should also say don't go for the masters with out some real work to back it up.
In the past 10 years how many CS graduated did you have to fire/have had fired because of their inability to learn something new? (i.e. because they need classes to hold their hands). Parent's shouldn't push their kids into a field about which the kids have no passion.
You have several million other people with cs degrees out there right now. Most of the ones from last year still don't have jobs. Let alone in computers...
I suggest you start practicing for the job most of you will end up with.
"would you like fries with that?"
That's ridiculous. None of the jobs that interest me offer anything near that much, even for senior management. I guess he is silently implying that you find a job that will bore the hell out of you but pay well.
I'm not buying that, as a summa cum laude graduate, I want a job that challenges me. I could have settled for software engineering or even some mickey mouse IT degree if I cared about salary. Honestly, I think computer science is too lumped in with software engineering these days.
It must have been something you assimilated. . . .
"Don't sit on your ass and expect the world to come to you." Speech.
find a small company for your first job, but not one that is going to burn you out.
It may be easier to prove that unicorns exist...
I think the key is to know when to get out... of course there can be other reasons for staying.
and schools need to be more trades / tech school like to much theory leads to skill gaps.
> and schools need to be more trades / tech school like to much theory leads to skill gaps.
Parsing error.
I'm sorry, but this is the vague timeless advice that isn't targeting the class of 2013. It gives no information that is insightful for today's graduates that wasn't also true for the last 30 years.
Even start-up / small companies have been an aspect of the industry since... what? The 80's? Before that you needed some capital just to afford a computer.
Why doesn't he address the upcoming death of the desktop? That China and India are developing a middle class and that China is graduating more engineers than the USA has citizens? The effects of large corporations steering large OSS projects into the ground? That the hardware has bottomed out and full computers only cost you $30. What about the consolidation of the Internet? Or how about the war on general computing? I mean, these are computer science majors, I imagine it's kind of a thing for them.
I don't know that I'd say that. Honestly, software engineering broke off from computer science for precisely that reason. I would like to see CS curriculum stay theoretical, and leave the implementation to software engineering degree programs.
So many schools these days are dropping CS altogether and replacing it with software engineering, I would have to say that what you're asking for is effectively already happening.
I've been an IT professional since '95. Unix admin / DBA / network admin / SAN admin / Release Engineer / etc. etc. This advice really speaks to my career. You have to have passion for technology and you have to be willing to learn new things on your own. I run into so many people who want nothing to do with technology when they go home. I feel they are in the wrong industry.
-- Thou hast strayed far from the path of the Avatar.
I'm doing the same thing today for my $150k that my predecessors were doing for their $100k 10-12 years ago.
research and theory = a poor setting to learn job skills and people in that setting may just do the min to pass and you can really see that in the filler and fluff classes.
Kill Philosophy/History/Art etc and focus entirely on STEM and nothing else. as well have a more hands trades / tech track.
The well rounded and a time overload of gen edus is pulling the tech schools down.
and the same people think CS = IT work
now CS is more on the programming side. But on the other side not only is there some skills that need to be very hands on Like Cisco / networking they have certs that you need to know stuff and do it in a real IT lab setting. Also others parts like desktops / servers 4 years pure class room is extreme over kill.
the college system is stuck in the past and the push for all to got is dumbing it down and hurting the tech / trades schools as well.
Strike that. Reverse it.
research and theory = a poor setting to learn job skills and people in that setting may just do the min to pass and you can really see that in the filler and fluff classes.
I don't know how many times I can stress this. Computer Science is not supposed to teach trade skills, there are specialized programs such as software engineering for that purpose. At my school, many of the students who could not hack theory quickly dropped out of computer science and enrolled in either information systems or software engineering; the way it should be.
In one of my past jobs I covered for other staff when they "couldn't be there". In two years at one location I worked one year of overtime. That is, I worked 2,000 hours of overtime in two years covering for people who, generally, just didn't feel like working. Oh, and this was at a location where 11 people worked. Shift structure was 2 people on day, 2 on afternoon, 1 on night shift, times 7 days a week. 392 total hours for the week and I averaged working 60 of those. So yeah some people just skip work.
I come here for the love
i thought commencement was supposed to be about life, the universe, and everything (TM).
here i come to find out it's supposed to be career advice like you'd find on any thrid rate jobs website.
thanks!!!! im glad i will spend 40 years with my head down in a cubicle, never thinking, never questioning, never acting on anything other than my desire to have a shit hot career and a fuckton of money.
i mean, that's what "success" is, right?
i'm pretty sure Steve Jobs book was full of practical, sensible stuff like that.
“A lack of planning on your part does not constitute an emergency on my part.”
The question is, how to effectively communicate this to clients.
apprenticeship system can fix that and add real training. So you get people who know what they are doing not test crammers who can pass the test but not know that much.
Well the old MS tests started some of the memorization drones and having questions that seemed to be set in setting that you would have hunt to find.
"What will net you $130K today will be done by junior programmers in five years"
That really depends on why you're getting paid a premium. Is it because you have experience with the current "hot thing", or is it because you are capable of crafting correct, performant and elegant solutions to hard problems? If it's the latter, then that probably won't be "done by junior programmers in five years".
You are rarely going to get an opportunity to have your current employer pay for you to learn things, so learn them on your own and be in a position to leverage the skills when a new project comes along.
Tech employers, mind that most white collar employers *do not* pay for training anymore like it was 20yrs ago. I remember in the old days I used to get OOA/D training, UML instruction, code optimization, real-time development, etc... today? Nada! You're on your own kid!
Training drives the salaries in this industry, period. s/w development is based on things with a design (e.g. languages), so there is truly 'nothing new invented here', just things to discover and exploit. And the only way to become useful is training. You can read an O'Reilly book, but its nothing compared to real hands on training. Employers used to do on-hands training, but found it to be very, very expensive to the bottom line. And with the culture of s/w development, hey the employees are willing to train themselves... AT THEIR OWN COSTS. So, why not take advantage of the cultural aspects of s/w employees?
So what I'm saying here is everyone here should demand top dollar for their salaries. Low ball salaries, low bids/rates, outsourcing, etc... it does hurt the industry and technical progress because we have to train ourselves--that's VERY costly if you think about (aka "time is money"). It really recovers the cost of training a corporation should (and once did) be providing in the 1st place... I mean they are investing in you as a resource. Right?
More from the speech:
Thank you,Dean Martin,
President Sinclair...
and members
of the graduating class.
I have only one thing
to say to you today...
it's a jungle out there.
You gotta look out
for number one.
But don't step in number two.
And so,
to all you graduates...
as you go out into the world
my advice to you is...
don't go!
It's rough out there.
Move back with your parents.
Let them worry about it.
Hey, everybody! We're all programmers. Let's never get laid!
(-1: Post disagrees with my already-settled worldview) is not a valid mod option.
Junior programmers will inevitably recreate what you created. It is then your job to grumble and start the task of putting proper locks in their code and running it in valgrind.
The current generation of kids (graduating since early-2000's onward) grew up in a consumerist economy: be the "one" and you'll be rich! Accomplish this by pursuing a degree in a field of study perceived as financially viable regardless of the greater economy's need for such "specialty."
Too many kids graduate without being prepared for adulthood -- much less the responsibilities expected of them that goes in-hand with a commanding financial package. These kids dutifully do their homework but never truly appreciate the significance of the assignments. This is the real truth: apply your homework assignment to some new-fangled idea that is more significant than yourself then quit school to pursue it to its fullest.
College drop-outs financially succeed not only because they take risks, but also because they actually appreciated what was taught to them by applying it in the real world. Some drop-outs were not computer geniuses... rather, they are the unsung heroes who go to work day-in/day-out with recognition for being young, ambitious, attentive to detail, and reliable workers (either as programmers, analysts, or support staff).
Moral of the story: do something worthwhile in college instead of waiting for Godot after shaking some person's hand with a rolled up piece of paper.
How about we ditch the Software Engineering curriculum entirely, and stick with CS? Because standard software engineering practices produce nothing but a lot of paperwork behind overbudget projects.
Well, the first thing to understand about this article is that it treats software engineering as a pure meritocracy.
Maybe at some places it is.
However, for me the important film is that timeless documentary, Office Space, which drummed into my head two things that I actually found to be true:
1. If you are good at office politics, you will be called "a straight shooter with upper management written all over him," if you are merely good at creating software you will be "Mr. Samir Naga... Naga... Naga... Not gonna work here anymore, anyway."
2. Even being a successful office politicker like Peter Gibbons or Bill Lumbergh, you will still possibly find that you have a hateful, soul crushing job that drains away your life and enthusiasm every day.
What does this mean? Well, it means that you have to decide early on whether you are chasing a good life or an early retirement. chasing the good life means hanging on until you get a job you can tolerate, early retirement means making as much as you can so you can get out as fast as you can. Or perhaps being hit by a truck so you can work at your real passion, "A Jump to Conclusions" mat.
All in all, I think wire fraud and armed robbery are probably more satisfying careers much of the time.
"MIT betrayed all of its basic principles."
the college system is stuck in the past and the push for all to got is dumbing it down and hurting the tech / trades schools as well.
WTH?
Sorry, but how is the recent suckage of colleges and universities hurting the people with HVAC, Diesel, Plumbing, Electrician, etc. training from Wyotech again?
How are these things even comparable?
Uh, you got that backwards.
Best Advice EVER. Wish I had become a plumber or electrician, unfortunately my stupid father talked me out of it.
Now in my 50's. Two Master's degrees (CS and TEL). Zero job opportunities.
Oh well. I am learning to live off the generosity of others, and take great comfort in not having to work to live while others rack up their heart attacks and stress-related impotence. Exercise, reading, films, sex. It fills my days.
"Pick the right technologies to learn." - If you could do that, you could INVEST in the right technologies and NEVER HAVE TO WORK because your omniscient self would know what was going to be big and what wasn't.
"I’ve never been hurt, career-wise, by waiting a year or two to learn a technology, because that’s when a truly useful item starts to show up in job positions." Dude, if you wait 2 years to learn a new technology, YOU WON'T EVER GET A JOB because companies ONLY HIRE PEOPLE WITH EXPERIENCE. You will have doors slammed in your dabbling, lagging face if you take this approach.
Were people in the audience throwing rotten fruit at this guy by the end?
Sorry guys (and gals - yes I know there are a couple of you out there), I won't play this game anymore. I recently have been faced with a life threatening (potentially weeks to months to live) illness (still trying to determine what it is). I have been chasing tech since the 80's and after first hearing I may not have long to live, I shit you not, I actually felt relief. I'll skip the rest of the drama, but it didn't take long in my thought process to decide with whatever time I have left, I am going to pursue things I actually like, instead of worrying about the next technology MS or Oracle or BigCompanyThatWantsToOwnMyAss is going to shit out, then kill and reinvent once again.
No thank you. I really enjoy retro computing, so that's what I'm going to do. That's what got me into computers in the first place. If I don't pick up the technology on the job, I'm not chasing it down. Kiss my ass.
Look boys and girls, if life sucks, then change it while you have time. Don't keep living the sucky life. Get on with what you want to do, and do it now. Regardless of my outcome, I am now free. Thank you. That is all.
I don't know that I'd say that. Honestly, software engineering broke off from computer science for precisely that reason.
You say that past tense, as if it has happened.
At best, in education, the split is in its early stages. Most schools do not have a SE program except as a specialty within CS. Many do not have a SE discipline at all.
In industry, it's the other way around, but industry doesn't (and won't) train the next generation.
this message is also appropriate for the it boys