Stop looking for a book. Best advice, I think, is to just write code. It will, eventually, turn into programming.
Learning to think like a programmer on some basic, novice, level is very much like learning a language. And one learns a language by memorizing a bunch of stuff and then speaking.
Once bigger challenges arise, one has to study. And one is able to study, only if they speak the language.
The pitfall of just write code, of course, is that the conventions and protocols and styles you're "of course" about (because you learned it all yourself) are things that may drive others batty. Like my preferred indenting scheme.
So, additionally, reading code and asking questions to other programmers should be part of the process as well.
I really don't think that a novice, that is just learning to think algorithmically should focus or be able to focus on following some conventions. As you say, one can 'learn that for himself'.
First thing to master is putting a thought into code. Conventions and best practices just add a layer of overhead on top of that.
So, additionally, reading code and asking questions to other programmers should be part of the process as well.
Definitely.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Stop looking for a book. Best advice, I think, is to just write code. It will, eventually, turn into programming.
Learning to think like a programmer on some basic, novice, level is very much like learning a language. And one learns a language by memorizing a bunch of stuff and then speaking.
Once bigger challenges arise, one has to study. And one is able to study, only if they speak the language.
The pitfall of just write code, of course, is that the conventions and protocols and styles you're "of course" about (because you learned it all yourself) are things that may drive others batty. Like my preferred indenting scheme.
So, additionally, reading code and asking questions to other programmers should be part of the process as well.
I really don't think that a novice, that is just learning to think algorithmically should focus or be able to focus on following some conventions. As you say, one can 'learn that for himself'.
First thing to master is putting a thought into code. Conventions and best practices just add a layer of overhead on top of that.
Definitely.