Difference between revisions of "User:Hcurtis0010/GSoC2014/logs"
Hcurtis0010 (talk | contribs) |
Hcurtis0010 (talk | contribs) |
||
| Line 4: | Line 4: | ||
I re-read the Hacking file, and that led me to do research on binaries, regression testing, and other topics. Also, I had a good IRC conversation with my mentor, Sean Morrison, about how best to interact with one another and what I will need to do to succeed during GSoC. | I re-read the Hacking file, and that led me to do research on binaries, regression testing, and other topics. Also, I had a good IRC conversation with my mentor, Sean Morrison, about how best to interact with one another and what I will need to do to succeed during GSoC. | ||
| + | |||
| + | |||
| + | '''Tuesday, May 20''' | ||
| + | |||
| + | Sean and I had an enlightening IRC conversation in which he pointed out the danger of relying too much on examples when dealing with code. | ||
| + | |||
| + | Afterward, I wrote some programs involving arrays. I ran into a problem with one of them, and I did some research as I attempted to solve it. The topics I investigated included dynamic allocation, vectors, and heaps. Sean asked me to create the programs in order to learn more about dynamic and stack memory and be able to apply that knowledge to future GSoC activities. | ||
Revision as of 03:24, 21 May 2014
Week 1
Monday, May 19
I re-read the Hacking file, and that led me to do research on binaries, regression testing, and other topics. Also, I had a good IRC conversation with my mentor, Sean Morrison, about how best to interact with one another and what I will need to do to succeed during GSoC.
Tuesday, May 20
Sean and I had an enlightening IRC conversation in which he pointed out the danger of relying too much on examples when dealing with code.
Afterward, I wrote some programs involving arrays. I ran into a problem with one of them, and I did some research as I attempted to solve it. The topics I investigated included dynamic allocation, vectors, and heaps. Sean asked me to create the programs in order to learn more about dynamic and stack memory and be able to apply that knowledge to future GSoC activities.
