7
edits
Darrazo
Joined 26 April 2013
no edit summary
(Created page with "= Public application template = == A: An introduction == * Please describe yourself in three sentences, one of them regarding your current studies. I am a student at a Frenc...") |
No edit summary |
||
| Line 30: | Line 30: | ||
I never had a professional experience in a development team. Although, I worked various University projects in teams ( three to five people) | I never had a professional experience in a development team. Although, I worked various University projects in teams ( three to five people) | ||
* Please describe the biggest project you have written code for and what you learned by doing so. Also describe your role in that project over time. | * Please describe the biggest project you have written code for and what you learned by doing so. Also describe your role in that project over time. | ||
My biggest project was in C. We were three and the subject was simulation of a MIPS CPU. First we | My biggest project was in C. We were three and the subject was simulation of a MIPS CPU. First we identified the needs, then we agreed on an implementation, finally we realised several tests to validate our project. I participated in all of the tasks, starting from suggesting an implementon to the validation stage. | ||
== F: Feeling fine == | == F: Feeling fine == | ||
* Please describe (in short) your experience with the following tools: | * Please describe (in short) your experience with the following tools: | ||
| Line 54: | Line 54: | ||
* 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 help us build a better tool. Criticism help us finding the Achilles ' heel of our programs and try to fix it. | Criticism help us build a better tool. Criticism help us finding the Achilles ' heel of our programs and try to fix it. | ||
* 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? We must discuss a lot before starting to code. Because a good idea may appear in the discussion and we are able to see the different problems that we could possibly face later on. Nevertheless, sometimes we have to begin to code to see it through. So, my conclusion, it is that dicussions before coding are mandatory but they don't have to last longer than it's should take. | If I understand the problem I can be totally autonomous. else, I rather prefer working on a specific task that contribute may not reflect all the tasks but help me understand one part of the whole project. | ||
** 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 it happens sometimes. Particularly it | ** Do you like to discuss changes intensively and not start coding until you know what you want to do? | ||
We must discuss a lot before starting to code. Because a good idea may appear in the discussion and we are able to see the different problems that we could possibly face later on. Nevertheless, sometimes we have to begin to code to see it through. So, my conclusion, it is that dicussions before coding are mandatory but they don't have to last longer than it's should take. | |||
** 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 it happens sometimes. Particularly it happens when discussion are not deep enough. Even so, seeing how it turns out helps a lot sometimes. | |||
== Y: Your task == | == Y: Your task == | ||
* Did you select a task from our list of proposals and ideas? | * Did you select a task from our list of proposals and ideas? | ||
Yes i choose implementing the incomplete sparse factorization project | Yes i choose implementing the incomplete sparse factorization project | ||
I | I want in particular to implement the CCS version of ichol for Octave using m-scripting and eventually ilu if it is not already been done. I can also try the second option of interfacing Octave to ITSOL. Indeed, I think here the use of C++ and Qt is needed. | ||
* Please provide a rough estimated timeline for your work on the task. I | * Please provide a rough estimated timeline for your work on the task. | ||
I will identify the needs of the project during 1 to 2 weeks, afetr that during one week I will validate my first choice of implementation, I will also validate my functions and methods all the way long. During the last three or four weekd, I won't add any functionnalities, I will only validate and documentate my project. | |||