<?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: Jacob Martin</title>
    <description>The latest articles on DEV Community by Jacob Martin (@unsungdeveloper).</description>
    <link>https://dev.to/unsungdeveloper</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%2F469671%2Fbc3da4e0-d7a2-4eb4-af12-51b684ff8ed3.jpeg</url>
      <title>DEV Community: Jacob Martin</title>
      <link>https://dev.to/unsungdeveloper</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/unsungdeveloper"/>
    <language>en</language>
    <item>
      <title>freeCodeCamp New Responsive Web Design Curriculum.</title>
      <dc:creator>Jacob Martin</dc:creator>
      <pubDate>Thu, 22 Sep 2022 12:33:03 +0000</pubDate>
      <link>https://dev.to/unsungdeveloper/freecodecamp-new-responsive-web-design-curriculum-2h02</link>
      <guid>https://dev.to/unsungdeveloper/freecodecamp-new-responsive-web-design-curriculum-2h02</guid>
      <description>&lt;h1&gt;
  
  
  All you need to know...
&lt;/h1&gt;

&lt;p&gt;Presently I am revising CSS styles from @freeCodeCamp, and I want to commend them for improving how they tutor the new Responsive Web design curriculum. I’m currently enjoying the CSS challenges, and my experience is being enhanced by&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;About coursework&lt;/strong&gt; – First, the old coursework for the Responsive Web Design Curriculum is still intact and renamed to Legacy Responsive Web Design right at the bottom of the curriculum ladder board. In addition, your progress in the Legacy Responsive Web Design is still intact, and your certification is still valid. The new curriculum coaching has improved. That is the big difference and game changer from my end.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;New editor&lt;/strong&gt; – The new editor works similarly to an external editor, for example, (visual studio code or sublime text) used on local computers. You must link your styles.css file to your HTML for your code to run. Additionally, you have access to both index.html and styles.css files while working. The latter provides learners with room for tracking practice progress.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Seek help&lt;/strong&gt; – The new version help link redirects you to a read-search-ask method which implies you can read the documentation or error, google, or ask friends. Equally, you can join the @freeCodeCamp community forum and post your issues. The old version provided a watch video when seeking help which the new curriculum does not. These improve the ability of newbies to google and develop strong problem-solving skills.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Certification&lt;/strong&gt; – The certification is similar to the older version, which you get upon completing five (5) certification projects. In addition, you can still claim certificates from the old version curriculum if you completed the projects or intend to finish the curriculum if already in progress.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;About Project&lt;/strong&gt; – Five projects are done in both versions. The big difference here, however, is that in the new curriculum, you build your project after completing a given section of the CSS course and not the whole course. For example, after finishing forms, you will match onto the next CSS challenge (flexbox) before undertaking another project. I feel the latter way gets newbie devs to complete projects unlike stacking the whole five (5) projects at the end of the CSS curriculum.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

</description>
    </item>
    <item>
      <title>Getting my groove Back</title>
      <dc:creator>Jacob Martin</dc:creator>
      <pubDate>Tue, 20 Sep 2022 05:35:48 +0000</pubDate>
      <link>https://dev.to/unsungdeveloper/getting-my-groove-back-4d14</link>
      <guid>https://dev.to/unsungdeveloper/getting-my-groove-back-4d14</guid>
      <description>&lt;p&gt;Finding my groove back to coding after a long break has been one of the toughest challenges I have faced in my tech journey. However, thanks to self-discipline and adopting positive habits. Gradually coming along &amp;amp; pulling myself together. &lt;/p&gt;

&lt;p&gt;Here is how I do it&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;   Planning for your day – You can not be a master of all. Planning helps you approach your tasks in succession. You achieve greatness when you allocate time and effort to accomplish the task you had a plan on achieving.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;ul&gt;
&lt;li&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;    Work Out – When you exercise, your body releases chemicals called endorphins. Endorphins trigger a positive feeling in the body and elevate your morale to tackle your day bugs. Go crush it and if possible work out in the morning.
&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;
&lt;li&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;    Set Realistic Goal – The landscape of web development is ever-changing. It is therefore important that you discern between learning new frameworks vs having strategic career goals, for example, Technical goals, job goals, or community goals.
&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;
&lt;li&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;    Take breaks – It's very important to take breaks when coding. In my case, I can focus on a certain thing for about 30-40 minutes.
&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;
&lt;li&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;    Meditate - Reflect on your coding journey. This is important in setting realistic goals and achievable targets. Remember this is your future, you have to see yourself in the future if the practices you are doing now will eventually get you to it.
&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;
&lt;li&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;    Work on projects you are comfortable doing – Start that side project that you never did earlier, contribute to open-source projects or build that portfolio you never did, but start working with what you are okay with    
&lt;/code&gt;&lt;/pre&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
    </item>
    <item>
      <title>Today was a good day. Got lost into programming structure in JavaScript.</title>
      <dc:creator>Jacob Martin</dc:creator>
      <pubDate>Wed, 16 Sep 2020 14:56:47 +0000</pubDate>
      <link>https://dev.to/unsungdeveloper/today-was-a-good-day-got-lost-in-programming-structure-in-javascript-l7m</link>
      <guid>https://dev.to/unsungdeveloper/today-was-a-good-day-got-lost-in-programming-structure-in-javascript-l7m</guid>
      <description></description>
    </item>
  </channel>
</rss>
