2013|10|11|12|
2014|01|02|03|04|05|06|07|08|09|10|11|12|
2015|01|02|03|04|05|06|07|08|09|10|11|12|
2016|01|02|03|04|05|06|07|08|09|10|11|12|
2017|01|02|03|04|05|06|07|08|09|10|11|12|
2018|01|02|03|04|05|06|07|08|09|10|11|12|
2019|01|02|03|04|05|06|07|08|09|10|11|12|
2020|01|02|03|04|05|06|07|08|09|10|11|12|
2021|01|02|03|04|05|06|07|08|09|10|11|12|
2022|01|02|03|04|05|06|07|08|09|10|11|12|
2023|01|02|03|04|05|06|07|08|09|10|11|12|
2024|01|02|03|04|05|

2019-02-25 "Is there a problem with global variables ?" [長年日記]

Every year, at this time, I have to code (programming) as if I were driven.

Recently, I have been staring at the display for about 10 hours every day (including weekends).

However, my code is not for a product development ("product program"). They are mostly used as one that verifies the hypothesis of your own system ("verification program").

The verification program, in many cases,

- is not developed by a multi-player team,

- is used by myself,

- in many cases, nobody will reuse the past code

Especially, from the viewpoint of "reuse", not "reuse of past code" but only "past memories of my code" is reliable.

It is a rare case to reuse my code by another red person.

So, now I am making code with "writing priority", "time priority", and "confirmation priority".

"Three days a day over 1000 steps", is normal for me.

-----

So, the backwardness of that "cumbersome code" makes me write many comments in my codes.

It is fun to watch those "excuses comments".

"Is there a problem with global variables?"

"Let's stop "anything subroutine""

"Troublesome searching for argument types is wasting time"

"In the main routine, making a loop makes is easier to debug"

"Since memory is abundant, it is no problem to secure a sufficiently large area statically"

There were many people saying "I want to use the code", but there was never actually a request to send a "code"

-----

It is fun to watch past of (and the current) my driven work,