Perhaps almost as valuable as the important concepts might be a list of most frequent errors, and most frequent frustrations. We have all run into them, and most of us still do.
Sometimes, just having seen what troubles others have can help a person avoid those same troubles very early in the game.
Most important concepts to learn for a new developer (Top 50)
-
- Posts: 606
- Joined: Nov 28, 2012 1:27
- Location: CA, USA moving to WA, USA
- Contact:
Re: Most important concepts to learn for a new developer (Top 50)
Well, that is IMHO the second most important thing. First is debugging, finding your way around sources etc, getting your own answers.speedfixer wrote:Perhaps almost as valuable as the important concepts might be a list of most frequent errors, and most frequent frustrations. We have all run into them, and most of us still do.
Sometimes, just having seen what troubles others have can help a person avoid those same troubles very early in the game.
The second most important is documentation, forum and community in general, iow answers from others for when you need more input.
Re: Most important concepts to learn for a new developer (Top 50)
Best things that have helped me:
- Callbacks/Events
- Learning how to properly handle pointers
- Sorting
- Linked lists
- Vector math
- Interpolation
- OOP design patterns
- Program flow
- Input/Output
- Variables
- Arrays
- Subs/Functions
Re: Most important concepts to learn for a new developer (Top 50)
I also output what's going on during the program (especially more complex parts), and reading the log after a crash is my main method of debugging. I can catch the last activity and specific variable values. Works pretty well for me.grindstone wrote:For my part, the most important debugging "tool" is the PRINT command (either to screen or to file), occasionally in combination with SLEEP and END.
Last edited by mrToad on Nov 06, 2017 22:23, edited 1 time in total.
-
- Posts: 139
- Joined: Feb 04, 2011 20:34
- Location: Ontario, Canada
Re: Most important concepts to learn for a new developer (Top 50)
There are really only three concepts to learn:
1) Read -- buy a book, then repeat forever
2) Experiment -- write code and figure out for yourself why it doesn't work
3) Practice -- do this for 5 years to become a passable programmer
Failure to do all of the above indicates a lack of aptitude -- a different hobby/occupation is indicated
Rod
1) Read -- buy a book, then repeat forever
2) Experiment -- write code and figure out for yourself why it doesn't work
3) Practice -- do this for 5 years to become a passable programmer
Failure to do all of the above indicates a lack of aptitude -- a different hobby/occupation is indicated
Rod