How to be a Programmer: A Short, Comprehensive, and Personal Summary
samizdat.mines.edu
How to be a Programmer: A Short, Comprehensive, and Personal Summary
1–10 of 32 posts
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#2Shorter: learn, think, code, debug, solve, share, enjoy.
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#3a short summary?! i could learn python in the time it takes to read this.
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#4I presume the author is female, according to her use of the feminine pronoun in referring to programmers generally. Nice to get a female perspective. I appreciate her emphasis on all the qualities beyond coding itself that contribute to a good programmer.
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#5I presume the author is female, according to her use of the feminine pronoun in referring to programmers generally. Nice to get a female perspective. I appreciate her emphasis on all the qualities beyond coding itself that contribute to a good programmer.
Original Author's Bio
Robert L. Read lives in Austin, Texas, with his wife and two children.
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#6I presume the author is female, according to her use of the feminine pronoun in referring to programmers generally. Nice to get a female perspective. I appreciate her emphasis on all the qualities beyond coding itself that contribute to a good programmer.
I've actually noticed only a weak correlation at best between gender of the writer/speaker and the generic pronoun e uses. It's pretty common for people of the progressive set to use the feminine personal pronoun for programmers generically, which is a Good Thing (tm).
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#7I presume the author is female, according to her use of the feminine pronoun in referring to programmers generally. Nice to get a female perspective. I appreciate her emphasis on all the qualities beyond coding itself that contribute to a good programmer.
I've actually noticed only a weak correlation at best between gender of the writer/speaker and the generic pronoun e uses. It's pretty common for people of the progressive set to use the feminine personal pronoun for programmers generically, which is a Good Thing (tm).
As opposed to the gender-neutral 'they', which is the Best Thing (that few people seem to realise).
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#8As a Mines alum I can say I damn good first step to becoming a programmer is surviving a school as tough as Mines (if you're academically minded). I graduated with a chem degree but decided to switch to web development about a year and a half ago, and if there's one thing that school really taught me how to do was be a good learner which ended up being an awesome asset in trying to get hired.
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#9a short summary?! i could learn python in the time it takes to read this.
I think this is more of a meta-level write-up on being a programmer. For example, take a look at the "How to Know When to Apply Fancy Computer Science" and "How to Talk to Non-Engineers" sections.
Furthermore, I think that the writing is clear and succinct. I wish I had this when I started programming.
Re: How to be a Programmer: A Short, Comprehensive, and Personal Summary
#10Earlier quoted context omitted.
I've actually noticed only a weak correlation at best between gender of the writer/speaker and the generic pronoun e uses. It's pretty common for people of the progressive set to use the feminine personal pronoun for programmers generically, which is a Good Thing (tm).
As opposed to the gender-neutral 'they', which is the Best Thing (that few people seem to realise).
Many people still like to claim that 'they' can only be used as a plural.