I think its thinking with a mindset that you are writing a book.
Being willing to learn more and accepting constructive criticism. Accepting constructive criticism is very, very, important if you wish to be a coder. It doesn’t matter if the person is less experienced than you. If they have a fair point, you’ve got to accept what they said.
Another thing you never want to accept is that you’re satisfied where you are with your coding knowledge. There is always so much more you can learn if you only reach out your hand and try. I’ve been coding for awhile now and I’ve learned a lot but there is always so much more you can learn.
A couple years ago, I tried to create a
textarea that when you clicked on some buttons, it would add that letter to the
Another example, a couple days ago I posted a reply to a question which asked why the
input element did not require a closing tag. I, being pretty experienced with HTMl, replied that it did have a closing tag (referring to the slash and closing angle bracket
<input />). Pretty soon after that, someone sent me an article explaining that actually, the slash before the angle bracket was not required, thus showing that no ending tag.
As you can see, there are two responses to that. One is to get all high and mighty about it and not accept the constructive criticism. OR you can accept that because you’re a human, you’re not gonna know everything, and accept that you were wrong and try to learn from your error.
I guess that’s a couple different things, but all of them are required if you want to become a successful coder. Basically what I’m saying is, your greatest strengths would be your willingness to learn and being able to accept criticism from anyone.
Anyways, hope this gives you something to think about!
There’s no need to accept unconstructive criticism, if someone just wants to rail at you for no good reason. It’s also advice that applies across every aspect of one’s life, I think. If you can’t accept constructive criticism, you’ll likely not grow much in whatever aspect it is you’re trying to improve.
To add to what @stevencopeland has said, though, as well as being able to accept constructive criticism and feedback on your work, you also need to be willing to accept that you’re not going to be able to do everything immediately.
One of the things I’ve found helpful, though your mileage may vary, is to set myself a “challenge” of sorts. The whole reason I know any programming languages at all is because I thought “I wonder if I can build/code/design/program X”… then went off and learnt how to do it. Codecademy has been great for getting the basics of several things down, but along the way to getting my hobby projects off the ground I’ve bought numerous books and spent goodness knows how long reading documentation and articles to figure out how to do stuff.
In short, being willing to put in the time to get better and constantly improve what you can do will make you a better programmer.
Your greatest strength as a code is reading these long answers
Just kidding, but you should read these answers!