The scary thing about coding is that the correlation between "results" and "effort or time" is very small.

For example, it is possible to create a program of about 200 lines in 30 minutes, or to be "stuck" for 10 hours to a week on a program of two lines.

"I'll finish the JSON parser in three hours"

It was only this time yesterday that I started to do it.

I kept searching the net for sample code for a program to parse an array type format without tags. And now 24 hours (including naps) have passed while dealing with dozens of errors.

I am completely "stuck".

"Oh, God, no"

Reluctantly, I was prepared to post my question on a question site.

I wish I could post sooner rather than get into this, but of course, in order to post, I have to describe the situation in exact detail -- it's a hassle. Besides, I don't know if I'll get an answer.

When I write a short program for that purpose, somehow the program "works" correctly.

'No, no, no, I tried this code several times last night, didn't I?' I think, but it's working, so I can't help it.

-----

The program is only justified by the things that work.

A program that does not work, no matter how beautiful, readable, or grammatically correct the code may be -- it is all "garbage".

Codig is a world where "effort and time" are not taken into consideration.

-----

Lately, my GW, summer vacation, and year-end vacations have been spent almost entirely in coding.

Because, I want to survive as an engineer.