What I Gained from Personal Development and a Passion for Computers in My Work

Hello, it's Munou here.
I've been so busy that I realized I'd forgotten to update for quite a while.
My apologies.

Just a thought

I understand the anxiety one feels when they like tinkering with computers but can't quite make it a job.
This is because for geeks and nerds, there's always someone better, so it's undeniable that there's a feeling of "can I really make this a job myself?"
However, people who love computers often also possess arrogance, thinking "I'm the best...". Yet, on the flip side, they often keenly feel their own weaknesses.
In a way, this might be the kind of struggle that lies behind the words of Perl creator Larry Wall, who famously joked about "laziness, impatience, and hubris."

Github Activities

My first encounter with Github was around 2016, but essentially, I was just a "read-only member," or rather, I only did git clone.
Back then, as a middle schooler, I wondered, "Why do I have to use this when I don't even know where to download things from?!"
At that time, GPU mining was popular, and as an extension of that, there was software that would brute-force hash values generated by Unix's crypt(3) to crack keys. I remember cloning something for the very first time just to use that.

Time passes, into my 20s

Speaking of which, it was quite recently that I registered to share software I had modified for my own use, after seeing someone on a 5channel software board looking for something similar.
As I was setting up my home server and doing various things, scripts would often get lost or wiped out, so to avoid the pain of that each time, I started doing git push.
That's pretty much it, but somehow I've become proficient with git operations, but...

Differences when using it for work

Perhaps it's things like conflicts occurring, or starting to use git blame. After all, even if you occasionally submit pull requests for OSS activities, these things don't happen unless you continuously work on a single repository.
But if you have clear operations you need and use them daily for work, I don't think it's that difficult.
However, the truth is that git itself is too feature-rich, and I haven't mastered all of it.

Benefits of personal projects

If I were to mention something useful, for example, I use the following format for commit messages:↓

$ git --no-pager log
commit 37d71cc01d1bce5b3d5d748b24c61f0d84f4c88b (HEAD -> main, origin/main)
Author: haturatu <taro@eyes4you.org>
Date:   Mon Mar 17 08:06:00 2025 +0900

    fix: readme

commit d14075115766ac0dec86f8a9a5208d1834e0c018
Author: haturatu <taro@eyes4you.org>
Date:   Mon Mar 17 00:29:44 2025 +0900

    add: gscp

commit dd932e5db50a4610fa59e08cd4aa2ee11d5eeb4d
Author: haturatu <taro@eyes4you.org>
Date:   Mon Mar 17 00:06:56 2025 +0900

    first commit
alleycat:[haturatu]:~/git/gscp$ 

I simply put add or fix at the beginning.
Since this is for my own repository, I keep it very simple, but for work, I write commit messages in Japanese on the CLI, which feels a bit awkward. Roughly, when adding features or files, I use add; when deleting features or files, del; and for corrections, fix. The benefit of doing this is that it helps develop the habit of properly categorizing commit messages.

git commit -m "fix: aaa" -m "add: bbb" -m "del: ccc"

One might say, "If you're writing multiple commit messages like that, just split the commits," but currently, I don't make huge, sudden changes, so the above is sufficient.

It's easy to talk about computers

This... well, it depends on the environment, but I'm incredibly grateful that I can talk about computers daily now.

I realized later that "floating fish" (people like me) on the internet might be seeking a place to share, or for recognition, or a place to express themselves, because they don't have one in the real world. In other words, perhaps the "floating fish" active on the internet also have some unfulfilled aspects in the real world, which is why they are outputting it online.

Adapting to the unknown?

I don't really feel this much, but when I get curious about the behavior of various software or things I haven't written/can't write, and I read the code, I can grasp it to some extent, so it becomes relatively easy to get into.
Or rather, most things can be figured out by just trying, so it doesn't seem too difficult.

And the difference from just personal activities is having people around you whom you can ask.
This also has a mental aspect, but typically, when you're stuck in the "swamp" of personal activities, you might endlessly continue working for two days without sleep, as I have in the past. However, if you have team members, you can think, "I don't understand this, I'll ask when I have time," or "They're not here now and seem busy, so I'll ask later and put it aside for now."
While it's undeniable that this can lead to a habit of procrastination, if rolling a die for a higher chance of resolution means waiting until the next day when that person is available, wouldn't that be better?

In closing

I just wrote this, but I guess this is how it turned out...
I feel like there was something else, but if anything else comes to mind, I'll jot it down casually.
See you again. Best regards.