In "What theory are self taught devs usually missing?"I answer a programming question. A podcast version of the channel can be found here: anchor.fm/fred...
I have a question, what's your advice for approaching code reviews as a junior dev commenting on code written by another junior. I feel like I'm getting a lot of passive aggressive backtalk whenever I point out an obvious conceptual mistake or things that break best practices, leaving links to related articles. In fact, the seniors in my company are incredibly receptive to my reviews. I know I can get tickets done twice as fast as most of the other juniors and I get the feeling that this causes some form of intimidation. Regardless, code reviews are part of the job but I also want to maintain these relationships. Help? 😢
I have a question, what's your advice for approaching code reviews as a junior dev commenting on code written by another junior. I feel like I'm getting a lot of passive aggressive backtalk whenever I point out an obvious conceptual mistake or things that break best practices, leaving links to related articles. In fact, the seniors in my company are incredibly receptive to my reviews. I know I can get tickets done twice as fast as most of the other juniors and I get the feeling that this causes some form of intimidation. Regardless, code reviews are part of the job but I also want to maintain these relationships. Help? 😢
quick title correction: should be "are" not "do"