<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fundamentals on Rowanto Luo</title><link>https://log.rowanto.com/tags/fundamentals/</link><description>Recent content in Fundamentals on Rowanto Luo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 03 Sep 2026 09:59:54 +0200</lastBuildDate><atom:link href="https://log.rowanto.com/tags/fundamentals/index.xml" rel="self" type="application/rss+xml"/><item><title>Git Fundamentals</title><link>https://log.rowanto.com/posts/git-fundamentals/</link><pubDate>Thu, 03 Sep 2026 09:59:54 +0200</pubDate><guid>https://log.rowanto.com/posts/git-fundamentals/</guid><description>
&lt;p&gt;It is not uncommon to meet fellow developers who are able to use git, we are ones ourselves. Most of us are able to commit, push, resolve conflicts, etc. However, how many would be still comfortable to use it when things deviate from a normal workflow? E.g., hotfix, recover deleted branch, fixing our local branch if the remote is squashed, detached HEAD, etc.&lt;/p&gt;
&lt;p&gt;These are all symptoms of learning git usage through surface level commands without understanding git itself. I was in the same boat, and many developers I spoke to share the same experience, especially the new ones. Hopefully, this article will give us an improved understanding about git to be able to leverage it more.&lt;/p&gt;</description></item></channel></rss>