Except as soon as you want to do something nontrivial, you will need to learn about makefiles, and then perhaps compiler options, and after that probably git, and before you know it you will be deep in the mire.
Makefiles are actually next to trivial and very easy to learn. More complex build systems such as autoconf, cmake, etc. are more difficult, but they are not required until the project gets big and/or aims to be cross-platform compatible and become public.
Compiler options are learned and added as you need them. Defaults are fine, except that it is a good idea to use "-Wall -pedantic" right from the start.
Git will eventually become required no matter what ecosystem you choose, except when you opt for that Microsoft-made makeshift nonsense forced upon the unlucky ones (used to be called VSS, no idea how it's called now) that they created only to reinvent the wheel and avoid following one of the industry-standard solutions. And even then you still need to know a necessary minimum of Git.
But it's not required for a beginner playing around and making first steps on her/his local machine.
The good thing about the Linux ecosystem, or the Unix-style approach to programming and controlling the machine in general, is that you learn and begin to deal with each new entity only as it becomes needed. Step by step, simple to complex, perfect for learning.
Anyone who tells you that programming is simple is being economical with the truth.
Couldn't be said better.
Yes, programming IS simple. You just tell the machine what it has to do, can it be any simpler?
But there are certain nuances, which the beginner doesn't need to know right away -- that's what you called being economical with the truth

.