<?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: nicolasnardi404</title>
    <description>The latest articles on DEV Community by nicolasnardi404 (@nicolasnardi404).</description>
    <link>https://dev.to/nicolasnardi404</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%2F1408047%2F21e50261-8a95-4c02-b730-b3ccf215d713.png</url>
      <title>DEV Community: nicolasnardi404</title>
      <link>https://dev.to/nicolasnardi404</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/nicolasnardi404"/>
    <language>en</language>
    <item>
      <title>Do you test your code?</title>
      <dc:creator>nicolasnardi404</dc:creator>
      <pubDate>Mon, 10 Jun 2024 12:13:43 +0000</pubDate>
      <link>https://dev.to/nicolasnardi404/do-you-test-your-code-ggm</link>
      <guid>https://dev.to/nicolasnardi404/do-you-test-your-code-ggm</guid>
      <description>&lt;p&gt;I've been coding for about eight months now. My journey started with the Piscine at 42 School—a four-week program where I got my feet wet with C programming. Next, I enrolled in Scrimba's Front End BootCamp to work more with front-end. Currently, I'm in the final stretch of a full-stack coding course, which is part of a 600-hour program.&lt;/p&gt;

&lt;p&gt;One thing that's been puzzling me is why so many coding programs don't emphasize testing right from the beginning. I reached out to ChatGPT for insights—because what's better than a machine to answer me this—and the responses pointed towards complexity and the idea that it would be covered later. However, I'm convinced that testing early on is crucial for developing robust and reliable code.&lt;/p&gt;

&lt;p&gt;Testing isn't just an afterthought; it's a fundamental aspect of coding that deserves attention from the start. Ignoring it early on can lead to bad habits and potentially costly mistakes down the line. Moreover, it's surprising to hear about companies that seemingly operate without thorough testing. It highlights the importance of prioritizing testing in our coding practices.&lt;/p&gt;

&lt;p&gt;To the coding community, please, let’s talk more about testing. Sharing experiences, challenges, and successes can help us all become better programmers. Tests are all about improving the quality and reliability of our code.&lt;/p&gt;

&lt;p&gt;In conclusion, let's acknowledge the significance of testing in our coding journeys. It's time we integrated it into our practices from the very beginning. Happy coding, and don't forget to keep tests in your heart and in your code. &amp;lt;3&lt;/p&gt;

</description>
      <category>testing</category>
      <category>webdev</category>
      <category>beginners</category>
      <category>programming</category>
    </item>
    <item>
      <title>My life into coding #1 the first course - 42 School</title>
      <dc:creator>nicolasnardi404</dc:creator>
      <pubDate>Fri, 05 Apr 2024 10:51:59 +0000</pubDate>
      <link>https://dev.to/nicolasnardi404/my-life-into-coding-1-the-first-course-42-school-17c7</link>
      <guid>https://dev.to/nicolasnardi404/my-life-into-coding-1-the-first-course-42-school-17c7</guid>
      <description>&lt;p&gt;I'm starting a series of articles in which I want to write about my coding journey and the different approaches and experiences I'm having during this life journey of studying coding.&lt;/p&gt;

&lt;p&gt;It's a way of keeping a diary of my studies and sharing my progress.&lt;/p&gt;

&lt;p&gt;My first experience started with 42 School's Piscine project - a free international coding school. They have schools in various places and I signed up for their program because it was the cheapest (free) option I had at the time. I definitely didn't have the money to spend on a bootcamp. &lt;/p&gt;

&lt;p&gt;The admission program - also called Piscine - is an intensive one-month course, every day, to see if you are able to adapt to their learning method. There are no teachers, no classes, just other students to help you and the famous internet.&lt;/p&gt;

&lt;p&gt;I didn't pass the 2-year intensive program, but I had already thought, before finishing Piscine, about not continuing with it for a few reasons.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the entire course is only in the C language;&lt;/li&gt;
&lt;li&gt;I'm a queer person and there were a lot of straight people with a macho mentality around. I was in Berlin at the time, so I expected things to be a bit different;&lt;/li&gt;
&lt;li&gt;I asked if anyone already had a job as a programmer and even the people with almost a year of course still weren't working in the field;&lt;/li&gt;
&lt;li&gt;Most of the people studying there were struggling to follow the program. The only ones who were a bit more chill were people who had the privilege of not having to worry about money or were receiving some kind of government benefit. Those who had to work full-time or part-time were struggling.&lt;/li&gt;
&lt;li&gt;I like having classes and at least having a base material to follow. Otherwise, why would I be at school and not at home studying whatever I wanted?&lt;/li&gt;
&lt;li&gt;WTF I can do only with C language?
In any case, I would recommend Piscine to anyone interested in having a first experience with programming. There will be intense days with lots of programming and without spending any money for it. It really helps to break the ice and start programming. At least that's how it was for me. C is terrible, but taking a look at it before anything else is a good start - but not for 2 years.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>beginners</category>
      <category>42</category>
      <category>learning</category>
    </item>
  </channel>
</rss>
