<?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: Manuel Sanchez</title>
    <description>The latest articles on DEV Community by Manuel Sanchez (@manuelsanchez2).</description>
    <link>https://dev.to/manuelsanchez2</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%2F442131%2F610b184f-ec5c-4bcd-af8e-0ce24afcc041.jpg</url>
      <title>DEV Community: Manuel Sanchez</title>
      <link>https://dev.to/manuelsanchez2</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/manuelsanchez2"/>
    <language>en</language>
    <item>
      <title>Creating a Youtube Channel on Coding for Noobs</title>
      <dc:creator>Manuel Sanchez</dc:creator>
      <pubDate>Mon, 21 Dec 2020 17:11:57 +0000</pubDate>
      <link>https://dev.to/manuelsanchez2/creating-a-youtube-channel-on-coding-for-noobs-3dcn</link>
      <guid>https://dev.to/manuelsanchez2/creating-a-youtube-channel-on-coding-for-noobs-3dcn</guid>
      <description>&lt;p&gt;Hi there! Hope this post reaches you out well! I am relatively new to this world. To put it in a nutshell, after losing my job as a Content Marketer some months ago, I attended a 3-month bootcamp on coding and few weeks after I found a job as a frontend web developer. And every single day  I am learning new cool things!&lt;/p&gt;

&lt;p&gt;I decided to open a YouTube Channel to help people like me, who were completely unaware of how cool all this is. You know, to help people dive in. That's why I thought the name Dev4Noobs was quite appropriate.&lt;/p&gt;

&lt;p&gt;I wanted to write this post to ask you for some kind of advice: what type of content would you suggest me doing? Long or short videos? Do you thing there is a lack of videos on any specific topic worth looking at? &lt;/p&gt;

&lt;p&gt;This is the account so far:&lt;br&gt;
&lt;a href="https://www.youtube.com/channel/UCtxh0DXIjizByJ1Rzq72Qog" rel="noopener noreferrer"&gt;https://www.youtube.com/channel/UCtxh0DXIjizByJ1Rzq72Qog&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thanks in advance for your time!&lt;br&gt;
Stay safe!&lt;/p&gt;

</description>
      <category>youtube</category>
      <category>html</category>
      <category>css</category>
      <category>react</category>
    </item>
    <item>
      <title>Git, Git, Git: what the heck is Git?</title>
      <dc:creator>Manuel Sanchez</dc:creator>
      <pubDate>Tue, 15 Dec 2020 17:25:09 +0000</pubDate>
      <link>https://dev.to/manuelsanchez2/git-git-git-what-the-heck-is-git-1jm8</link>
      <guid>https://dev.to/manuelsanchez2/git-git-git-what-the-heck-is-git-1jm8</guid>
      <description>&lt;p&gt;I have to admit that when I was learning to code and my coach came with the term “control version”, it took a while until I grasped what he meant by that. Git came to my early life as a developer, and since that very moment, it is not very easy to get rid of it.&lt;/p&gt;

&lt;p&gt;But what is Git and what is meant by control version? Well, the easiest way to describe it is like you have a very accurate record of your project at any time, and &lt;strong&gt;not only local&lt;/strong&gt; -at your computer- &lt;strong&gt;but also remote&lt;/strong&gt; -on services like GitHub or GitLab. &lt;/p&gt;

&lt;p&gt;So for example, let’s say you create a project from scratch, let’s say you are creating your portfolio page, and you are keeping a record of every single (important) step you are making. &lt;strong&gt;This way you can accomplish several things: you can always take a look where you are, where you began, what you have done so far, share your code, import your code, etc&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Git is much more than that but I think that it a very good definition to start with!&lt;/p&gt;

&lt;p&gt;Once we understand the term control version, we should jump onto the “branches” culture.&lt;/p&gt;

&lt;p&gt;We like working in a relatively organised way, right? In order to do it properly, developers work with branches. Let’s say you have your main branch, normally called &lt;strong&gt;master&lt;/strong&gt;. The easiest approach could be to have in this branch the best and most recent version of our project. Imagine you create a branch called footer and then you create the footer and when you are done, you say: footer branch should be included in my main branch. This process is called merge.&lt;/p&gt;

&lt;p&gt;Why is this approach so cool? Because &lt;strong&gt;you can ask your friend Mario to create for example the header branch, your friend Luigi to create the main section branch, while you take care of your precious footer. And at the end of the day every one merges its branch into master&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;This is also a very easy way to have a classical git merge conflict! But since this article was meant to talk about happy things, git conflicts will be addressed in another article.&lt;/p&gt;

&lt;p&gt;All in all, Git is really cool, there are a couple of tutorials that are worth watching and will fast increase your value as a developer while you learn to master it. &lt;/p&gt;

&lt;p&gt;Ah, and if you messed it up a lot with Git, there is one page you should know: &lt;a href="https://ohshitgit.com/" rel="noopener noreferrer"&gt;https://ohshitgit.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;That’s all for today! &lt;/p&gt;

</description>
      <category>git</category>
      <category>github</category>
      <category>merge</category>
    </item>
  </channel>
</rss>
