User:PWeclewski: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 63: Line 63:
* Please describe how useful criticism looks from your point of view as committing student.<br/>Useful criticism is very important but people who give it should know how to do this. Its directness and strength should be considered and adapted to situation and relations between people.
* Please describe how useful criticism looks from your point of view as committing student.<br/>Useful criticism is very important but people who give it should know how to do this. Its directness and strength should be considered and adapted to situation and relations between people.
* 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?<br/>I really like to know how code should work, what the inputs and outputs are. Until I start coding I try to draw some kind of data flow chart to understand how data should flow and what is a role of code parts. When I discuss this step I think what methods I should use, how pass data, which elements should be separated. Every of these steps needs approval and cast aside doubts. If I have a possibility to discuss this with somebody with grader experience, it is great.
** Do you like to discuss changes intensively and not start coding until you know what you want to do?<br/>I really like to know how code should work, what the inputs and outputs are. Until I start coding I try to draw some kind of data flow chart to understand how data should flow and what is a role of code parts. When I discuss this step I think what methods I should use, how pass data, which elements should be separated. Each of these steps needs approval and cast aside doubts. If I have a possibility to discuss this with somebody with grader experience, it is great.
** 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?


17

edits

Navigation menu