LYH

User:LYH (edit)

Revision as of 04:48, 3 May 2013

242 bytes removed , 3 May 2013

→‎GSoC 2013 - Application

LYH

47

edits

@@ Line 67: / Line 67: @@
 * '''Did you ever hear about Octave before?'''
 ** '''If so, when and where? How far have you been involved already?'''
-::Yes, I have known the Octave four years ago, at my university, in Brazil.
+::Yes, I do noticed Octave when I use property Matlab in my school last year.
+** '''What was the first question concerning Octave you could not find an answer to rather quickly?'''
+::The build process. I do not know that I need run ./bootstrap first until I read etc/HACKING. Because I usually run autoregen and configure directly.
 == P: Prerequisites ==
 * '''Please state the operating system you work with.'''
 ** '''If you have access to more than one, please state them and the conditions under which you are granted this access.'''
-::I have a notebook with Ubuntu and Windows 7. Eventually can I use a MacBook of a lab at my university, to perform some tests (if necessary).
+::Usually Linux. But I could work with Mac OSX and Windows if I need to test on variant platform.
 * '''Please estimate an average time per day you will be able to ''(if separated)'' access'''
 ** '''an internet connection'''
+::Disconnect when I sleep.
 ** '''a computer'''
+::All the time.
 ** '''a computer with your progressing work on'''
-::I am all the time with my laptop, I just disconnect the internet when I sleep...
+::More than 40 hours per week.
-::I understand the importance of dedication to the project, so I can guarantee that I will be absolutely free for GSoC and that I can accomplish much more than 40 hours per week.
 * '''Please describe the degree up to which you can install new software on computers you have access to.'''
-:I can install any software on the computers mentioned!
+:I have my own macbook. So I could install all softwares if I need.
 == S: Self-assessment ==
 * '''Please describe how useful criticism looks from your point of view as committing student.'''
-:Criticisms are essential in group work, because people are able to share knowledge, and can bring improvements to the development process.
+:Criticisms are essential in group work, because people are able to share knowledge, and can bring improvements to the development process. //
 * '''How autonomous are you when developing?'''
-: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 like to dicuss direction first and reinterpret in my words. Then ask others whether I understand well. And I would start to write small program to prove my concept. If the work doesn’t match the goal, I would thrown it away early rather then coding for thousands of code and hard to debug.
-::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 ==