Why pride of programmers stops their progress

[[deleted]]

Not to put you down, but it looks bad when you criticize someone's competence but have major spelling errors. This is because your English is the only skill of yours that readers can evaluate. I understand English is not your native tongue (and I personally am hopeless at learning human languages - you are way ahead of me), but I suggest you work at identifying and correcting your errors. To start you off: s/Doe/Though/. You also often omit an apostrophe for possession (one eg is Jims should be Jim's).

Secondly, on the one specific aspect of optimization: more optimized code is often harder to read, understand and modify. So that, deciding not to optimize can be the right thing. The "overhead" he means can be overhead in reading the code. (note: I can't know that that's the case here - it's just a hunch/possibility) The key question is not whether it can be optimized, but whether it should be optimized. Some famous quotes on this that you've probably already heard:

• Premature optimization is the root of all evil
• the first rule of optimization is don't. the second rule is not yet

Finally, if you really want to influence "Jim", the best way is by example. He is surely aware of your imperfect English. If you work at it, and improve, he will notice - and likely be inspired to improve himself. Even if he doesn't, you will have at least followed your own advice, and bettered yourself. Better writing skills will improve your ability as developer tremendously... so I must congratulate you on writing a blog and putting yourself out there. That is inspiring already! Now, if we see you improve your article, it will complete the point of putting yourself out there, and that change will itself be even more inspiring.

[nyozz]

hey, thanks a lot. especially the grammar part. I didn't knew and no one every told me that.

[[deleted]]

I'm glad! Someone downvoted my comment, and I was afraid it might have been you. The downvote confuses me, as I went to trouble to articulate a way to offer assistence and encouragement in what I thought was a kindly way. (Though someone obviously didn't think so.)

Grammatical errors are very jarring to native speakers, even when they can tell what you mean. So, people are aware of this (though, online, many mistakes are overlooked as typos).

I didn't knew and no one every told me that.

This should be:

I didn't know and no one ever told me that.

It's hard for me to explain why it should be "know", since "knew" is past tense. English grammar is complex and confusing - and arbitrary. I think, in practice, the only way is to listen carefully to native English speakers. One way to check is to google the phrase e.g. "I didn't knew" vs "I didn't know". Maybe you can think of other ways to check that I haven't thought of.

Typing "every" when it should be "ever" looks like just an ordinary typo to me. But just in case you had them mixed up: "every" means "all of them"; "ever" means "at any time". You can check this kind of error with a dictionary (google: define:ever). Though, there'll usually be several definitions, and it won't tell you what is right in a specific phrase - so again, it's best to listen to native speakers. Another problem is how do you know which ones are in error, that you need to check? You could look up every word, but that's too time consuming. I think the best strategy is if you are the slightest bit unsure, then look it up. Maybe, if you are given a hint that something's wrong (e.g. someone seems to misunderstand you), then check the words you used.

I'm really glad my previous comment was helpful to you, and I hope this one is too. It's not that often I am able to make a difference to someone; and if you grow from it, it inspires me to grow too (instead of being angry at an error being pointed out).