DEV Community: Tyclone81

Getting into the Git: Unlocking the Version Control

Tyclone81 — Thu, 02 Jul 2026 13:44:22 +0000

Just like any house requires a foundation or any chemical reaction requires individual elements, I realized coding requires an elaborate understanding of the version control system. My Git project was intentionally designed as a progressive journey into the world of version control and collaboration. Initially I could type commands in my terminal without necessarily being sure what they do, I quickly discovered this was not sustainable. I now have to unlearn, learn and relearn if I am to stand any chance in this field.

The project laid down the basics of what I need, starting from git init, a command to create a git repository to git push, one to send my project to the repository. I moved from ground up, git clone, a command to pull down project templates into my terminal, the staging cycle where my code moves between states. The three states of Git have become an integral part of my journey as everything coding is done here. The working directory comprises my active code files, the staging area, git add . & git commit -m and the repository, _git push _.

I hit this puzzle that required me to stage once but commit twice, and that's how I learnt git add -p , a command that allows me to commit sections of my file separately. Moving through the project taught me this deep web of commands that would become integral in group collaboration such as git switch -c, git log, git push origin (branch name), etc.

At the end of the project, my git skills progressed from frantic guesswork to deliberate, structural control. Indeed, git is not just a list of terminal prompts to memorize, it is a logical environment built to protect my work. Another week, another reason to look forward for more.

Science v Syntax: The Rude Awakening.

Tyclone81 — Sun, 28 Jun 2026 20:03:40 +0000

Passing the selection pool at Zone01 Kisumu was just the gate. Four weeks into my official journey to software development and I have been hit by a rude awakening! The case sensitivity of Go has already signaled me not to shade my laboratory skin off yet. The attention to detail shall come in handy. Miss a comma, brace, or even an exclamation mark and the program throws in syntax errors.
My introduction to this reality was go-reloaded, a command-line text parsing tool. The assignment sounded simple: take a raw text file, manipulate the strings, fix punctuation spacing, and convert the binary or hexadecimal strings to numbers.
The chemist in me figured I would logic my way through it in an hour. Instead, I immediately hit a wall trying to format punctuation marks (., ,, !). They need to close up to the word before them, but maintain a space after them. My clueless loops resulted in constant runtime crashes;
panic: runtime error: index out of range.

With assistance from a few of my peers(I had to sample ideas from a few to establish my base), I was able to break the execution into two phases. First I split the text string into a slice of individual words and characters. I then used Go's built in standard package, strconv , to look ahead and convert specific flags (like hex _and _bin to decimal), while cleaning up the slice indexes.

The feeling of being able to run my first program albeit with enormous help from my peers was so much fulfilling. Much like the feeling I used to get when I got a breakthrough on a particular research, never gets old really.
The biggest lesson I learned wasn't actually about Go syntax. It was learning that error messages are not a sign of personal failure. In science, an unexpected result is just data. In coding, a red error screen is exactly the same thing, it is just an input telling you exactly where your logic diverged from reality. Each day is a learning day.

Beginners #Golang #Zone01Kisumu

From the lab to the loop; Starting Again!

Tyclone81 — Sun, 28 Jun 2026 13:18:45 +0000

Start of the year this year I felt like I was completely trapped in this endless loop of self doubt. Fast forward 6 months into the year, I am completely locked in at Zone01 Kisumu as an aspiring software Developer.
Why jump ship from science to tech? That is the question I find myself facing from almost everyone around me right now. To me, the answer is straightforward: the world is evolving, and I want to be at the center of it all. It is the oldest rule in the jungle, the rule of natural selection. Either adapt, or get eliminated.
During my time in the science fraternity, I noticed a pattern. Most of the hiccups, bottlenecks, and major problems we faced were ultimately solved by technology, whether it was built internally or outsourced. I saw a massive opportunity right there. Instead of just relying on the tools, I wanted to learn how to build them.
So, I took the first step into the unknown. I decided to start over. Time will surely tell whether it was the right step or not, but I had to try.

Getting selected into Zone01 Kisumu however, had me questioning my decision to start again. Calling the selection process intense would be an understatement. Our perseverance and mental limits were seriously tested. "Where do you go now if you fail" is the question that could not leave my head, I guess I would never know now.
To anyone out there who is standing on the edge, wanting to make a fresh start, whether it is in your career, your family, or your employment: take that leap of faith. The unknown is terrifying, but staying stuck is worse, you got this!

beginners #golang #Zone01Kisumu