45
edits
Template:Student application template public: Difference between revisions
Template:Student application template public (edit)
Revision as of 06:30, 28 March 2017
, 28 March 2017→S: Self-assessment
| Line 88: | Line 88: | ||
== 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'm open to all useful and constructive criticism. It helps me self-evaluate myself and it is pivotal for a good product development. | |||
* How autonomous are you when developing: | * How autonomous are you when developing: | ||
** I tend to code based on my approach to the problem, I try to figure out the bugs or inefficiencies(If any) for a while. If I don't find any solution then I don't hesitate to ask for a help. I also ask for suggestions after completing my code. | |||
** 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? | ||
*** Yes, I prefer to discuss the approach intensively before coding. I think it is more suitable to write bug-free code at once and it also eliminates the some of the inefficiencies involved. | |||
** 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? | ||
Yes, I like to code a proof of concept. I'd take the risk of having work thrown away, at least it'd tell us whether the risk was worth taking or not. | |||
== Y: Your task == | == Y: Your task == | ||