| EZEKIEL M. CLARK | |
| Software Engineer | |
| clarkzeke@gmail.com | |
| (202) 669-6940 | |
| https://github.com/Yetidancer | |
| https://www.linkedin.com/in/ezekiel-clark/ | |
| To whom it may concern, | |
| Please accept this letter in conjunction with my resume as my application for Full-Stack Engineer. I heard about this position from an employee of yours, Taite Sandefer. This opportunity is ideal for me as it exists at the intersection of my strengths: efficiency, sustainable solutions, and full-stack programming. |
| Re-DTR: | |
| We feel productive so far, despite the apparent slow going. We are spending a good bit of time on research, but I don’t think we are doing badly as far as pace. | |
| Kathleen: | |
| I think we have done well assigning tasks and dividing up responsibilities. Even if it feels slow I think we have made a lot of progress from where we started. | |
| Danny: | |
| I don’t think anything has gone poorly, but it feels like we are treading water with regards to progress. | |
| Kathleen: |
As we've discussed, meeting people, forming relationships, and having conversations are the key pieces to getting your foot in the door at any company. It's important to be proactive in your approach to outreach and networking, so it's necessary to make a plan for what you'll try to further your networking.
Identify a contact you will reach out to by the end of this module. This could be a mentor, alum, or anyone from your current network. Describe:
My contact is Justine Troyke. I want to connect with her because she is a Turing alum that has been at her first job for a little while and I am curious to see what the job search and hiring process was like for her.
| 1. What have you learned about the use of agile vs. waterfall in software projects? | |
| I learned that waterfall is a more popular and perhaps easier implementation because it allows responsibilities to be separated and steps to remain discrete. | |
| It does however let problems persist for longer and potentially cause problems down the line. Agile is the fix for this, as it allows a project to constantly self-assess and adjust to the needs of the group. | |
| 2. How did you and your group approach project management in this project (what tools did you use, how did you hold each other accountable, etc.)? | |
| We used trello to assign responsibilities and constant pull requests to make sure that issues were not being compounded on by long sets of code that built upon itself. We held each other accountable by constant code review that made sure we were sticking to a plan and implementing it correctly. On top of this we reassessed our goals a few separate times throughout the project so that we were on the same page about our prio |
Zeke Clark and Elom Amouzou
Zeke wants to work on his teamwork skills: I think I work best individually, so I think working in close conjuction with my partner will be a continuous project in adjusting to account for expectations and strengths. Elom expressed that he wanted to work on coding as a team We want to work on coding as a team. Teamwork skills will be vital to this and be an ongoing assessment of where we are at in terms of getting things done on time, communicating well, solving problems, etc. As far as succeeding as a team, we want to meet the 4s of the rubric as close as possible. This will also be our measurement of success. Past that, we think if we can make a schedule, stick to it, and resolve any conflicts along the way, from schedule to working differences, then I will be happy with our results, which are as much intangible as they are measurable.