<?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: Eyad abdelmoez mohamed</title>
    <description>The latest articles on DEV Community by Eyad abdelmoez mohamed (@eeyyaadd).</description>
    <link>https://dev.to/eeyyaadd</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%2F3983706%2Fabbee1a4-7739-4956-ae16-75238dbdc27a.jpg</url>
      <title>DEV Community: Eyad abdelmoez mohamed</title>
      <link>https://dev.to/eeyyaadd</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/eeyyaadd"/>
    <language>en</language>
    <item>
      <title>Why Poorly Formatted SQL Queries Slow Down Development Teams</title>
      <dc:creator>Eyad abdelmoez mohamed</dc:creator>
      <pubDate>Mon, 15 Jun 2026 11:14:54 +0000</pubDate>
      <link>https://dev.to/eeyyaadd/why-poorly-formatted-sql-queries-slow-down-development-teams-1ipa</link>
      <guid>https://dev.to/eeyyaadd/why-poorly-formatted-sql-queries-slow-down-development-teams-1ipa</guid>
      <description>&lt;p&gt;Every developer has opened a SQL file that looked like a wall of text.&lt;/p&gt;

&lt;p&gt;While SQL formatting may seem cosmetic, it directly impacts productivity, debugging speed, and collaboration between team members.&lt;/p&gt;

&lt;p&gt;Consider the following query:&lt;/p&gt;

&lt;p&gt;SELECT users.name,orders.total FROM users INNER JOIN orders ON users.id=orders.user_id WHERE orders.total &amp;gt; 1000 ORDER BY orders.created_at DESC;&lt;/p&gt;

&lt;p&gt;Technically correct? Yes.&lt;/p&gt;

&lt;p&gt;Easy to read? Not at all.&lt;/p&gt;

&lt;p&gt;Well-formatted SQL allows developers to:&lt;/p&gt;

&lt;p&gt;Identify joins quickly&lt;br&gt;
Spot logical errors faster&lt;br&gt;
Review pull requests more efficiently&lt;br&gt;
Reduce onboarding time for new team members&lt;/p&gt;

&lt;p&gt;Most modern development teams enforce formatting standards for the same reason they enforce coding standards.&lt;/p&gt;

&lt;p&gt;Best practices include:&lt;/p&gt;

&lt;p&gt;One column per line&lt;br&gt;
Uppercase SQL keywords&lt;br&gt;
Consistent indentation&lt;br&gt;
Clear JOIN separation&lt;br&gt;
Logical grouping of conditions&lt;/p&gt;

&lt;p&gt;Good formatting won't improve query performance, but it will improve developer performance.&lt;/p&gt;

&lt;p&gt;That's often just as important.&lt;/p&gt;

&lt;p&gt;Need a quick solution?&lt;/p&gt;

&lt;p&gt;Try our free SQL Formatter:&lt;br&gt;
&lt;a href="https://digitalmix.dev/tools/sql-formatter" rel="noopener noreferrer"&gt;https://digitalmix.dev/tools/sql-formatter&lt;/a&gt;&lt;/p&gt;

</description>
      <category>sql</category>
      <category>programming</category>
      <category>opensource</category>
      <category>automation</category>
    </item>
    <item>
      <title>5 Regular Expressions Every Developer Should Know</title>
      <dc:creator>Eyad abdelmoez mohamed</dc:creator>
      <pubDate>Sun, 14 Jun 2026 22:57:32 +0000</pubDate>
      <link>https://dev.to/eeyyaadd/5-regular-expressions-every-developer-should-know-5h1m</link>
      <guid>https://dev.to/eeyyaadd/5-regular-expressions-every-developer-should-know-5h1m</guid>
      <description>&lt;p&gt;Regular expressions can feel intimidating, but a few patterns solve most real-world problems.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Email Validation&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;^[^\s@]+@[^\s@]+.[^\s@]+$&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;URL Detection&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;https?://[^\s]+&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Extract Numbers&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;\d+&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Remove Extra Spaces&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;\s+&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Strong Password Validation&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;^(?=.[A-Z])(?=.[a-z])(?=.*\d).{8,}$&lt;/p&gt;

&lt;p&gt;The biggest mistake developers make with regex is trying to memorize everything.&lt;/p&gt;

&lt;p&gt;Instead, build a small collection of patterns you use repeatedly and test them with real-world examples.&lt;/p&gt;

&lt;p&gt;Regex is not about memorization.&lt;/p&gt;

&lt;p&gt;It's about pattern recognition.&lt;/p&gt;

</description>
      <category>development</category>
      <category>devops</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>Why Poorly Formatted SQL Queries Slow Down Development Teams</title>
      <dc:creator>Eyad abdelmoez mohamed</dc:creator>
      <pubDate>Sun, 14 Jun 2026 11:10:55 +0000</pubDate>
      <link>https://dev.to/eeyyaadd/why-poorly-formatted-sql-queries-slow-down-development-teams-23nc</link>
      <guid>https://dev.to/eeyyaadd/why-poorly-formatted-sql-queries-slow-down-development-teams-23nc</guid>
      <description>&lt;p&gt;Every developer has opened a SQL file that looked like a wall of text.&lt;/p&gt;

&lt;p&gt;While SQL formatting may seem cosmetic, it directly impacts productivity, debugging speed, and collaboration between team members.&lt;/p&gt;

&lt;p&gt;Consider the following query:&lt;/p&gt;

&lt;p&gt;SELECT users.name,orders.total FROM users INNER JOIN orders ON users.id=orders.user_id WHERE orders.total &amp;gt; 1000 ORDER BY orders.created_at DESC;&lt;/p&gt;

&lt;p&gt;Technically correct? Yes.&lt;/p&gt;

&lt;p&gt;Easy to read? Not at all.&lt;/p&gt;

&lt;p&gt;Well-formatted SQL allows developers to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Identify joins quickly&lt;/li&gt;
&lt;li&gt;Spot logical errors faster&lt;/li&gt;
&lt;li&gt;Review pull requests more efficiently&lt;/li&gt;
&lt;li&gt;Reduce onboarding time for new team members&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most modern development teams enforce formatting standards for the same reason they enforce coding standards.&lt;/p&gt;

&lt;p&gt;Best practices include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;One column per line&lt;/li&gt;
&lt;li&gt;Uppercase SQL keywords&lt;/li&gt;
&lt;li&gt;Consistent indentation&lt;/li&gt;
&lt;li&gt;Clear JOIN separation&lt;/li&gt;
&lt;li&gt;Logical grouping of conditions&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Good formatting won't improve query performance, but it will improve developer performance.&lt;/p&gt;

&lt;p&gt;That's often just as important.&lt;/p&gt;

&lt;p&gt;Need a quick solution?&lt;/p&gt;

&lt;p&gt;Try our free SQL Formatter:&lt;br&gt;
&lt;a href="https://digitalmix.dev/tools/sql-formatter" rel="noopener noreferrer"&gt;https://digitalmix.dev/tools/sql-formatter&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>database</category>
      <category>sql</category>
      <category>mysql</category>
    </item>
  </channel>
</rss>
