<?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: Shahar Taite</title>
    <description>The latest articles on DEV Community by Shahar Taite (@sht5).</description>
    <link>https://dev.to/sht5</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%2F125951%2Fdaf82f56-d69b-4b8c-bebb-3dd40419ed97.png</url>
      <title>DEV Community: Shahar Taite</title>
      <link>https://dev.to/sht5</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sht5"/>
    <language>en</language>
    <item>
      <title>Enforcing Go coding conventions and best practices with Cursor</title>
      <dc:creator>Shahar Taite</dc:creator>
      <pubDate>Wed, 23 Jul 2025 19:57:04 +0000</pubDate>
      <link>https://dev.to/sht5/enforcing-go-coding-conventions-and-best-practices-with-cursor-139l</link>
      <guid>https://dev.to/sht5/enforcing-go-coding-conventions-and-best-practices-with-cursor-139l</guid>
      <description>&lt;p&gt;Read my short blog about Enforcing Go coding conventions and best practices with Cursor&lt;br&gt;
&lt;/p&gt;
&lt;div class="crayons-card c-embed text-styles text-styles--secondary"&gt;
      &lt;div class="c-embed__cover"&gt;
        &lt;a href="https://www.linkedin.com/pulse/enforcing-coding-conventions-best-practices-cursor-shahar-taite-4tuof/?trackingId=DNMqntR952Z1EtYJp37GXA==" class="c-link s:max-w-50 align-middle" rel="noopener noreferrer"&gt;
          &lt;img alt="" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fmedia.licdn.com%2Fdms%2Fimage%2Fv2%2FD4D12AQHIUwvQZdUwAg%2Farticle-cover_image-shrink_720_1280%2FB4DZgytbGpH4AI-%2F0%2F1753197429552%3Fe%3D2147483647%26v%3Dbeta%26t%3DLVlZJBxY89R0zUz6J5GPvAmxZqyyVHAJUsOlZ02Llfc" height="427" class="m-0" width="760"&gt;
        &lt;/a&gt;
      &lt;/div&gt;
    &lt;div class="c-embed__body"&gt;
      &lt;h2 class="fs-xl lh-tight"&gt;
        &lt;a href="https://www.linkedin.com/pulse/enforcing-coding-conventions-best-practices-cursor-shahar-taite-4tuof/?trackingId=DNMqntR952Z1EtYJp37GXA==" rel="noopener noreferrer" class="c-link"&gt;
          Enforcing Coding conventions and best practices with Cursor 🤖
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;p class="truncate-at-3"&gt;
          I’ve been experimenting with using Cursor to enforce Go backend code conventions across services — and the results are super promising. Here at HUMAN we develop go code with a convention we like to call Backend structure, which includes project structure, use of common helper libraries for best prac
        &lt;/p&gt;
      &lt;div class="color-secondary fs-s flex items-center"&gt;
          &lt;img alt="favicon" class="c-embed__favicon m-0 mr-2 radius-0" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fstatic.licdn.com%2Faero-v1%2Fsc%2Fh%2Fal2o9zrvru7aqj8e1x2rzsrca" width="64" height="64"&gt;
        linkedin.com
      &lt;/div&gt;
    &lt;/div&gt;
&lt;/div&gt;


</description>
      <category>go</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>https://www.linkedin.com/pulse/enforcing-coding-conventions-best-practices-cursor-shahar-taite-4tuof/?trackingId=DNMqntR952Z1EtYJp37GXA%3D%3D #go #golang</title>
      <dc:creator>Shahar Taite</dc:creator>
      <pubDate>Wed, 23 Jul 2025 19:47:08 +0000</pubDate>
      <link>https://dev.to/sht5/-do6</link>
      <guid>https://dev.to/sht5/-do6</guid>
      <description></description>
      <category>go</category>
      <category>cleancode</category>
      <category>softwaredevelopment</category>
    </item>
  </channel>
</rss>
