<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kendra Curtis on Medium]]></title>
        <description><![CDATA[Stories by Kendra Curtis on Medium]]></description>
        <link>https://medium.com/@kscurtis2000?source=rss-9eead4795863------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mycV0zQsCltC25uqo9iCtA.jpeg</url>
            <title>Stories by Kendra Curtis on Medium</title>
            <link>https://medium.com/@kscurtis2000?source=rss-9eead4795863------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:08:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kscurtis2000/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Top Book Recommendations for Engineers and Engineering Managers]]></title>
            <link>https://kscurtis2000.medium.com/top-book-recommendations-for-engineers-and-engineering-managers-1b612364e159?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b612364e159</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[book-recommendations]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Thu, 30 Nov 2023 12:01:48 GMT</pubDate>
            <atom:updated>2023-11-30T12:01:48.084Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wm4r-Vdm97PNDHjV9eMVhQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@syinq?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Susan Q Yin</a> on <a href="https://unsplash.com/photos/books-on-brown-wooden-shelf-2JIvboGLeho?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>December is often a time for <strong>reflection on the past year</strong>. Professional development books can provide insights, lessons, and strategies to help you evaluate your achievements and areas for growth. They can help you <strong>set career goals for the upcoming year </strong>or <strong>prepare for career changes. </strong>Given that here is the books I recommend:</p><h4>General</h4><ul><li><a href="https://www.amazon.com/gp/search?ie=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=81e1fc47b2b8a7d8b241001a97ae5232&amp;camp=1789&amp;creative=9325&amp;index=books&amp;keywords=Mythical%20Man%20Month">Mythical Man-Month by Fred Brooks</a></li><li><a href="https://www.amazon.com/Crucial-Conversations-Third-Talking-Stakes/dp/B09MV3818X/ref=sr_1_1?crid=1DV9Y8NAE75CK&amp;keywords=crucial+conversations&amp;qid=1701223773&amp;sprefix=crutial+converstaions%252Caps%252C152&amp;sr=8-1&amp;_encoding=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=6099b93cb09600b05af24352d38bb8ba&amp;camp=1789&amp;creative=9325">Crucial Conversations</a></li><li><a href="https://www.amazon.com/gp/search?ie=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=69532e749bc833e9e6fff5b9755033ff&amp;camp=1789&amp;creative=9325&amp;index=books&amp;keywords=HBR%2010%20must%20reads">HBR 10 must reads on various topics</a> — These can be very beneficial if you start a professional reading group. Each book contains 10 standalone articles, making them quicker to read and increasing engagement within the group.</li><li><a href="https://www.amazon.com/Find-Your-Why-audiobook/dp/B074F33DYD/ref=sr_1_1?crid=22CEL9TPGGS8N&amp;keywords=Find+Your+Why+by+David+Mead%252C+Peter+Docker%252C+and+Simon+Sinek&amp;qid=1701224265&amp;s=books&amp;sprefix=find+your+why+by+david+mead%252C+peter+docker%252C+and+simon+sinek%252Cstripbooks%252C138&amp;sr=1-1&amp;_encoding=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=2c4eb9666b06af72325069f52ef42aea&amp;camp=1789&amp;creative=9325">Find Your Why by David Mead, Peter Docker, and Simon Sinek</a></li></ul><h4>Project Management</h4><ul><li><a href="https://www.amazon.com/gp/search?ie=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=80f8bda6d90d78f34129a873f1f33921&amp;camp=1789&amp;creative=9325&amp;index=books&amp;keywords=Slack%20by%20Tom%20DeMarco">Slack by Tom DeMarco</a></li></ul><h4>Negotiation</h4><ul><li><a href="https://www.amazon.com/gp/search?ie=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=f73af91024af692909c7fcc6493b7914&amp;camp=1789&amp;creative=9325&amp;index=books&amp;keywords=Getting%20More%20by%20Stuart%20Diamond">Getting More by Stuart Diamond</a></li><li><a href="https://www.amazon.com/gp/search?ie=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=58d6a7a6915a0b9ae9fcd04d3d8e43a5&amp;camp=1789&amp;creative=9325&amp;index=books&amp;keywords=Getting%20to%20Yes%20by%20Roger%20Fisher%20and%20William%20Ury">Getting to Yes by Roger Fisher and William Ury</a></li></ul><h4>Management</h4><ul><li><a href="https://www.amazon.com/gp/search?ie=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=30006ee0047391cf2a23df95e9e7b8f5&amp;camp=1789&amp;creative=9325&amp;index=books&amp;keywords=Peopleware%20by%20Timothy%20Lister%20and%20Tom%20DeMarco">Peopleware by Timothy Lister and Tom DeMarco</a></li><li><a href="https://www.amazon.com/gp/search?ie=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=511ccee34fc94d990137f798e3e92fbc&amp;camp=1789&amp;creative=9325&amp;index=books&amp;keywords=Managing%20Humans%20by%20Michael%20Loop">Managing Humans by Michael Loop</a></li><li><a href="https://www.amazon.com/gp/search?ie=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=f39e3638caab5fac3649817f5bf9a7d2&amp;camp=1789&amp;creative=9325&amp;index=books&amp;keywords=Conscious%20Accountability%20Deepen%20Connections%20Elevate%20Results">Conscious Accountability: Deepen Connections, Elevate Results by David C. Tate, Marianne S. Pantalon, et al</a> — Don’t skip the introduction; you may find a reference to someone familiar.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b612364e159" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Steps to Improving Your Time Management]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://kscurtis2000.medium.com/3-steps-to-improving-your-time-management-1bb54545cc79?source=rss-9eead4795863------2"><img src="https://cdn-images-1.medium.com/max/2600/1*jyG0_poA7UtBWUdNxa67hw.jpeg" width="4592"></a></p><p class="medium-feed-snippet">For many of us, productivity is often equated with spending more time working. However, there are techniques that can help you organize&#x2026;</p><p class="medium-feed-link"><a href="https://kscurtis2000.medium.com/3-steps-to-improving-your-time-management-1bb54545cc79?source=rss-9eead4795863------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://kscurtis2000.medium.com/3-steps-to-improving-your-time-management-1bb54545cc79?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bb54545cc79</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Thu, 16 Nov 2023 21:59:35 GMT</pubDate>
            <atom:updated>2023-11-28T15:33:00.529Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to Weather the Storm of Tech Layoffs by Managing to Scale]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/geekculture/how-to-weather-the-storm-of-tech-layoffs-by-managing-to-scale-85f8a89e04f0?source=rss-9eead4795863------2"><img src="https://cdn-images-1.medium.com/max/2600/0*UgmN9lGt3rHERkqp" width="6720"></a></p><p class="medium-feed-snippet">Your company has had layoffs and you are still there&#x2026; Now what?</p><p class="medium-feed-link"><a href="https://medium.com/geekculture/how-to-weather-the-storm-of-tech-layoffs-by-managing-to-scale-85f8a89e04f0?source=rss-9eead4795863------2">Continue reading on Geek Culture »</a></p></div>]]></description>
            <link>https://medium.com/geekculture/how-to-weather-the-storm-of-tech-layoffs-by-managing-to-scale-85f8a89e04f0?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/85f8a89e04f0</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[layoffs]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Wed, 15 Feb 2023 12:32:37 GMT</pubDate>
            <atom:updated>2023-02-24T09:16:25.044Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Are you using Coding Interviews for Senior Software Developers?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/geekculture/are-you-using-coding-interviews-for-senior-software-developers-6bae09ed288c?source=rss-9eead4795863------2"><img src="https://cdn-images-1.medium.com/max/2600/1*denFVkmsgWRgQ_aLlktQeg.jpeg" width="5426"></a></p><p class="medium-feed-snippet">Please Don&#x2019;t&#x2026; What you should be doing instead.</p><p class="medium-feed-link"><a href="https://medium.com/geekculture/are-you-using-coding-interviews-for-senior-software-developers-6bae09ed288c?source=rss-9eead4795863------2">Continue reading on Geek Culture »</a></p></div>]]></description>
            <link>https://medium.com/geekculture/are-you-using-coding-interviews-for-senior-software-developers-6bae09ed288c?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bae09ed288c</guid>
            <category><![CDATA[interviewing]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[interview-questions]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Sat, 02 Apr 2022 15:02:48 GMT</pubDate>
            <atom:updated>2022-04-02T15:02:48.102Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Imposter Syndrome: How to overcome it during Code Reviews]]></title>
            <link>https://kscurtis2000.medium.com/imposter-syndrome-how-to-overcome-it-during-code-reviews-3eb23beae383?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/3eb23beae383</guid>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[code-review]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 16:37:59 GMT</pubDate>
            <atom:updated>2023-12-13T21:58:28.202Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/795/1*fJnYWyT6BRNRxp6JkaMJuQ.jpeg" /></figure><p>The articles in this series <a href="http://kendracurtis.com/ghc2020">about being an effective code reviewer </a>have be leading to this final article on imposter syndrome. Sending your code for review or reviewing the code of a colleague can be intimidating and stress inducing. Often you feel as though, I am not qualified to do this?! In particular, when team members haven’t been working together for a long time and a senior developer asks you to review their code…. Who am I to give them advice? I’m not good enough to do this Code Review.</p><p><strong>Stop right there, you are good enough!! </strong>In fact you may be the perfect person to do this review, specifically because you have different experience than the author of the code. The feeling you are having is imposter syndrome. Everyone experiences it and it is normal. Twenty years into my career, I still experience this.</p><h4>What is imposter syndrome?</h4><blockquote><em>Impostor syndrome (also known as impostor phenomenon, impostorism, fraud syndrome or the impostor experience) is a psychological pattern in which one doubts one’s accomplishments and has a persistent internalized fear of being exposed as a “fraud”.- </em><a href="https://en.wikipedia.org/wiki/Impostor_syndrome">wikipedia</a></blockquote><p>It is important to recognize imposter syndrome and ensure you have a culture and leadership that provides the tools to overcome it. <strong>Psychological safety has been shown to be a #1 key factor to a successful team</strong>. When team members feel safe to take risks and are not scared of embarrassment during collaboration and exchange, ideas can quickly flourish.</p><p>Therefore, it is critical to build a culture where people feel safe to ask questions, share what they do not know, and share ideas when they disagree.</p><p>Some common problems:</p><ul><li>I do not understand the code and I am afraid to ask for clarification</li><li>I am less senior and do not want to disagree with more senior people</li></ul><p>Here are some tips to overcome imposter syndrome and contribute to the team:</p><ol><li><strong>Imposter syndrome never goes away!!</strong> Developers with years of experience still experience it. There is always more to learn</li><li><strong>Everyone has something to add</strong> to a code review regardless of their experience. A fresh second set of eyes always has something to offer regardless of your level of experience.</li><li><strong>Look at this as a way to learn as well as review</strong>.</li><li><strong>Establish a specialty.</strong> i.e. I am the “go-to” person for _____ type of code reviews or _____ area of the code. It is also good to align this with your career goals.</li><li>Look at the <strong>review until you find a way to improve the code</strong> or find an edge case.</li><li><strong>Compliment</strong> the person who wrote the code when it teaches you something. This will help create a relationship and may break barriers for the next time.</li><li><strong>Pair with someone</strong> who you know does great code reviews so you can learn their technique.</li></ol><p>In addition, code reviews are an opportunity to encourage healthy communication on the team. There are many, many, many concrete tips on communicating in a constructive way which feels inclusive and where people do not feel judged. Here are a few tips for authors and reviewers of a code review:</p><ul><li><strong>Assume good faith and competence</strong></li><li><strong>Avoid selective ownership of code</strong>. <em>(“mine”, “not mine”, “yours</em>”) The review is of the code, not the author. Favor the use of “we”. Instead of “<em>you should use a constant here</em>“, frame it as “<em>Here it seems we need a constant because this value</em>”</li><li><strong>Asking questions</strong> instead of making demands. Instead of “r<em>ename to user_id</em>”, use “<em>what do you think of naming this user_id</em>?</li><li><strong>Be humble and assume the best of the author</strong>. Instead of “<em>Why didn’t you use X here?</em>”, use “<em>Have you considered using X ? because …</em>”.</li><li><strong>A comment can simply be a question asking for clarification</strong>. “<em>I am not sure why this has an impact on latency, could you add more details?</em>” It is important to make it specific and not be too general.</li><li><strong>Positive Reinforcement</strong>: it is important for both authors and reviewers to thank each other. Small notes such as “<em>Good catch, thanks. Fixed” </em>or<em> “Thanks for the rework, this looks really good.”</em></li></ul><p>Finally, if you are a team lead, it is crucial to reward good reviewers and acknowledge their contributions. Do not forget to use this criteria when evaluating people. You can also reinforce it in your 1:1 or team meetings when some work really benefited from a code review. A good code review can <strong>catch a bug early and/or prevented lots of technical debt</strong>.</p><p>For further reading on Imposter Syndrome check out <a href="https://www.amazon.com/Yes-You-Good-Enough-Perfectionism/dp/1732865523?&amp;_encoding=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=5ee9a4126039a699f1e3b2767f280f91&amp;camp=1789&amp;creative=9325">Yes! You are good enough by Trish Taylor</a></p><p>This article is a series on how to be an effective code reviewer. Please see my previous article that provides background on <a href="https://medium.com/@kscurtis2000/what-is-a-code-review-74f080c33013">Code Reviews and Their Benefits</a>. Other articles in the series are:</p><p><a href="https://medium.com/@kscurtis2000/4-rules-of-thumb-for-providing-effective-code-review-feedback-bb188864f50d">4 Rules of Thumb for Providing Effective Code Review Feedback</a></p><p><a href="https://medium.com/@kscurtis2000/how-to-provide-effective-feedback-based-on-code-review-type-ccace3d60092">How to Provide Effective Feedback based on Code Review Type</a></p><p><a href="https://medium.com/@kscurtis2000/inclusive-and-productive-collaboration-in-code-reviews-e7d05c228f4d">Inclusive and Productive Collaboration in Code Reviews</a></p><p>Thank you to<a href="https://www.linkedin.com/in/bonhommebiais"> Alice Bonhomme-Biais</a>, co-author of this article. We originally presented the content at Grace Hopper 2020 as a part of a presentation on “<a href="http://kendracurtis.com/ghc2020">Finding your Voice as a Code Reviewer</a>”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3eb23beae383" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inclusive and Productive Collaboration in Code Reviews]]></title>
            <link>https://kscurtis2000.medium.com/inclusive-and-productive-collaboration-in-code-reviews-e7d05c228f4d?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7d05c228f4d</guid>
            <category><![CDATA[diversity-and-inclusion]]></category>
            <category><![CDATA[grace-hopper-conference]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 05:43:15 GMT</pubDate>
            <atom:updated>2023-12-13T22:15:04.588Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDgZncNXFROvwfVqFIZdbQ.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/@fauxels?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">fauxels</a> from <a href="https://www.pexels.com/photo/group-of-people-standing-indoors-3184396/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels">Pexels</a></figcaption></figure><p>Code reviews can often be a source of stress and frustration and they should not be. From my original article that<a href="https://medium.com/@kscurtis2000/what-is-a-code-review-74f080c33013"> defined code review and their benefits</a>:</p><p><strong>#1 rule: This is about sharing knowledge and improving, not to catch someone out or shame them.</strong></p><p>Code reviews are one of the key spaces where you can foster an inclusive and collaborative culture in Software development. In general, code reviews should always be about the code and not the developer, so <strong>avoid using using you, your, etc</strong>. A key to a successful code review is to keep it short and effective. A way to achieve this goal is to make your comments clear and actionable:</p><ul><li><strong>Be kind: </strong>Compliment the person who wrote the code when it teaches you something. This will help create a relationship and may break barriers for the next time. Also, remember the context and background of the person asking for the review. Is the developer a new grad and this is the first time they have ever experienced a peer review? Is there a power dynamic between the 2 of you (i.e. are you much more experienced an/or influential in the company)?</li><li><strong>Explain your reasoning</strong>: when recommending a change and suggesting another approach, explain why, so the author can understand the motivation. Instead of “<em>add @override</em>” explain “<em>here it seems we need to add @override otherwise the method is simply overloading. See this reference on overload/override</em>”</li><li><strong>Provide suggestions</strong>: avoid simply stating “<em>this method is too long</em>” but take a few minutes and write an idea to help the person get started “<em>This methods seems to be over the limit of our standard, maybe we can extract this logic into a submethod</em>”</li><li>If you cannot understand the code, <strong>ask specific questions</strong>. Encourage developers to simplify code or add code comments instead of just explaining the complexity to you. Instead of “<em>this is very confusing, please clarify</em>”, explain “<em>I do not understand what are the parameters of the method and why we need this processing on it. Can you add more comments to provide context?</em>”</li><li><strong>Specify the importance of your comment</strong>: for example prefix “nit:” (short for nitpick) for small style recommendations</li></ul><p>Finally, if there are too many comments or back and forth on a review, stop and meet in person or Video Call to discuss the issue. This may be a case where there is a need to go back to design by creating or enhancing a design document summarizing the approach taken in the code review.</p><p>It is worth stating again:</p><p><strong>Compliment the person who wrote the code when it teaches you something.</strong></p><p>Code reviews are not just about finding mistakes, but also about learning. Also, the sooner you find a potential issue the less impact it will have, so don’t neglect using a critical eye. <strong>We all have a different journey and as a result have a different perspective, which is invaluable to the review process</strong>. If you show a piece of code to 10 developers, they will have 10 different things say.</p><p>Some addition reading on Diversity and Inclusion:</p><ul><li><a href="https://www.amazon.com/Brotopia-Breaking-Boys-Silicon-Valley/dp/0735213534?&amp;_encoding=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=d49af6d817ac52078c15b195b4c9ec3d&amp;camp=1789&amp;creative=9325">Brotopia: Breaking Up the Boys’ Club of Silicon Valley by Emily Chang</a></li><li><a href="https://www.amazon.com/Inclusion-Diversity-Workplace-Will-Change/dp/1946384100?&amp;_encoding=UTF8&amp;tag=engcoach-20&amp;linkCode=ur2&amp;linkId=9b014a90801886a3670fe335ec3491d4&amp;camp=1789&amp;creative=9325">Inclusion: Diversity, The New Workplace &amp; The Will To Change by Jennifer Brown</a></li></ul><p>This article is a series on how to be an effective code reviewer. Please see my previous article that provides background on <a href="https://medium.com/@kscurtis2000/what-is-a-code-review-74f080c33013">Code Reviews and Their Benefits</a>. Other articles in the series are:</p><p><a href="https://medium.com/@kscurtis2000/4-rules-of-thumb-for-providing-effective-code-review-feedback-bb188864f50d">4 Rules of Thumb for Providing Effective Code Review Feedback</a></p><p><a href="https://medium.com/@kscurtis2000/how-to-provide-effective-feedback-based-on-code-review-type-ccace3d60092">How to Provide Effective Feedback based on Code Review Type</a></p><p><a href="https://medium.com/@kscurtis2000/imposter-syndrome-how-to-overcome-it-during-code-reviews-3eb23beae383">Imposter Syndrome: How to overcome it during Code Reviews</a></p><p>Thank you to<a href="https://www.linkedin.com/in/bonhommebiais"> Alice Bonhomme-Biais</a>, co-author of this article. We originally presented the content at Grace Hopper 2020 as a part of a presentation on “<a href="http://kendracurtis.com/ghc2020">Finding your Voice as a Code Reviewer</a>”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7d05c228f4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Provide Effective Feedback based on Code Review Type]]></title>
            <link>https://kscurtis2000.medium.com/how-to-provide-effective-feedback-based-on-code-review-type-ccace3d60092?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccace3d60092</guid>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[grace-hopper-conference]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 05:00:27 GMT</pubDate>
            <atom:updated>2020-10-01T16:44:17.155Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ArhOEo6YjoO-pgOZu71HYQ.jpeg" /><figcaption>Photo by <a href="https://picjumbo.com/author/viktorhanacek/">Viktor Hanacek</a></figcaption></figure><h3>Type of code reviews</h3><p>There are several types of code reviews and you may want to adjust your style depending on the type of review you are undertaking:</p><ul><li>Features</li><li>Bug fixes</li><li>Other: script to automate a recurring task, github template, …</li></ul><h4>Features</h4><p>Features are more likely to come to you in a series of code reviews. A good practice for the person requesting the review is to include you in the design of the feature (i.e. asking for advice, reviewing, co-authoring a design doc) The level of prior involvement will depend on the size of the feature.</p><p>As you are reviewing the feature you should ask the following design questions:</p><ul><li>Do the interactions of various pieces of code make sense?</li><li>Does this change belong in this codebase, or in a library?</li><li>Does it integrate well with the rest of the system?</li></ul><p><strong>Discuss and iterate on overall design before discussing details in the code.</strong> Then review the functionality of the piece of code.</p><p>Once the code is out for review it is reasonable to expect that it works correctly. The reviewer brings a fresh perspective:</p><ul><li>What are the edge cases?</li><li>How could a user break this code?</li><li>Is there a potential for concurrency problems?</li><li>Is there prior knowledge or art that I know about this portion of the code base?</li><li>Is this code “too complex”? Can I understand the code quickly or are there ways it can be simplified for the future.</li></ul><h4>Bugs</h4><p>Bugs fixes tend to be much smaller and more focused. They may also be on a timeline. This is where the reviewer’s prior knowledge of the code may be the most useful way they can contribute. It may also be useful to try to break the code, to ensure it really fixes the issue and does not introduce another bug.</p><p>As a reviewer you should stay focused on the goal of the review and table discussion of deeper changes, or style changes for future. If needed, open another issue to track other changes rather than delaying a bug fix.</p><h4>Other</h4><p>This is the case where you may want to give a LGTM (looks good to me) upfront, depending on the purpose of the review. For example, if it is a new issue template, you may want to point out spelling mistakes, items you may find useful and give them approval, so they don’t need a second round of communication with you.</p><p>The goal of all of these types of reviews is to improve the overall code health and share knowledge. Reviewers can also learn by reviewing the code others have written.</p><p>Remember it doesn’t have to be perfect and you can use a TODO or similar to iterate in another review or capture an idea for the future.</p><p>This article is a series on how to be an effective code reviewer. Please see my previous article that provides background on <a href="https://medium.com/@kscurtis2000/what-is-a-code-review-74f080c33013">Code Reviews and Their Benefits</a>. The other articles in the series are:</p><p><a href="https://medium.com/@kscurtis2000/4-rules-of-thumb-for-providing-effective-code-review-feedback-bb188864f50d">4 Rules of Thumb for Providing Effective Code Review Feedback</a></p><p><a href="https://medium.com/@kscurtis2000/inclusive-and-productive-collaboration-in-code-reviews-e7d05c228f4d">Inclusive and Productive Collaboration in Code Reviews</a></p><p><a href="https://medium.com/@kscurtis2000/imposter-syndrome-how-to-overcome-it-during-code-reviews-3eb23beae383">Imposter Syndrome: How to overcome it during Code Reviews</a></p><p>Thank you to<a href="https://www.linkedin.com/in/bonhommebiais"> Alice Bonhomme-Biais</a>, co-author of this article. We originally presented the content at Grace Hopper 2020 as a part of a presentation on “<a href="http://kendracurtis.com/ghc2020">Finding your Voice as a Code Reviewer</a>”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccace3d60092" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Rules of Thumb for Providing Effective Code Review Feedback]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/4-rules-of-thumb-for-providing-effective-code-review-feedback-bb188864f50d?source=rss-9eead4795863------2"><img src="https://cdn-images-1.medium.com/max/1020/0*ULAgRYoIBzvd8Qwx" width="1020"></a></p><p class="medium-feed-snippet">The above is the worst case scenario for a code review. Each of the developers thinks the other will look at the code closely. This&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/swlh/4-rules-of-thumb-for-providing-effective-code-review-feedback-bb188864f50d?source=rss-9eead4795863------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/4-rules-of-thumb-for-providing-effective-code-review-feedback-bb188864f50d?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb188864f50d</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[grace-hopper-conference]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Thu, 01 Oct 2020 04:26:44 GMT</pubDate>
            <atom:updated>2020-10-03T07:10:19.617Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What is a code review?]]></title>
            <link>https://kscurtis2000.medium.com/what-is-a-code-review-74f080c33013?source=rss-9eead4795863------2</link>
            <guid isPermaLink="false">https://medium.com/p/74f080c33013</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[grace-hopper-conference]]></category>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Kendra Curtis]]></dc:creator>
            <pubDate>Mon, 28 Sep 2020 03:29:13 GMT</pubDate>
            <atom:updated>2021-01-10T04:17:04.894Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is a code review? and Why should they be a part of your process?</h3><p>A code review is a standard practice in the software development life cycle, where one or more people review the source code of another developer. The goal of the review can vary, but it is generally to increase the code quality and provide consistency to a code base.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJCod5hg9CUKmVwqJYTVeg.jpeg" /><figcaption>Photo by <a href="https://picjumbo.com/author/viktorhanacek/">Viktor Hanacek</a></figcaption></figure><p>It is something I find many people have the hardest time adapting to when moving into industry and as developers moving through their careers. As an Engineering Manager, this is an area I find there is a very high probability of coaching employees. It is not uncommon for someone who is new to the process to submit their first review and have a large amount of feedback for various reasons.</p><p><strong>#1 rule: This is about sharing knowledge and improving, not to catch someone out or shame them.</strong></p><p>When I started writing code professionally, there were no tools to facilitate the process. We would literally call a meeting for any large or important pieces of code we were adding to the code base. All of the participants would manually review the code and give their feedback. Depending on the nature of the code, feedback could be given 1-on-1 or in a larger group where we would discuss the effect of the code on the code base.</p><p>Nowadays, we have built-in support for code reviews. They are often referred to as <a href="https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/about-pull-requests">Pull Requests (PRs)</a> and/or <a href="https://www.perforce.com/perforce/doc.051/manuals/p4guide/07_changelists.html">Change Lists (CLs)</a>, where the submission of the code is more than likely gated by a review.</p><h3><strong>Benefits of code reviews</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5j4cNs3bScwX83DUuIOIKg.png" /></figure><p>Back in 2006, Jeff Atwood, co-founder of stack-overflow, wrote in his <a href="https://blog.codinghorror.com/">“coding horror” blog</a> that “<em>peer code reviews are the single biggest thing you can do to improve your code</em>”. Since then, code reviews are now commonly used in most tech companies to help achieve the following goals:</p><ul><li><strong>Better code quality</strong>: makes the code more readable and maintainable</li><li><strong>Finding defects early</strong>: when a bug is found early, it is cheaper to fix.</li><li><strong>Learning/Knowledge transfer</strong>: team members gain better understanding of the code base and learn from each other.</li><li>Increase sense of collective code <strong>ownership and solidarity</strong>:</li><li>Finding<strong> better solutions</strong>: discussions can generate innovative ideas while maintaining a level of consistency in software design and implementation.</li><li>Complying to <strong>QA guidelines and coding standards</strong></li></ul><p>This article provides the background for a series of articles on Code Review best practices. The goal of the following articles will be to:</p><ul><li>provide concrete guidelines and tips on how you can contribute as a code reviewer</li><li>ensure all these benefits are generated for yourself, your team and your product.</li></ul><p>This article is a series on how to be an effective code reviewer, the other articles in the series are:</p><p><a href="https://medium.com/@kscurtis2000/4-rules-of-thumb-for-providing-effective-code-review-feedback-bb188864f50d">4 Rules of Thumb for Providing Effective Code Review Feedback</a></p><p><a href="https://medium.com/@kscurtis2000/how-to-provide-effective-feedback-based-on-code-review-type-ccace3d60092">How to Provide Effective Feedback based on Code Review Type</a></p><p><a href="https://medium.com/@kscurtis2000/inclusive-and-productive-collaboration-in-code-reviews-e7d05c228f4d">Inclusive and Productive Collaboration in Code Reviews</a></p><p><a href="https://medium.com/@kscurtis2000/imposter-syndrome-how-to-overcome-it-during-code-reviews-3eb23beae383">Imposter Syndrome: How to overcome it during Code Reviews</a></p><p>Thank you to<a href="https://www.linkedin.com/in/bonhommebiais"> Alice Bonhomme-Biais</a>, co-author of this article. We originally presented the content at Grace Hopper 2020 as a part of a presentation on “<a href="http://kendracurtis.com/ghc2020">Finding your Voice as a Code Reviewer</a>”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74f080c33013" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>