<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Eric Meadows</title>
    <description>The latest articles on Forem by Eric Meadows (@ericmeadowsdev).</description>
    <link>https://forem.com/ericmeadowsdev</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1019061%2F93d66cbb-5e50-4a22-9462-14a2b750aef9.jpg</url>
      <title>Forem: Eric Meadows</title>
      <link>https://forem.com/ericmeadowsdev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/ericmeadowsdev"/>
    <language>en</language>
    <item>
      <title>Large gap between opening a PR and submitted reviews...</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Wed, 03 May 2023 00:57:33 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/large-gap-between-opening-a-pr-and-submitted-reviews-21fl</link>
      <guid>https://forem.com/ericmeadowsdev/large-gap-between-opening-a-pr-and-submitted-reviews-21fl</guid>
      <description>&lt;p&gt;We've noticed interesting trends...Tuesdays have the most code reviews.  Wednesdays have the most PRs created.  If we are supposed to get code reviewed fast, why is there such a large gap?  (Note that not everyone is opening PRs right when they start work on a new task)&lt;/p&gt;

</description>
      <category>codereviewvillains</category>
      <category>programming</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
    <item>
      <title>What causes more back-and-forths in PRs?</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Wed, 05 Apr 2023 22:25:30 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/what-causes-more-back-and-forths-in-prs-4b1l</link>
      <guid>https://forem.com/ericmeadowsdev/what-causes-more-back-and-forths-in-prs-4b1l</guid>
      <description>&lt;p&gt;Is it:&lt;br&gt;
a) poor syntax/styling&lt;br&gt;
b) too many bugs&lt;br&gt;
c) something else&lt;br&gt;
I'm curious what your views are.&lt;/p&gt;

</description>
      <category>codereviewvillains</category>
      <category>programming</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
    <item>
      <title>LLMs are problematic for knowledge sharing</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Thu, 30 Mar 2023 23:31:54 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/llms-are-problematic-for-knowledge-sharing-3jdl</link>
      <guid>https://forem.com/ericmeadowsdev/llms-are-problematic-for-knowledge-sharing-3jdl</guid>
      <description>&lt;p&gt;If LLMs are probabilistic - do you trust the code output to chance, thoroughly inspect it, or look at it as part of the story?&lt;/p&gt;

&lt;p&gt;Most engineers will thoroughly inspect it due to its probabilistic nature.&lt;/p&gt;

&lt;p&gt;But inspection doesn't yield good knowledge sharing...so now what?&lt;/p&gt;

</description>
      <category>codereviewvillains</category>
      <category>programming</category>
      <category>productivity</category>
      <category>gpt4</category>
    </item>
    <item>
      <title>Making PRs better - first public release!</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Thu, 30 Mar 2023 00:25:12 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/making-prs-better-first-public-release-1ong</link>
      <guid>https://forem.com/ericmeadowsdev/making-prs-better-first-public-release-1ong</guid>
      <description>&lt;p&gt;Yesterday we released the first public version (v0.4.0) of our &lt;strong&gt;FREE Chrome Extension&lt;/strong&gt; (see &lt;a href="https://sourcefield.io"&gt;https://sourcefield.io&lt;/a&gt; or &lt;a href="https://lnkd.in/gf-KesJu"&gt;https://lnkd.in/gf-KesJu&lt;/a&gt;)! We've been testing it internally for a week &amp;amp; are excited!! We have v0.5.0 on-deck to improve code reviews even more! Check it out!&lt;/p&gt;

&lt;p&gt;(&lt;em&gt;We're still early, so there might be some minor bugs&lt;/em&gt;)&lt;/p&gt;

&lt;p&gt;Here are the early “release notes”:&lt;br&gt;
Product Features:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Auto-generated PR Summary&lt;/strong&gt;: Quickly glean what packages were added/removed/up- and down-graded&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Arcs&lt;/strong&gt;: Ordered narratives, composed of PR comments, to guide reviewers through a PR&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Video &amp;amp; Audio Comments&lt;/strong&gt;: Whether you want to spice up your comments with audio or video, or add a video to show off your UI, we embed the video &amp;amp; show you a code-aware transcription.
We will be adding automatic hyperlinking over the next few weeks, so when variables are mentioned, the context is already quickly built for the commenter.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Risk Score&lt;/strong&gt;: Know when a code change is risky - and determine if you or other team members should spend more time reviewing the PR.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Browser Support:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Supported: &lt;strong&gt;Chrome, Edge, Brave, Vivaldi, Opera&lt;/strong&gt;, and &lt;strong&gt;Epic&lt;/strong&gt; (we have not tested SRWare Iron, Comodo Dragon, Torch)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Platform Support:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Supported: &lt;strong&gt;GitHub Cloud&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>codereviewvillains</category>
      <category>productivity</category>
      <category>devops</category>
      <category>codereview</category>
    </item>
    <item>
      <title>What is the purpose of code review? Can LLMs help?</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Tue, 28 Mar 2023 23:46:23 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/what-is-the-purpose-of-code-review-can-llms-help-3c4a</link>
      <guid>https://forem.com/ericmeadowsdev/what-is-the-purpose-of-code-review-can-llms-help-3c4a</guid>
      <description>&lt;p&gt;For years we've been told code reviews are the best place to prevent bugs.  But code inspection doesn't scale.  Given these conflicts - what is the purpose - reducing the bus factor, sharing knowledge, adopting standards, catching bugs, or ___?&lt;/p&gt;

&lt;p&gt;If they're true...can LLMs help?&lt;/p&gt;

</description>
      <category>codereviewvillains</category>
      <category>programming</category>
      <category>productivity</category>
      <category>codereview</category>
    </item>
    <item>
      <title>LGTM - why it's scary</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Tue, 28 Mar 2023 01:17:51 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/lgtm-why-its-scary-4gip</link>
      <guid>https://forem.com/ericmeadowsdev/lgtm-why-its-scary-4gip</guid>
      <description>&lt;p&gt;Why is LGTM scary?  We don't know if the reviewer reviewed it, spent time to understand the code change, know what the code is supposed to do, etc.  As a senior eng, sometimes I wanted to steer the review to be thorough, but inspection doesn't scale...enter GPT.&lt;/p&gt;

</description>
      <category>lgtm</category>
      <category>codereviewvillains</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
    <item>
      <title>LGTM = Scary</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Thu, 23 Mar 2023 00:00:48 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/lgtm-scary-4l3h</link>
      <guid>https://forem.com/ericmeadowsdev/lgtm-scary-4l3h</guid>
      <description>&lt;p&gt;LGTM - the scariest words to see as a CTO.  That means devs didn't spend enough time on a PR.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>codereviewvillains</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Stacked PRs are bad!</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Wed, 22 Mar 2023 00:42:17 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/stacked-prs-are-bad-1bmi</link>
      <guid>https://forem.com/ericmeadowsdev/stacked-prs-are-bad-1bmi</guid>
      <description>&lt;p&gt;Stacked PRs - they look like fun, but they're terrible.  They unblock the author but they make code reviews a nightmare.  They're a code review villain in disguise!&lt;/p&gt;

</description>
      <category>programming</category>
      <category>productivity</category>
      <category>codereview</category>
      <category>codereviewvillains</category>
    </item>
    <item>
      <title>Context in PRs is not being solved</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Tue, 21 Mar 2023 01:39:10 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/context-in-prs-is-not-being-solved-23j2</link>
      <guid>https://forem.com/ericmeadowsdev/context-in-prs-is-not-being-solved-23j2</guid>
      <description>&lt;p&gt;Bottlenecks in PRs are everywhere - but the core issue is lacking context.  Devs &amp;amp; managers don't know how close a PR is to shipping.  Reviewers don't know if major changes are coming or how the author got to the final code. They also lack a product that shows them the key data to review w/o jumping around.  No tools fix this, and the latest start-ups aren't working on the core problem.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>codereviewvillains</category>
      <category>productivity</category>
      <category>devtools</category>
    </item>
    <item>
      <title>Is AI bad for code reviews?</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Sat, 18 Mar 2023 01:02:42 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/is-ai-bad-for-code-reviews-227</link>
      <guid>https://forem.com/ericmeadowsdev/is-ai-bad-for-code-reviews-227</guid>
      <description>&lt;p&gt;If a code review was done by AI, what would you lose out on?  If an AI told you, before you request a review, that it's going to be rejected because of reasons XYZ, would that be better?&lt;/p&gt;

</description>
      <category>codereviewvillains</category>
      <category>programming</category>
      <category>productivity</category>
      <category>devops</category>
    </item>
    <item>
      <title>"How is the review coming along"...would this be useful?</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Fri, 17 Mar 2023 00:30:56 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/how-is-the-review-coming-alongwould-this-be-useful-fe7</link>
      <guid>https://forem.com/ericmeadowsdev/how-is-the-review-coming-alongwould-this-be-useful-fe7</guid>
      <description>&lt;p&gt;As a dev, I write a bunch of code.  I just want to get a PR merged.  I am often frustrated to know if a dev is even looking at my PR, how close they are to wrapping it up, etc.&lt;/p&gt;

&lt;p&gt;Would knowing this make you happier or more frustrated?&lt;br&gt;
👍 = yes&lt;br&gt;
👎 = no&lt;/p&gt;

&lt;p&gt;React to get your voice heard!!&lt;/p&gt;

</description>
      <category>codereviewvillains</category>
      <category>programming</category>
      <category>productivity</category>
      <category>codereview</category>
    </item>
    <item>
      <title>Quicker PRs means you can do _____</title>
      <dc:creator>Eric Meadows</dc:creator>
      <pubDate>Wed, 15 Mar 2023 00:21:59 +0000</pubDate>
      <link>https://forem.com/ericmeadowsdev/quicker-prs-means-you-can-do--2m2a</link>
      <guid>https://forem.com/ericmeadowsdev/quicker-prs-means-you-can-do--2m2a</guid>
      <description>&lt;p&gt;Code reviews take up 20% of a good dev's time.&lt;/p&gt;

&lt;p&gt;If you could accomplish the same goals, while drastically reducing the time...what would you do?&lt;/p&gt;

</description>
      <category>codereviewvillains</category>
      <category>programming</category>
      <category>productivity</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
