<?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: George Hany</title>
    <description>The latest articles on DEV Community by George Hany (@george_hany_899df0785b4fe).</description>
    <link>https://dev.to/george_hany_899df0785b4fe</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%2F3538470%2Facf8fd9a-744d-49f4-8a98-b20aafcfb3d6.png</url>
      <title>DEV Community: George Hany</title>
      <link>https://dev.to/george_hany_899df0785b4fe</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/george_hany_899df0785b4fe"/>
    <language>en</language>
    <item>
      <title>“How to Build a Strong GitHub Portfolio”</title>
      <dc:creator>George Hany</dc:creator>
      <pubDate>Tue, 30 Sep 2025 01:58:30 +0000</pubDate>
      <link>https://dev.to/george_hany_899df0785b4fe/how-to-build-a-strong-github-portfolio-hki</link>
      <guid>https://dev.to/george_hany_899df0785b4fe/how-to-build-a-strong-github-portfolio-hki</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;Your GitHub profile is often the first thing recruiters check.&lt;br&gt;&lt;br&gt;
Here’s how to make it shine.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tips
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Pin your best projects
&lt;/li&gt;
&lt;li&gt;Write clear README files
&lt;/li&gt;
&lt;li&gt;Contribute to open source
&lt;/li&gt;
&lt;li&gt;Show consistency (commit history)
&lt;/li&gt;
&lt;li&gt;Use GitHub Actions for automation
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;A well-organized GitHub portfolio can speak louder than a résumé.&lt;/p&gt;

</description>
      <category>portfolio</category>
      <category>github</category>
      <category>tutorial</category>
      <category>career</category>
    </item>
    <item>
      <title>“Top 7 Git Commands Every Developer Should Know”</title>
      <dc:creator>George Hany</dc:creator>
      <pubDate>Tue, 30 Sep 2025 01:57:45 +0000</pubDate>
      <link>https://dev.to/george_hany_899df0785b4fe/top-7-git-commands-every-developer-should-know-46b3</link>
      <guid>https://dev.to/george_hany_899df0785b4fe/top-7-git-commands-every-developer-should-know-46b3</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;Git can feel overwhelming, but you don’t need to memorize everything.&lt;br&gt;&lt;br&gt;
Here are 7 commands you’ll use daily.&lt;/p&gt;

&lt;h2&gt;
  
  
  Essential Commands
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;git init&lt;/code&gt; → Start a repo
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;git clone&lt;/code&gt; → Copy an existing repo
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;git status&lt;/code&gt; → See changes
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;git add .&lt;/code&gt; → Stage changes
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;git commit -m "message"&lt;/code&gt; → Save changes
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;git push&lt;/code&gt; → Upload to remote
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;git pull&lt;/code&gt; → Download updates
&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Master these, and you’ll be productive in 90% of real-world Git scenarios.&lt;/p&gt;

</description>
      <category>git</category>
      <category>tutorial</category>
      <category>productivity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>“Understanding REST APIs in Simple Terms”</title>
      <dc:creator>George Hany</dc:creator>
      <pubDate>Tue, 30 Sep 2025 00:29:32 +0000</pubDate>
      <link>https://dev.to/george_hany_899df0785b4fe/understanding-rest-apis-in-simple-terms-1129</link>
      <guid>https://dev.to/george_hany_899df0785b4fe/understanding-rest-apis-in-simple-terms-1129</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;APIs are everywhere, but many beginners struggle to understand how they work.&lt;br&gt;&lt;br&gt;
This post explains REST APIs in plain language.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is an API?
&lt;/h2&gt;

&lt;p&gt;API stands for &lt;em&gt;Application Programming Interface&lt;/em&gt;.&lt;br&gt;&lt;br&gt;
It’s a way for two applications to talk to each other.&lt;/p&gt;

&lt;h2&gt;
  
  
  REST in Action
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GET&lt;/strong&gt; → fetch data (like reading a blog post)
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;POST&lt;/strong&gt; → create data (like writing a new post)
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PUT/PATCH&lt;/strong&gt; → update existing data
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;DELETE&lt;/strong&gt; → remove data
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;REST APIs are like a menu at a restaurant — you order what you need, and the server delivers it.&lt;/p&gt;

</description>
      <category>api</category>
      <category>beginners</category>
      <category>webdev</category>
    </item>
    <item>
      <title>“Why You Should Always Write Clean, Readable Code”</title>
      <dc:creator>George Hany</dc:creator>
      <pubDate>Tue, 30 Sep 2025 00:26:02 +0000</pubDate>
      <link>https://dev.to/george_hany_899df0785b4fe/why-you-should-always-write-clean-readable-code-2bj</link>
      <guid>https://dev.to/george_hany_899df0785b4fe/why-you-should-always-write-clean-readable-code-2bj</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;Anyone can write code that works, but not everyone writes code that’s easy to maintain.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Readability Matters
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Other developers need to understand your code&lt;/li&gt;
&lt;li&gt;Future you will thank you&lt;/li&gt;
&lt;li&gt;Clean code reduces bugs&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Tips
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Use meaningful variable names
&lt;/li&gt;
&lt;li&gt;Keep functions small and focused
&lt;/li&gt;
&lt;li&gt;Comment &lt;em&gt;why&lt;/em&gt;, not &lt;em&gt;what&lt;/em&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Readable code is professional code. Make it a habit.&lt;/p&gt;

</description>
      <category>softwaredevelopment</category>
      <category>coding</category>
      <category>productivity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>“Getting Started with React Hooks: useState and useEffect Explained”</title>
      <dc:creator>George Hany</dc:creator>
      <pubDate>Tue, 30 Sep 2025 00:24:24 +0000</pubDate>
      <link>https://dev.to/george_hany_899df0785b4fe/getting-started-with-react-hooks-usestate-and-useeffect-explained-52hp</link>
      <guid>https://dev.to/george_hany_899df0785b4fe/getting-started-with-react-hooks-usestate-and-useeffect-explained-52hp</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;React Hooks make it easier to manage state and side effects in functional components.&lt;br&gt;&lt;br&gt;
In this article, we’ll cover the basics of &lt;code&gt;useState&lt;/code&gt; and &lt;code&gt;useEffect&lt;/code&gt; with simple examples.&lt;/p&gt;

&lt;h2&gt;
  
  
  useState
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;useState&lt;/code&gt; lets you add state to functional components...&lt;/p&gt;

&lt;h2&gt;
  
  
  useEffect
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;useEffect&lt;/code&gt; helps you run side effects (like fetching data or updating the DOM)...&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Hooks are a powerful way to simplify React code. Start by mastering &lt;code&gt;useState&lt;/code&gt; and &lt;code&gt;useEffect&lt;/code&gt;.&lt;/p&gt;

</description>
      <category>tutorial</category>
      <category>javascript</category>
      <category>react</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
