98
edits
Line 148: | Line 148: | ||
== S: Self-assessment == | == S: Self-assessment == | ||
* Please describe how useful criticism looks from your point of view as committing student. | * '''Please describe how useful criticism looks from your point of view as committing student.''' | ||
:- I always appreciate constructive criticism. | :- I always appreciate constructive criticism. | ||
* How autonomous are you when developing: | * '''How autonomous are you when developing:''' | ||
** Do you like to discuss changes intensively and not start coding until you know what you want to do? | ** Do you like to discuss changes intensively and not start coding until you know what you want to do? | ||
** 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? | ** 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? | ||
::- That depends on the task. | ::- That depends on the task. I'd say that, if the outcome is defined or at least predictable with some decent accuracy, I'll discuss the problem statement and immediately get down to code. Otherwise, I'll code up a '''small model''' first to see if the approach really would work and proceed thereafter. | ||
== Y: Your task == | == Y: Your task == |
edits