*** I like to think about the code intensively before starting. However, an overview is acceptable as far as discussion is concerned.
** Do you like to code a proof of concept to 'see how it turns out', modifying that and taking the risk of having work thrown away if it doesn't match what the project or original proponent had in mind?
*** I have rarely coded on projects where the only options are accepted code or "thrown out" code. Usually, I prefer
cucles of coding and feedback, as the code starts resembling what the original proponent has in mind. If that is impossible, it depends on the length of the code. If it is a comprehensive project, or one where the execution time is measurable in days, I prefer a proof of concept. Else, I prefer to start working right away.
== Y: Your task ==