I used to think my code was broken.Turns out it wasn’t the code,it was me not understanding Git.
The beginning: confusion everywhere
When I first started using Git, it felt difficult.Typing commands in the terminal, seeing outputs I didn’t understand, and dealing with rules that felt like they were there just to complicate things.
I thought Git was supposed to help me build projects easily.Instead, it felt like something that slowed me down.
Where things went wrong
At some point, I messed things up and had to use commands like reflog and restore to fix my mistakes.
That’s when it hit me.Git wasn’t broken, I just didn’t understand what I was doing.
I was trying to use a system without understanding how it actually works.
What changed
I didn’t suddenly get smarter.I just practiced.
A month ago, things started clicking because I kept using Git, making mistakes, fixing them, and repeating the cycle.
Slowly, I stopped seeing it as confusing rules and started seeing it as history tracking.
Then came Go
I also started learning Go.
My first thought was simple:
“This is new, but I can learn it.”
I started small like printing output, working with runes, counting characters, basic stuff.
Nothing fancy.
What feels different about Go
Go feels very step-by-step.You don’t really guess your way through it.You solve problems one small piece at a time.
It’s structured, clear, direct.
Right now, I’m still learning it, but it doesn’t feel impossible, just new.
What I’ve learned so far
The biggest lesson isn’t Git or Go.
It’s this:
You can actually learn new things even if you have no background or experience.
But you have to start with two things:
1.Accept that you don’t know
2.Have the will to learn
Ask questions, make mistakes, do it scared and do it clueless.
Because waiting until you feel ready usually means never starting.
Top comments (0)