When someone corrects your code

In that spirit, I will call attention to your first sentence, specifically the comma. In my opinion, that can be improved. One of three other constructions would be more appropriate:

• I am really happy when people are quite strict in code reviews. It makes me feel safer and I get to learn more.
• I am really happy when people are quite strict in code reviews, because it makes me feel safer and I get to learn more.
• I am really happy when people are quite strict in code reviews; it makes me feel safer and I get to learn more.

The first of my suggested changes is favoured by those who follow the school of thought that argues that written sentences should be kept short and uncomplicated to make processing easier for those less fluent. To me, it sounds choppy or that you've omitted someone asking "Why?" after the first sentence.

Personally, I prefer the middle one, because it is the full expression of a complete state of mind. You have a feeling and a reason for that feeling. There is a sense in which they are inseparable, so not splitting them up seems like a good idea. The "because" explicitly links the feeling and reason.

The semicolon construction was favoured by my grade school teachers in the 1960s, but, as with the first suggestion, it just feels choppy. I tend to overuse semicolons, so I try to go back and either replace them with periods or restructure the sentences to eliminate them. In this particular case, I think the semicolon is preferable to both comma and period, but still inferior to the "because" construction.

I've clearly spent too much time hashing stuff out in writers' groups. :)

Like the other guy, I also read your comment twice looking for mistakes but found none.
You should of left something to fix!
😏

Edit: I'm glad there so many people who are as passionate about the correct spelling of "should've" as I am. I was testing you all, and you passed!

Notably, a good code review should also bring up the good parts of the submission, and not just concentrate on the errors. Not only does it make the recipient feel better to get positive feedback among the negative, but it helps them learn about good practices too. Just concentrating on the errors doesn't really tell them which things they're doing well.

Many reviewers concentrate on just finding mistakes, and while it's useful it's sort of the bare minimum; a good code review should be educational. Especially if the submitter's a more junior coder, in which case it'd also be a good idea to not just outright tell them how you'd fix some problem, but sort of lead them to a solution by asking them questions and pointing things out and letting them do the thinking themselves. But still, experienced coders will also benefit from well-structured feedback, it's not like we're "finished" and stopped learning.

Yeah, I learn so much from code reviews and they've saved me so much time from dumb mistakes I missed. I've also caught no shortage of bugs in other people's code that saved us all a stressful headache. It's just vastly easier to fix a bug before it merges than once it breaks a bunch of people.

I'm juggling 3 languages

We Americans like to forget that anyone might have any trouble understanding English especially in cases of polyglots.

I don't know which is your native tongue but from this comment it looks like you're doing a fine job.

Assuming you have competent leadership, then it wouldn't be merged if you missed something obvious. I guess you're saying that you want more positive reinforcement.

Me omw to tell the POSiX guys it's supposed to be "O_CREATE" instead of "O_CREAT":

What if your grammar is that bad that people struggle to understand you?

I know someone who is incomprehensible most of the time. I have to ask probing questions just to vaguely understand what they're trying to communicate. I've politely told them more than once about the issue but they never try; they're not mentally challenged or anything, just an ass.

English changes very quickly. New words come out every year. Some programming languages takes years for updates.

fr fr no cap

It’s actually “their’yre” dumby, learn ur words

SOme morans should of staid inn School!!

No, you're grammerer

Oh boy

However, real grammar and prescribed textbook grammar are two different things.

Brother you don't even remember what it does, how and why after 3 days