<?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: Emmanuel Uchewa</title>
    <description>The latest articles on DEV Community by Emmanuel Uchewa (@emmajnr1000).</description>
    <link>https://dev.to/emmajnr1000</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%2F464025%2Fcf0157df-21af-456b-b706-00ccdf6c0f7e.jpg</url>
      <title>DEV Community: Emmanuel Uchewa</title>
      <link>https://dev.to/emmajnr1000</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/emmajnr1000"/>
    <language>en</language>
    <item>
      <title>A note for beginner programmers.</title>
      <dc:creator>Emmanuel Uchewa</dc:creator>
      <pubDate>Wed, 28 Jun 2023 15:38:42 +0000</pubDate>
      <link>https://dev.to/emmajnr1000/a-note-for-beginner-programmers-2jo4</link>
      <guid>https://dev.to/emmajnr1000/a-note-for-beginner-programmers-2jo4</guid>
      <description>&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--AhI2Q2xE--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/woqu35r9pmeozsyoe6gm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--AhI2Q2xE--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/woqu35r9pmeozsyoe6gm.png" alt="beginner's building block to programming" width="500" height="333"&gt;&lt;/a&gt;&lt;br&gt;
Watching YouTube tutorials and reading huge tutorial PDFs are a great way to learn, but nothing beats getting your hands dirty building stuff. Less tutorials and more building.&lt;/p&gt;

&lt;p&gt;Learning is progressive, you do not need to know everything in a specific programming language or framework before you start working with it.&lt;/p&gt;

&lt;p&gt;ChatGPT is wonderfull, avoid it like a plague 😁. ChatGPT is like a drug which you can easily get addicted to and just like a drug abuser you will no longer be able to do anything without it thereby losing the ability to think for yourself.&lt;/p&gt;

&lt;p&gt;Allways ask for feedback on your work. When you open your work up for criticism you should be open to hearing things you don't like, things that will make you feel bad and angry, and also things you probably don't agree with.&lt;/p&gt;

&lt;p&gt;But one thing criticism does is that it helps us give a second look at our work, whether we agree with what has been said about it or not, it gives us fresh perspective to look at our work.&lt;/p&gt;

&lt;p&gt;Criticism is good, but always get ready for damaging words when you want to be criticized. Stay resilient and keep an open mind!&lt;/p&gt;

&lt;p&gt;Lastly, always be prepared for change. Programming and technology are ever-changing fields. I understand that change is difficult and sometimes overwhelming, but it is the only way for us to try so many tools and choose which one is best for the job. Always be willing to shift from what works to what works better.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Building applications using (PIC) progressive Incremental Change method.</title>
      <dc:creator>Emmanuel Uchewa</dc:creator>
      <pubDate>Thu, 08 Dec 2022 14:50:15 +0000</pubDate>
      <link>https://dev.to/emmajnr1000/building-applications-using-progressive-incremental-change-method-5f09</link>
      <guid>https://dev.to/emmajnr1000/building-applications-using-progressive-incremental-change-method-5f09</guid>
      <description>&lt;p&gt;The progressive incremental change method is a software development approach that entails constructing an application in tiny, incremental phases. This technique is a popular alternative to the traditional "big bang" process of building an application all at once and then deploying it in a single, massive update.&lt;/p&gt;

&lt;p&gt;In a variety of ways, the progressive incremental change strategy outperforms the old approach. For starters, it allows developers to independently test each change, allowing them to identify and solve any flaws before they become big issues. Additionally, this technique enables developers to collect user feedback at each stage of development, which may help influence the application's direction and ensure that it meets their needs.&lt;/p&gt;

&lt;p&gt;Another advantage of the progressive incremental change technique is that it enables developers to provide new features and upgrades to consumers on a more frequent basis. This can help keep users engaged and interested in the application while also assisting developers in gaining extra data on how users interact with the application, which can be used to improve future updates.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implimentation
&lt;/h2&gt;

&lt;p&gt;To use the progressive incremental change method, developers must first define the essential functionality of their application, without which the application would be useless, and then construct that core feature in a series of small, incremental stages. This can include breaking down the development process into smaller, more manageable portions, such as adding a new feature or upgrading an existing one.&lt;/p&gt;

&lt;p&gt;Once the core functionality has been developed, the developers can proceed to add other features and upgrades to the application in a similar manner. Working with users to get feedback on the application and incorporate their suggestions into future upgrades is one example.&lt;/p&gt;

&lt;p&gt;In general, the progressive incremental change strategy is a useful tool for developing apps. By breaking down the development process into simple, manageable chunks, developers may build applications more swiftly and effectively, while also keeping users engaged and satisfied.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>webdev</category>
      <category>android</category>
      <category>react</category>
    </item>
  </channel>
</rss>
