New Programmer's Survival Manual - For CS Grads Looking to Become Professional Devs
Join the DZone community and get the full member experience.Join For Free
a computer science degree doesn’t prepare you to be a programmer. here’s an excerpt from a
i wrote comparing computer scientists and programmers:
i had a conversation yesterday with someone who said he needed to hire a computer scientist. i replied that actually he needed to hire someone who could program, and that not all computer scientists could program. he disagreed, but i stood by my statement. i’ve known too many people with computer science degrees, even advanced degrees, who were ineffective software developers. of course i’ve also known people with computer science degrees, especially advanced degrees, that were terrific software developers. the most i’ll say is that programming ability is positively correlated with computer science achievement.
how do you bridge the gap between obtaining a computer science degree and becoming a professional programmer? for years i’ve recommended that cs grads read code complete . now i’d also recommend new programmer’s survival manual by josh carter. this new book has some similarly to code complete. however, code complete is about good programming technique, not programming as a profession.
the survival manual has four parts:
- professional programming
- people skills
- the corporate world
- looking forward
the first part has the most similarity to code complete, though even there the two books are complementary. the second part, people skills, has some great advice, though i imagine most cs graduates will skim over this part because they don’t realize it is important.
cs students may do well to read the survival manual, especially parts one and three, to find out whether they want to be programmers. some who find abstract computer science fascinating will find a typical programming sorely disappointing. see mike taylor’s post whatever happened to programming .
a few of these may be able to find refuge as computer science professors, but not many. if you want to become a professor and think you’ll be able to get an academic job, watch so you want to get a phd in theoretical computer science and read no, you cannot be a professor .
the survival manual assumes the majority programmers will be working in cube farms on enterprise software , which is true. but there is a small middle ground between enterprise development and academia, jobs that will give you a chance to use advanced computer science without having to write papers about it.
one reservation i have about this book is that it may be overwhelming. if you have a friend who is starting a new career as a programmer, maybe you could buy a copy of the survival manual and rip it into chapters. then mail your friend one chapter a week.
another reservation i have is that new cs graduates may not benefit much from the book because they won’t believe it. they may deny that the real world is as josh carter describes.
the people who may benefit the most from reading the survival manual are programmers with some experience who want to improve their skills. they may have learned through hard knocks about some of the challenges carter writes about. also, carter describes life in a software shop with fairly high standards. those who are used to producing lower quality software will do well to read about life in an organization with higher standards.
Opinions expressed by DZone contributors are their own.