98
edits
User:Sudeepam: Difference between revisions
Jump to navigation
Jump to search
→S: Self-assessment
| Line 158: | Line 158: | ||
== 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. | |||
* 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. Say I am working on something like a neural network. Neural networks are sometimes unpredictable so I believe that it is best to try out a small model first to 'see how it turns out'. However, if say I am working on a problem like a dictionary search through a trie, then I know that this would work out and so I'll intensively discuss the requirements of the project and then code accordingly. So I'd say that, if the concept is defined or at least predictable with some assurance, I'll discuss the problem and immediately get down to code. Otherwise, I'll code up a small model first to see if my approach really would work out and proceed thereafter. | |||
== Y: Your task == | == Y: Your task == | ||