This is an invaluable list. Third point is something that I did in school, but I definitely avoid most of the time nowadays. Very good catch, thank you.
I had it this morning : to provide a consequent portfolio, you might be consistent by filling the github's dashboard's cases to green; no matter the colour of tone.
In the list, i forgot to say that i write all titles to see what's available, and to use them to write pseudo-code, and then i dig deeper into docs for details. Another point, in my opinion, is to ask myself on what type of data do i work, to see if the operation i want to do already exists in a built-in class, or if i have to compose with them to write my own method.
Finally, when you make a mistake, the compiler talks to you and gives you a lesson, not a fail...
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.
This is an invaluable list. Third point is something that I did in school, but I definitely avoid most of the time nowadays. Very good catch, thank you.
I had it this morning : to provide a consequent portfolio, you might be consistent by filling the github's dashboard's cases to green; no matter the colour of tone.
I should definitely try it... please keep me posted on your experience with this.
In the list, i forgot to say that i write all titles to see what's available, and to use them to write pseudo-code, and then i dig deeper into docs for details. Another point, in my opinion, is to ask myself on what type of data do i work, to see if the operation i want to do already exists in a built-in class, or if i have to compose with them to write my own method.
Finally, when you make a mistake, the compiler talks to you and gives you a lesson, not a fail...