23
edits
CodingCoffee
Joined 29 March 2017
→S: Self-assessment
CodingCoffee (talk | contribs) |
CodingCoffee (talk | contribs) |
||
| Line 87: | Line 87: | ||
== 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 constructive criticism. It'll helps me improve myself and also prove productive for the product being developed. | |||
* How autonomous are you when developing: | * How autonomous are you when developing: | ||
** I initially try to come up with a solution of my own and implement it, and then test it for bugs/errors. However if after multiple attempts I'm not able to get through the problem at hand, I tend to spend time on StackOverflow for help. | |||
** 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 prefer thinking up a basic flowchart for the code and start implementing it. And then work on the individual parts of the flowchart, rather than discussing intensively initially and then writing the entire code. | |||
** 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, since I believe one learns a lot more while failing at a particular thing! | |||
== Y: Your task == | == Y: Your task == | ||