6
edits
Juanmanpr
Joined 19 April 2013
→P: Prerequisites
| (One intermediate revision by the same user not shown) | |||
| Line 61: | Line 61: | ||
== P: Prerequisites == | == P: Prerequisites == | ||
* Please state the operating system you work with. Different Linux based distros such as Ubuntu and OpenSUSE. Windows at the University. | * Please state the operating system you work with. ''Different Linux based distros such as Ubuntu and OpenSUSE. Windows at the University.'' | ||
** If you have access to more than one, please state them and the conditions under which you are granted this access. | ** If you have access to more than one, please state them and the conditions under which you are granted this access. | ||
* Please estimate an average time per day you will be able to ''(if separated)'' access | * Please estimate an average time per day you will be able to ''(if separated)'' access | ||
** an internet connection 24 hrs | ** an internet connection ''24 hrs'' | ||
** a computer 24 hrs | ** a computer ''24 hrs'' | ||
** a computer with your progressing work on 24 hrs | ** a computer with your progressing work on ''24 hrs'' | ||
* Please describe the degree up to which you can install new software on computers you have access to. | * Please describe the degree up to which you can install new software on computers you have access to. ''Total'' | ||
== 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. ''Criticism is an important tool to improve the work is being done.'' | ||
* How autonomous are you when developing? '' | * How autonomous are you when developing? ''I am pretty autonomous, and I am used to focus on a goal and do whatever is on my hand before asking for help. But when assistant or help become necessary, I don't hesitate to ask for it.'' | ||
** 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? ''Before coding I need at least a clear goal to reach. So I first divide my tasks in goals. Depending on the work I have to do, I can set this goals individually, or discussing with the team in charge.'' | ||
** 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? '' Actually, yes. If I have a particular problem which I think I can solve, I write the code and test it. I don't consider doing this is actually throwing away work. Testing/Validating and Correcting is usually the normal work cycle of a programmer'' | ||
== Y: Your task == | == Y: Your task == | ||