<?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: Hugo Aguiar</title>
    <description>The latest articles on DEV Community by Hugo Aguiar (@hugodeaguiar).</description>
    <link>https://dev.to/hugodeaguiar</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%2F2634728%2F7f3c6625-b8b5-4f05-93d0-a13234bafd12.jpeg</url>
      <title>DEV Community: Hugo Aguiar</title>
      <link>https://dev.to/hugodeaguiar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hugodeaguiar"/>
    <language>en</language>
    <item>
      <title>OS: Public IP project</title>
      <dc:creator>Hugo Aguiar</dc:creator>
      <pubDate>Mon, 13 Jan 2025 21:15:41 +0000</pubDate>
      <link>https://dev.to/hugodeaguiar/os-public-ip-project-41ec</link>
      <guid>https://dev.to/hugodeaguiar/os-public-ip-project-41ec</guid>
      <description>&lt;p&gt;Hi everyone,&lt;/p&gt;

&lt;p&gt;Last year, I started a project, &lt;a href="https://getip.dev" rel="noopener noreferrer"&gt;https://getip.dev&lt;/a&gt;, intending to show your Public IP address to simplify this task as much as possible without thousands of Ads and pop-ups.&lt;/p&gt;

&lt;p&gt;Today I am opening the project code to the community so we can improve and turn this the best site to check your IP that everyone knows! &lt;/p&gt;

&lt;p&gt;So please, access the project on GitHub, give it a star, and start collaborating with it. Everyone is welcome.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/hugodeaguiar/public-ip" rel="noopener noreferrer"&gt;https://github.com/hugodeaguiar/public-ip&lt;/a&gt; &lt;/p&gt;

&lt;p&gt;Thank you &amp;lt;3 &lt;/p&gt;

</description>
      <category>network</category>
      <category>node</category>
      <category>opensource</category>
      <category>devops</category>
    </item>
    <item>
      <title>Continuous Feedback? That’s right! And we’re not talking about people management!</title>
      <dc:creator>Hugo Aguiar</dc:creator>
      <pubDate>Mon, 30 Dec 2024 20:06:34 +0000</pubDate>
      <link>https://dev.to/hugodeaguiar/continuous-feedback-thats-right-and-were-not-talking-about-people-management-28m0</link>
      <guid>https://dev.to/hugodeaguiar/continuous-feedback-thats-right-and-were-not-talking-about-people-management-28m0</guid>
      <description>&lt;p&gt;When we say that professionals in the DevOps field are responsible for implementing task automation—such as automated testing and automatic deployment—many people still fail to grasp the benefits of such tasks. So, let’s delve a little deeper into this topic.  &lt;/p&gt;

&lt;p&gt;In a development workflow without DevOps solutions in place, it’s very common to observe the following process:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Development of part of the system &amp;gt; Deployment &amp;gt; Testing (if any) &amp;gt; Bug creation  

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The main problem with this workflow is that it fosters feelings of helplessness among the development team, which generates negative factors for individuals and inevitably leads to harmful effects on deliverables. Implementing a workflow that minimizes this sense of helplessness will benefit the entire company.  &lt;/p&gt;

&lt;h2&gt;
  
  
  Continuous Feedback!
&lt;/h2&gt;

&lt;p&gt;The key to creating a more efficient workflow that also helps reduce the feeling of failure in teams is &lt;strong&gt;constant feedback&lt;/strong&gt;! Workflows that allow issues to be identified even before reaching the manual testing stage make all the difference. Let’s illustrate a basic DevOps workflow:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Task development &amp;gt; Merge Request creation &amp;gt; Code validation pipeline &amp;gt; Deployment &amp;gt; Testing  

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In this workflow, we add an automatic code validation step to identify syntax errors and prevent the creation of future rework tasks if an issue were identified during manual testing—or worse, in the production environment by the client, which would lead to much greater strain on the team and the client relationship.  &lt;/p&gt;

&lt;p&gt;We can conclude, then, that automation benefits the individuals working on the project, the client (who will have a more reliable and productive system), and the company as a whole—since it will likely spend less on code maintenance and can focus more on evolutionary tasks!  &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reference&lt;/strong&gt;: &lt;em&gt;DevOps Handbook&lt;/em&gt; (2018)  &lt;/p&gt;

</description>
      <category>devops</category>
      <category>automation</category>
      <category>pipeline</category>
    </item>
  </channel>
</rss>
