<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Git on Antonio Montemurro</title><link>https://antoniomontemurro.com/en/tags/git/</link><description>Recent content in Git on Antonio Montemurro</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 17 Sep 2024 19:33:08 +0000</lastBuildDate><atom:link href="https://antoniomontemurro.com/en/tags/git/index.xml" rel="self" type="application/rss+xml"/><item><title>Version Control</title><link>https://antoniomontemurro.com/en/posts/version-contrl/</link><pubDate>Tue, 17 Sep 2024 19:33:08 +0000</pubDate><guid>https://antoniomontemurro.com/en/posts/version-contrl/</guid><description>&lt;p&gt;In any activity that involves creating something, there is always the possibility of wanting to make changes to your work, only to realize that you’ve made a mistake and can’t go back. And this is precisely where version control systems come to the rescue!&lt;/p&gt;
&lt;h2 id="version-control-system"&gt;Version Control System&lt;/h2&gt;
&lt;p&gt;One of the first challenges faced during professional growth in the field of computing is managing code and its changes.&lt;/p&gt;
&lt;p&gt;Imagine writing a function, and after hours of work, you decide to modify some parts, only to realize that the new changes not only don’t work but weren’t even necessary. Moreover, the classic CTRL+Z might not be enough to go back far enough.&lt;/p&gt;</description></item></channel></rss>