"Why is Ebata still coding?" I think there are many people who think that.

For the past few years, I have had the program created by an outsourcer.

I've had all the items delivered to me, including the source code, however, I came to realize

"I have not been able to reuse (modify) their source code at all"

-----

To be clear, "programs written by others" are, to put it bluntly, "spellbinding.

Not only programming languages that I am not familiar with, but also even programming languages that I am familiar with, are not

- Libraries are different,

- Program development environments are different,

- Versions (specifications) of the programming language are differnt,

In, addition, the crucial thing is that

- Coding approaches (philosophy) are different.

This point is hopelessly "spellbinding".

Once, my mentor, "Erukan" said,

"Reading someone else's program is like looking into someone else's head. it's offensive and even vomit-inducing"

I think that this is a great quote.

-----

Pain-free programming is programming done by myself alone from scratch.

However, this is a 'luxury' of such programming, given the speed of digital services these days.

I also have to admit that it is 'unproductive'.

If the programming is "luxury" and "unproductive", where can I get resources from?

The only thing I can use is "weekends" and "sleeping time".

-----

In the past, I could usually talk about the programming on the 'weekends' and on less sleep.

These days, it seems to be a 'compliance issue' to publicly state such a thing in the workplace, etc.

And I agree with this opinion.

This kind of talk is, after all, "power harassment," and this kind of bragging is infuriating to listen to.

So, from now on, I think it will become the norm that 'the work I want to do (programs I want to try, etc.) will be prepared "under the table".

-----

By the way, this "under the table" is not limited to programming. This goes for work in general.

I've always said.

"The work you want to do, do it alone, without making it public"

"Keep my eyes open for any opportunity to make it public"

These are important.

If you disclose your ideas to the organization in an unfinished state and at an inappropriate time, 'your idea will surely be crushed' -- logistically.

It is no exaggeration to say that this is an "axiom of organization".

For example, I have a service/product that I kept my idea hidden for three years, and after two years of discreetly disclosing it little by little, I finally got it to be recognized within the organization.

Now let's return to the main subject

-----

Why is Ebata still coding?" A lot can be said about this, but in a nutshell

"Because, it is easy"