Now I have one more anecdotal confirmation for my hypothesis that all advice is bullshit.
I notice that the section on Networking has nothing to do with building cross-company relationships with your peers and future business contacts.
Nothing is said about interviewing or salary negotiation.
Suspiciously absent is the section about how to balance doing something correctly against doing it profitably--or how to stop arguing with your manager before you get fired.
I have to assume that someone majors in computer science as a means to land a job in the field. We all know that hobbyists don't need the expensive degree credential. The vast, overwhelming majority of work now available for software professionals is to take someone else's shit code and make it work better. A very tiny fraction of it is producing all-new code that is done right the first time. As a new grad, you are probably not going to get that work, and even if you do, your inexperience in the real world will probably still make it shit code that someone else will have to improve.
You do need a resume, even if you have a stellar portfolio, because the majority of available jobs are filled by people who don't know what a github is, or how much their mechanic charges to fix it.
It is blindingly obvious that the writer is an academic, who has never held a developer position in a startup, a mid-cap, a megacorp, or a government.
In the real world, the only skill you absolutely need is to learn exactly what you need to be productive. You don't just make yourself "T-shaped"--you also cultivate the ability to make yourself "Pi-shaped" by quickly growing a new stem of deep knowledge.
I notice that the section on Networking has nothing to do with building cross-company relationships with your peers and future business contacts.
Nothing is said about interviewing or salary negotiation.
Suspiciously absent is the section about how to balance doing something correctly against doing it profitably--or how to stop arguing with your manager before you get fired.
I have to assume that someone majors in computer science as a means to land a job in the field. We all know that hobbyists don't need the expensive degree credential. The vast, overwhelming majority of work now available for software professionals is to take someone else's shit code and make it work better. A very tiny fraction of it is producing all-new code that is done right the first time. As a new grad, you are probably not going to get that work, and even if you do, your inexperience in the real world will probably still make it shit code that someone else will have to improve.
You do need a resume, even if you have a stellar portfolio, because the majority of available jobs are filled by people who don't know what a github is, or how much their mechanic charges to fix it.
It is blindingly obvious that the writer is an academic, who has never held a developer position in a startup, a mid-cap, a megacorp, or a government.
In the real world, the only skill you absolutely need is to learn exactly what you need to be productive. You don't just make yourself "T-shaped"--you also cultivate the ability to make yourself "Pi-shaped" by quickly growing a new stem of deep knowledge.