ITP-Jan | Structuring and testing data | Roman Sanaye

[RomanSanaye]

---

1. Codewars Progress Checker

All katas completed for Sprint 1, 2, and 3:
View Progress Checker

---

2. Completed Pull Requests

• Sprint 1 Coursework Exercises: PR link
• Sprint 2 Coursework Exercises: PR link
• Sprint 3 “Implement and Rewrite Tests” Coursework Exercises: PR link (status: Needs Review)
• Sprint 3 “Practice TDD” Coursework Exercises: PR link (status: Needs Review)

---

3. Written Email for an Internship

View Email

---

4. Online Study Session Screenshot

---

5. Demo Session Screenshot

[cjyuan]

• PRs not yet completed
  • Sprint 3 "Implement and Rewrite Tests" Coursework Exercises
  • Sprint 3 "Practice TDD" Coursework Exercises

[RomanSanaye]

Good morning, Thank you for your message. I would like to clarify that I have already completed the pull requests for Sprint 3 (“Implement and Rewrite Tests” and “Practice TDD” coursework exercises), and they have also been reviewed. However, they do not appear to be marked as completed yet. Could you please confirm if anything further is required from my side, or if they can now be marked as completed? Thank you for your time and support. Kind regards, Roman Sanaye

…

On Wed, Mar 18, 2026 at 5:28 AM CJ Yuan ***@***.***> wrote: *cjyuan* left a comment (RomanSanaye/My-Coursework-Planner#85) <#85 (comment)> - PRs not yet completed - Sprint 3 "Implement and Rewrite Tests" Coursework Exercises - Sprint 3 "Practice TDD" Coursework Exercises — Reply to this email directly, view it on GitHub <#85 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BSZT7H2VWEH7H7OUCZBLXGL4RIXXJAVCNFSM6AAAAACWJRMOKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANZZHA2DINRWG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[cjyuan]

In CYF courses, the recommended way to inform the reviewer of your changes is to do both of the following:

• Reply to their feedback.
  • In the responses, clarify how each piece of feedback was addressed to demonstrate that you've carefully reviewed the suggestions.
    • You may find the suggestions in this PR Guide useful.
  • Your response may trigger a notification (depending on the reviewer's settings), helping ensure they’re aware of the updates you’ve made.
• Replace the "Reviewed" label by a "Needs review" label
  • Without this label, the reviewer would not know if your changes is ready to be reviewed.

In your "Implement functions and rewrite tests" PR, you should at least add the "Needs Review" label to the PR after you have made the change.

In your TDD PR, you didn't respond to my comments and you did not made any new commits based on those comments. If you have committed changes on your computer, you will need to push/sync them to GitHub for the commits to appear on your PR. After that, add a "Needs Review" label to the PR.

[RomanSanaye]

Hello, I have added the “Needs Review” label to both PRs. I have addressed all the feedback you provided, and usually after reviewing, the reviewer marks them as complete. I did not mark them as reviewed myself. Kind regards, Roman Sanaye

…

On Thu, Mar 19, 2026 at 10:42 AM CJ Yuan ***@***.***> wrote: *cjyuan* left a comment (RomanSanaye/My-Coursework-Planner#85) <#85 (comment)> In CYF courses, the recommended way to inform the reviewer of your changes is to do both of the following: - *Reply to their feedback.* - In the responses, clarify how each piece of feedback was addressed to demonstrate that you've carefully reviewed the suggestions. - You may find the suggestions in this PR Guide <https://programming.codeyourfuture.io/guides/reviewing/trainee-pr-guide/#addressing-reviewer-feedback> useful. - Your response may trigger a notification (depending on the reviewer's settings), helping ensure they’re aware of the updates you’ve made. - *Replace the "Reviewed" label by a "Needs review" label* - Without this label, the reviewer would not know if your changes is ready to be reviewed. In your "Implement functions and rewrite tests" PR <CodeYourFuture/Module-Structuring-and-Testing-Data#1119>, you should at least add the "Needs Review" label to the PR after you have made the change. In your TDD PR <CodeYourFuture/Module-Structuring-and-Testing-Data#1167>, you didn't respond to my comments and you did not made any new commits based on those comments. If you have committed changes on your computer, you will need to push/sync them to GitHub for the commits to appear on your PR. After that, add a "Needs Review" label to the PR. — Reply to this email directly, view it on GitHub <#85 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BSZT7H6I4SDYDNIWL265YMT4RPFIJAVCNFSM6AAAAACWJRMOKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBZGIZDGMBQGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[RomanSanaye]

Good afternoon, I have addressed the second PR on Sprint-3 of module Structuring and testing data. Thanks for your time and useful feedback. kind regards, Roman Sanaye

…

On Thu, Mar 19, 2026 at 11:06 AM Roman Sanaye ***@***.***> wrote: Hello, I have added the “Needs Review” label to both PRs. I have addressed all the feedback you provided, and usually after reviewing, the reviewer marks them as complete. I did not mark them as reviewed myself. Kind regards, Roman Sanaye On Thu, Mar 19, 2026 at 10:42 AM CJ Yuan ***@***.***> wrote: > *cjyuan* left a comment (RomanSanaye/My-Coursework-Planner#85) > <#85 (comment)> > > In CYF courses, the recommended way to inform the reviewer of your > changes is to do both of the following: > > - *Reply to their feedback.* > - In the responses, clarify how each piece of feedback was > addressed to demonstrate that you've carefully reviewed the suggestions. > - You may find the suggestions in this PR Guide > <https://programming.codeyourfuture.io/guides/reviewing/trainee-pr-guide/#addressing-reviewer-feedback> > useful. > - Your response may trigger a notification (depending on the > reviewer's settings), helping ensure they’re aware of the updates you’ve > made. > - *Replace the "Reviewed" label by a "Needs review" label* > - Without this label, the reviewer would not know if your changes > is ready to be reviewed. > > In your "Implement functions and rewrite tests" PR > <CodeYourFuture/Module-Structuring-and-Testing-Data#1119>, > you should at least add the "Needs Review" label to the PR after you have > made the change. > > In your TDD PR > <CodeYourFuture/Module-Structuring-and-Testing-Data#1167>, > you didn't respond to my comments and you did not made any new commits > based on those comments. If you have committed changes on your computer, > you will need to push/sync them to GitHub for the commits to appear on your > PR. After that, add a "Needs Review" label to the PR. > > — > Reply to this email directly, view it on GitHub > <#85 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BSZT7H6I4SDYDNIWL265YMT4RPFIJAVCNFSM6AAAAACWJRMOKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBZGIZDGMBQGY> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[RomanSanaye]

Hi @cjyuan ,
all the PR are marked complete now, should I paste the link again to the board for submitting or not?

[cjyuan]

Resubmitting the link on Dashboard would make my job easier, but I managed to find your submitted link on the Dashboard and approved it.3
You can resubmit the link for Step 3 or 4 in case they got rejected.