21
edits
Line 89: | Line 89: | ||
:I always do a search on the internet or in books in the great library at my university. If I'm not successful, I seek to talk to someone in the community, by email or IRC. | :I always do a search on the internet or in books in the great library at my university. If I'm not successful, I seek to talk to someone in the community, by email or IRC. | ||
:* '''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?''' | |||
::I think it largely depends on the purpose of development, some jobs require more time for research and planning. However, I believe that in general the best way is to use a few days to talk intensely about the tasks and perform some working sketches, after that, I think it is interesting to encode some examples and keep adjusting them over time, I think it is more attractive for work as the GSOC! | |||
== Y: Your task == | == Y: Your task == |
edits