A few weeks ago I was an instructor for a internship student who came to work.

Since he was a competent student, I had enough of all the materials he needed, and asked him for what I wanted to make.

The "a little unusual request" from me is

- Leave a short test program after confirming operation

-----

For me, the most difficult program to read is that

the list is long

a lot of meaningless variables are used

and

Neatly organized

"A concise and beautifully organized program" is "the worst program” for me as a developer.

------

I want sample programs to be within 20 lines at the maximum.

If possible, I'd like you to hard-code real numbers rather than variables.

I'd like you to leave the inefficient (unoptimized) loop intact.

Why do I want that?

I can read several knowledges from source codes of the sample program

The source codes make me clear that how to use argument of library's function, structures of object and orders of data references.

There is no program that allows programmers to study as much as a “straying course” program during program creation.

-----

When I use the command line, I don't need an explanation of the argument contents.

If there is an actual example (sample) of how to use the command line that actually works, I guess how to use it from that sample, and that is faster to understand the command..

(This story is the same as the "math" of mathematics and the "manual" of home appliances that I have repeated so far)

So I asked the intern student to leave a short test program without erasing it.

For me it is a treasure mountain.

(To be continued)