The Mindset of Eliminating Tedious Tasks Is Essential for Improving Your Programming Skills

Once you become proficient in writing code to some extent, you find yourself spending more time researching how to use libraries and APIs—focusing on usage rather than syntax.

Being able to manage most tasks within your current knowledge base provides a sense of speed and a certain level of comfort.
However, it's difficult to improve further if you stay in that zone. I believe it's crucial to keep challenging yourself with new things.

Your current skills are an accumulation of your past experiences.
And fortunately, the world is full of wonderful code written by engineers far more talented than oneself.

I want to write code that won't be heavily criticized by future engineers. (In fact, that person suffering from my poor code might be me just a few months from now.)
To achieve this, one should learn from excellent engineers, expand their own skills, and strive to perform superior programming.

I'm writing this article because I feel it's essential to stop tolerating "tedious things" to write code that makes both future engineers and yourself happy.

Don't Overlook the Small Inconveniences

"Efficiently," "More easily," "More simply."
By adopting this mindset, you should be able to write better code than you do now.

Have you ever had an experience like this?
"I didn't know there was a way to do it like this..."

I believe this very moment is when improvement happens.
Try to recall when you felt that emotion.
It might have been something someone mentioned in passing, or something that caught your eye while you were reading a topic unrelated to your original goal.

Perhaps you had been turning a blind eye to it, but didn't you actually find it a little tedious?
In the network age, you need to actively seek out information; otherwise, your repertoire won't grow.
If you stick with old ways of thinking, you will inevitably decline.

You should thoroughly investigate even the slightest inconveniences in your current development environment. Talented engineers are likely already working on solutions.
By encountering and understanding their perspectives, the quality of the code you write will surely change significantly.

There must be a simpler, easier way to write the code you are working on right now.
I encourage you to remember the redundant code you've been ignoring in the back of your mind and dedicate yourself to refactoring it.

Deriving Your Own Solutions

It's not cool to just follow in someone else's footsteps forever.
Gradually, while leaning on the shoulders of excellent engineers to improve my own level, I want to become someone who can provide topics that solve problems for others.

To that end, I intend to continue making the effort to share the knowledge I gain, regardless of the quality, even if it's something small.
Just as I have been helped by my seniors so far, I believe my knowledge will be useful to someone.

Conclusion

Recently, I've had many opportunities to work with new technologies, so I've been exposed to a lot of information.
Every time, I am helped by the insights of my seniors.

I started writing this with those thoughts in mind.
I hope that as many creators as possible can work in a meaningful development environment.