Question 0: What is my code name?
Mangrove
Question 1: What is my goal for programming assignments?
To appropriately complete and turn in the assignment before the assigned due date, with a decent if not perfect score.
Question 2: What are my strengths?
Late hours are available. I have a decent program knowledge and a quick ability to grasp concepts when doing tactile work.
Question 3: What are my weaknesses?
Less likely to work during the day, and I live a busy life so having to move and deal with an unknown issue is possible some nights.
Question 4: I like to a) get tasks done early. b) procrastinate. c) set my schedule based on weekly demands. d) be flexible about assignment deadlines.
C) I shoot to finish all assignments by there due dates, often before due dates. However I am aware certain assignments are worth more, and attempt to put more time and work into them then average.
Question 5: What do I like to do for fun?
I do a wide variety of things for fun. I tend to enjoy video games, reading, and parties.
Question 6: Describe your communication style.
Electronic communication is often easiest, however I am normally capable and willing to meet up and knock something out in person. I do operate on a prepaid phone so texting at times is a bit hesitant, I don't like using excess texts. I can normally work with or around most communication styles. I do think Google Drive works as one of the better ways to send programs and to handle discussions.
Question 7: Describe the characteristics of a good partner.
A good partner should be able to handle delegated code on time with appropriate effort. A good partner should create code with sharing and readability in mind, e.g. using appropriate variable names. A good partner should communicate well throughout the partnership. A good partner should also be a semi-decent person, working together will involve continued cooperation, decency is therefore valued, including humor. Simply, a good partner would get their work done on time with decent skill.
Question 8: Describe the characteristics of a bad partner.
A bad partner is lazy, uncommitted to the project while working to undermine or fustrate his partner. A bad partner has no issue leaving one partner to do anything, is disruptive, rude, and otherwise challenging towards the project as a whole. A bad partner takes advantage of the other, or acts very passive aggresive in regards to issues.
Question 9: My best open times to meet with a CS 200 parter (including recitation times) are:
I have recitation at 11am on fridays. Other than that I am capable of meeting most afternoons, however thursday nights, friday nights, and saturday nights, can be problematic for meeting in person. Electronic communication should still be possible. Although capable of working in the morning it is not my desired time in any way.
Question 10: Any additional comments should be made here.
I'm looking forward to working with a decent partner. Delays, hazards, issues, errors and other problems can be handled together with humor and hard work. Humor and cooperation will be a part of the partnership. A decent partner can be more important than the best programmer.
P.S. I may work on assignments very late into the night. I appreciate the silence and calmness of such a time. I am fully accepting some people actually like sleep. As long as were both pulling our weight things should be very acceptable, despite timing. (This paragraph does not mean I procrastinate until 3 a.m. It means I'm willing to spend long hours working.)