"There is a million-fold difference between "easy" as described by those who made it and "easy" as faced by those who use it."

I have not noticed it for a long time, but recently I realized it.

----

Recently, I have been doing a lot of work modifying systems created by others, and I have been suffering from this discrepancy in perception of "easy."

The programs and systems I have created are "easy."

It's like, 'What the heck do you not understand about this program?

However, from the point of view of the "modifiers" of my program, it is not "easy" but rather, quite frankly, a "spell" and a "cipher code."

To put it bluntly, it is so "difficult" that it would probably be faster to make it yourself from scratch.

This is also true when you ask someone (including software subcontractors) to make modifications based on a program you have created.

It is better not to use 'easy' easily.

The development environment and coding rules that others have tuned up (I don't know about others) are, to me,

the 'development environment from hell.'

-----

This story applies not only to "others" but also to "myself."

The reason I am writing morbidly technical notes on this site is,

"What was 'easy' for me in the past turns into 'hell' over time."

I understand this better than anyone else.

For those visiting my site, "SQL queries" and "Go language" are unimportant.

But for me, whether or not to keep such notes is really a matter of life and death.