[saeranv]

I find it very surprising that he suggests writing the introduction at the end of the paper. He doesn't explicitly mention the abstract, so I'm assuming the introduction includes the abstract of the paper. If that's true, I find it impossible to write any paper without first working out a fairly fleshed out abstract. It usually takes about 50% of my time to just write my abstract.

The way I structure my prototypes, I have to have a sense of the existing state of the art, which I then leverage to propose my hypothesis. I do a version of this for programming as well, I try and identify state of the art methods in the field, and use that to guide my implementation.

[Ar-Curunir]

It’s much easier to write an abstract and intro once the rest of the paper is concrete and correct; it tells you what the strengths and important points of your paper are. You don’t necessarily know these until you’ve done the hard work in the rest of the paper