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|

2017-05-17 "Please leave your lame, unmade and short code under the construction" [長年日記]

(Continuation from yesterday)

I ask the engineers to open a part of source code, that realizes a part of whole function. In addition, the code might be

lame, unmade

and

shorter (less than 100 steps, if ever)

I really want to read such incomplete codes.

Those codes are, in many case, fundamental function of the algorithm.

For me, the code is better for me than complete and completed source code by far.

A lame and unmade code is helpful to understand a basic structure of data, and,

A shorter code is helpful to understand the basic algorithm.

Especially, about a code that implements realtime processing function, the old code, before implementing the process, is extraordinarily fine, for me.

If the realtime process includes, the code traces must be difficult.

-----

Many engineers, who have opened their source code with good-will, love to make codes,

however,

they don't like write a document(like instruction manual,practical guide)

If they say "source code itself, is a manual" to me, I don't argue against them.

Because it is a just argument absolutely.

Above all, I also open my source code to the Internet, but I have not made the manual since now.

-----

So I don't say "Please write "readme.txt" down". but I want to say to them

"Please leave your lame, unmade and short code under the construction"

with greatest courtesy.