38
edits
Atuljangra
Joined 27 March 2012
→S: Self-assessment
Atuljangra (talk | contribs) |
Atuljangra (talk | contribs) |
||
| Line 80: | Line 80: | ||
== 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 take criticism in a healthy way only if it is delivered in a healthy way. It's like if you say "It is wrong", then I would ask for a reason and a better solution, or at least a motivation to do so.If you are saying "This is simply wrong" without any reason that I am afraid that I would hesitate in making any changes. In short, I can take criticism in a very healthy way if that criticism leads to a better result. | |||
* How autonomous are you when developing? ''If you answer both subquestions with "Yes, definitely", we are a tad confused. ;-)'' | * How autonomous are you when developing? ''If you answer both subquestions with "Yes, definitely", we are a tad confused. ;-)'' | ||
** 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? | ||
:I like to discuss changes and try to understand them before starting of code. But I believe that sometimes things are more clear if we start coding them. So I believe that we should discuss the change and try to understand it and start making our hands dirty by coding them away instead of discussing the changes ''intensively''. | |||
** 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, This is the thing that I was talking about. I believe in getting my hands dirty in code ;), and yes one should take the risk of throwing the code away if it does not fit into our project. | |||
== Y: Your task == | == Y: Your task == | ||