What kind of advise will you as a programmer give to someone who's new to programming and has the eagerness to learn. | Sololearn: Learn to code for FREE!
New course! Every coder should learn Generative AI!
Try a free lesson
0

What kind of advise will you as a programmer give to someone who's new to programming and has the eagerness to learn.

An advice to a new programmer

17th Sep 2017, 8:46 PM
Mark Joshua
Mark Joshua - avatar
3 Answers
+ 3
Study, practice coding and practice coding some more
17th Sep 2017, 10:54 PM
Joe Catoe
Joe Catoe - avatar
+ 3
1.You are not your code - Remember that the entire point of a review is to find problems, and problems will be found. Don't take it personally when one is uncovered. 2.No matter how much "karate" you know, someone else will always know more.- Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it's not needed. 3.Don't rewrite code without consultation. There's a fine line between "fixing code" and "rewriting code." Know the difference, and pursue stylistic changes within the framework of a code review, not as a lone enforcer. 4.Treat people who know less than you with respect, deference, and patience. Nontechnical people who deal with developers on a regular basis almost universally hold the opinion that we are prima donnas at best and crybabies at worst. Don't reinforce this stereotype with anger and impatience. 5.The only constant in the world is change. Be open to it and accept it with a smile. Look at each change to your requirements, platform, or tool as a new challenge, not as some serious inconvenience to be fought. 6.The only true authority stems from knowledge, not from position. Knowledge engenders authority, and authority engenders respect-so if you want respect in an egoless environment, cultivate knowledge. 7.Fight for what you believe, but gracefully accept defeat. Understand that sometimes your ideas will be overruled. Even if you do turn out to be right, don't take revenge or say, "I told you so" more than a few times at most, and don't make your dearly departed idea a martyr or rallying cry. 8.Don't be "the guy in the room." Don't be the guy coding in the dark office emerging only to buy cola. The guy in the room is out of touch, out of sight, and out of control and has no place in an open, collaborative environment.
27th Sep 2017, 10:04 AM
Shubham Shinde
Shubham Shinde - avatar
0
thank you shinde, you've given me a new way to approach coding and be good at it. I love your well-ordered and concise outlines. thank you, again
4th Oct 2017, 9:38 AM
Mark Joshua
Mark Joshua - avatar