Editing User:Ivanilos

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
== A: An introduction ==
== A: An introduction ==
* Please describe yourself in three sentences, one of them regarding your current studies.
** Which languages do you speak?
** What's your overall background? ''The general field you work in or are studying, e.g. computer science, physics, artificial intelligence, control theory...''
* Why do you want to participate in the Google Summer of Code? What do you hope to gain by doing so?
** Please also describe your previous experience with the GSoC, if any. ''Includes any community-bonding, mentor experience or application, not necessarily accepted. We use this subquestion to identify which students are unfamiliar with how the program goes, providing further support. It has no negative impact on your rating!''
* Why are you choosing Octave?


* I am a Brazilian student at the State University of Campinas, I've graduated in the beginning of March 2017 and decided to go back to university to take some courses I am interested in and possibly start pursuing a master's degree. My hobbies are playing guitar, chess, tennis, participating in some algorithmic programming competitions and watching video-game speedruns.
* I am a Brazilian student at the State University of Campinas, I've graduated in the beginning of March 2017 and decided to go back to university to take some courses I am interested in and possibly start pursuing a master's degree. My hobbies are playing guitar, chess, tennis, participating in some algorithmic programming competitions and watching video-game speedruns.
Line 10: Line 16:
** This is my first time applying to GSoC.
** This is my first time applying to GSoC.


* I've chosen Octave as the project seems to match my interests and knowledge.
* I've chosen Octave as I the suggested ideas seem to match my interests and knowledge. I've
 


== C: Contact ==
== C: Contact ==
 
* Please state the (unique and identical where possible) nick you use on IRC and any other communication channel related to Octave. ''We really want unique nicks. You might want to bold it.''
* My nick is '''ivanilos'''.
* Which time zone do you live in? Will that change over GSoC duration? ''Perhaps DST adjustment or a relocation. Note that both UTC and GMT are not aware of daylight saving time! Please state UTC+x or -x.''
 
* Please state the timeframe (in UTC+0) when you feel most comfortable working during GSoC. Where are your time buffers? ''Example: I usually code around 9.00 to 18.00 and could also try to start earlier (~7.00) for few days ;-)''
* The timezone I live in is -3.00 GMT and this will not change during the GSoC period.
 
* I would rather work during the day (possibly some time between 8.00 and 17.00) but I can be flexible regarding to work timeframe as long as it isn't anytime from 23.00 to 7.00 (with seldom exceptions).


== E: Coding experience ==
== E: Coding experience ==
Line 27: Line 31:
* 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.
* Please state the commits and patches you already contributed to Octave. ''This question (one of the most important parts by the way) is the only part of your application our wiki admins will edit for you even after the application deadline. Code sometimes speaks louder than many words do.''
* Please state the commits and patches you already contributed to Octave. ''This question (one of the most important parts by the way) is the only part of your application our wiki admins will edit for you even after the application deadline. Code sometimes speaks louder than many words do.''
* My main experience programming in C++ is in competitive programming. I've participated in several competitions and websites such as SPOJ, UVA, hackerrank, hackerearth, codeforces, topcoder, livearchive online judge, ACM-ICPC, Google Code Jam, Facebook Hacker Cup, Yandex Algorithm, IPSC (internet problem solving contest)... I've also used C++ to work on my Bachelor final project which is called "Voce Fiscal" (a public audit of elections in Brazil https://github.com/vocefiscal/vocefiscal-qrcode). I've used Octave in the beginning of the coursera course on machine learning (in 2016) but I stopped the course after winter break was over. I have no experience in using Matlab, OpenGL or Qt.
* I don't have a lot of experience with other programming languages but I've done college projects in Java, I studied a bit of Python on my own and took some classes of introduction to programming and algorithms in Python. I've also won this competition https://realpython.com/blog/python/python-programming-contest-first-to-five/ using Python. Yet, in a pair project me and my partner had to integrate Python with PHP to grab some data about musicians from wikipedia in a database course project. I took a non-mandatory course in university where I had to code in Lisp and Prolog and made a project for a game which is based in chess (I talk about the game below). Finally, in a course about logic circuits I had to use VHDL but I didn't have a good experience with it.
* TODO experience team
* TODO biggest project
* TODO commits to Octave
 


== F: Feeling fine ==
== F: Feeling fine ==
Please note that all contributions to Octave may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Octave:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)