Don’t frighten new engineers on your team with...
July 20th, 2020
Don’t frighten new engineers on your team with...
Don’t frighten new engineers on your team with code reviews. If you have a high bar to meet, help them get there! It’s one thing for a code submission to have fundamental flaws in how the problem was solved, which indicates you haven’t done your job explaining this problem to your new teammate, but it’s another if the submission has a bunch of style issues. Reality is, though, 20 open issues are 20 open issues — even if they are all minor styling, the new engineer on your team likely won’t fully appreciate that. Make it clear what you are commenting about; if it’s so fundamental that the problem isn’t even addressed, set up a meeting, and talk it through. If it’s just style, tell them!" "" "“Overall, this solution looks great! Just have some minor style things, you’ll get the hang of these in no time :)”" "" "Compassion in your reviews will make your new teammate productive so much faster, which will, in turn, make you and your team more productive." "" "For more snippets like these, check out & follow the hashtag #bendevtip!
Original post on LinkedIn