<?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>DEV Community: Andrey Lebedev</title>
    <description>The latest articles on DEV Community by Andrey Lebedev (@andrey_lebedev_db59283b0e).</description>
    <link>https://dev.to/andrey_lebedev_db59283b0e</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%2F3717896%2Ff27cfa6d-d29e-4fb9-bb82-51265c7fdd12.png</url>
      <title>DEV Community: Andrey Lebedev</title>
      <link>https://dev.to/andrey_lebedev_db59283b0e</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/andrey_lebedev_db59283b0e"/>
    <language>en</language>
    <item>
      <title>The Art of Code Review Corruption: 10 Ways to Always Get Your PRs Merged</title>
      <dc:creator>Andrey Lebedev</dc:creator>
      <pubDate>Mon, 19 Jan 2026 08:51:04 +0000</pubDate>
      <link>https://dev.to/andrey_lebedev_db59283b0e/the-art-of-code-review-corruption-10-ways-to-always-get-your-prs-merged-3844</link>
      <guid>https://dev.to/andrey_lebedev_db59283b0e/the-art-of-code-review-corruption-10-ways-to-always-get-your-prs-merged-3844</guid>
      <description>&lt;p&gt;Lately, I’ve seen many posts about cultivating a good PR review culture and sharing best practices. I’d like to take a different approach and present the same topic with a touch of sarcasm. Introducing: &lt;a href="https://www.linkedin.com/posts/andremoniy_the-art-of-code-review-corruption-activity-7241809735979610112-lFCq" rel="noopener noreferrer"&gt;"The Art of Code Review Corruption: 10 Ways to Always Get Your PRs Merged.&lt;/a&gt;" &lt;br&gt;
What do you think? Do any of these patterns sound familiar in your daily work?&lt;/p&gt;

</description>
      <category>jokes</category>
      <category>programming</category>
      <category>codereview</category>
      <category>agile</category>
    </item>
    <item>
      <title>Slicing your work with BDD or another aspect of speed increase with small Pull Requests.</title>
      <dc:creator>Andrey Lebedev</dc:creator>
      <pubDate>Sun, 18 Jan 2026 13:21:33 +0000</pubDate>
      <link>https://dev.to/andrey_lebedev_db59283b0e/slicing-your-work-with-bdd-or-another-aspect-of-speed-increase-with-small-pull-requests-3ohd</link>
      <guid>https://dev.to/andrey_lebedev_db59283b0e/slicing-your-work-with-bdd-or-another-aspect-of-speed-increase-with-small-pull-requests-3ohd</guid>
      <description>&lt;p&gt;&lt;a href="https://medium.com/@andremoniy/slicing-your-work-with-bdd-or-another-aspect-of-speed-increase-with-small-pull-requests-4ad86a701c44" rel="noopener noreferrer"&gt;In this article&lt;/a&gt; I focused on such an aspect of the daily development process as pull requests and code review: how to make these artefacts more readable, smaller and how to make the code review process more efficient, faster and more practical.&lt;/p&gt;

</description>
      <category>codereview</category>
      <category>bdd</category>
      <category>agile</category>
      <category>programming</category>
    </item>
    <item>
      <title>What ArchiMate and BDD Have in Common at the Architectural Level</title>
      <dc:creator>Andrey Lebedev</dc:creator>
      <pubDate>Sun, 18 Jan 2026 13:20:13 +0000</pubDate>
      <link>https://dev.to/andrey_lebedev_db59283b0e/what-archimate-and-bdd-have-in-common-at-the-architectural-level-4jlb</link>
      <guid>https://dev.to/andrey_lebedev_db59283b0e/what-archimate-and-bdd-have-in-common-at-the-architectural-level-4jlb</guid>
      <description>&lt;p&gt;ArchiMate and BDD are rarely discussed together.&lt;br&gt;
Yet both trace back to the same foundational ideas in the Zachman / ISA framework and Sowa’s conceptual graphs.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/p/3dcf2b62353e" rel="noopener noreferrer"&gt;In this article&lt;/a&gt;, I explore how requirements, behaviour, and architecture align at a deeper level — without proposing a new methodology, just a different way of reasoning about systems.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>bdd</category>
      <category>agile</category>
      <category>nlp</category>
    </item>
  </channel>
</rss>
