Jump to navigation Jump to search
953 bytes added ,  06:05, 18 March 2017
no edit summary
* ''Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers?''
Being sincere, since I am currently on a PhD program my work load is very unstable. However, I plan to work on GSoC from 07:00 to 10:00 and 17:00 to 21:00 during the weekdays. Anyway, I am very flexible and surely the excitement of working on this will lead to many more hours even on weekends. I've have been working in a private company and at the same time carrying my Master studies through a year and a half so I am quite good at managing my time.
== E: Coding experience ==
I can access to an internet connection the whole day, not only on a computer but also on my smartphone. I expend about 10 hours per day in front of my computers and they are all synchronised so I can access my progressing work any time.
* ''Please describe the degree to which you can install new software on computers you have access to.'' I can install anything on them.
== S: Self-assessment ==
* ''Please describe how useful criticism looks from your point of view as committing student.'' Constructive criticism is a key factor for improving one's skills and for creating better things. Someone told me once that if no one says nothing about your work that can only mean two things: it was perfectly done and no one knows how to improve it, or it is so regular that it does not seem useful or interesting to others - and the most common case is the second one. In addition, if you are not self-critic with your own work, that is a signal of being conformist. I do not like being conformist because that stops you from growing and learning. * ''How autonomous are you when developing:'' ** Do you like I am very used to discuss changes intensively working autonomously: in my past job I was in charge of a whole project myself and not start coding until you know what you want to do?** Do you as a researcher I am very proactive. I like to think and design everything as perfectly as I can before writing code because I find this a proof of concept to 'see good practice for saving time in the long term. However, I can understand that sometimes it is quite useful writing some toy prototypes that can evaluate your ideas. This is frequent in research when you do not know how something will turn out and you test it turns out', modifying using tools like Octave that and taking support perfectly a fast prototyping process. If the risk of having work thrown away results are not satisfying they are never a failure if it doesn't match what the project or original proponent had in mind?you learn from them!
== Y: Your task ==


Navigation menu