Timeline for I'm graduating with a Computer Science degree but I don't feel like I know how to program
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 18, 2012 at 13:20 | comment | added | onemach | stackoverflow.com/questions/1711/… this may be a great list | |
| Jul 15, 2011 at 18:43 | history | edited | Joey Adams | CC BY-SA 3.0 | Added nonbreaking spaces in "Never stop learning", as it word-wraps after "Never" in my browser. |
| S Feb 4, 2011 at 19:27 | history | suggested | CommunityBot | CC BY-SA 2.5 | grammar OCD. |
| Feb 4, 2011 at 19:25 | review | Suggested edits | |||
| S Feb 4, 2011 at 19:27 | |||||
| Feb 4, 2011 at 19:21 | comment | added | BrianV | I would also suggest 'The Mythical Man Month' by Fred Brooks. It's more about project management than actual programming, but it will give you an idea of the various constraints facing any project you get involved in. | |
| Feb 4, 2011 at 18:56 | comment | added | Gareth Davidson | @mrjohn, each language you learn opens up a new way of thinking. If you're a hammer then everything looks like a nail; if you're an OOP programmer than you'll solve all problems using OOP, even if a more elegant solution exists in another paradigm. | |
| Feb 4, 2011 at 15:07 | history | migrated | from stackoverflow.com (revisions) | ||
| Feb 4, 2011 at 14:21 | comment | added | mrjohn | I disagree with the comment on knowing one or more languages. Although it cannot hurt to know more than one language, it is not what makes a good programmer. Know logic and how to analyze goes beyond knowing a programming language, once you master these you can apply it to any programming language. | |
| Oct 28, 2010 at 6:20 | comment | added | Lavir the Whiolet | I would also advice B. Meyer's "Object-oriented software construction" and related books. | |
| May 15, 2010 at 19:42 | comment | added | Péter Török | @Denilson, could you have learnt multiple languages without learning one language first? | |
| May 15, 2010 at 0:51 | comment | added | Russell Dias | @Denilson OP has stated that she does not feel she knows how to program. Knowing one language for someone who is unsure about programming is good. My list is only applicable to this context. | |
| May 14, 2010 at 23:06 | comment | added | mmc | "Start Small" refers not only to selecting approachable projects, but starting to implement workable portions within a project. A project of mine started with a little experiment in parallax, and me thinking "that looks like a pretty cool star field for a background of a game". Add a ship... add an alien... add a few missiles, keyboard control and collision detection (each simple problems, by themselves) one at a time and soon, I had a commercial game I sold for (what I thought at the time) a good bit of cash. On the other hand "write a game" is a vague, unapproachable task. One bit at a time. | |
| May 14, 2010 at 19:20 | comment | added | Denilson Sá Maia | "Knowing one language is good" -> wrong. Knowing one language is not enough. Knowing multiple languages is good, learning even more languages is even better. | |
| May 13, 2010 at 23:56 | comment | added | lemon | Add Clean Code to your to-read lists, it's pretty good. | |
| May 13, 2010 at 0:49 | history | answered | Russell Dias | CC BY-SA 2.5 |