Skip to content

25-ITP-Sep | Data groups | Baba Yusuf #80

@Baba05206

Description

@Baba05206

a. Evidence that you have completed at least 6 katas in the Data Groups collection and at least 9 katas in total in the Array and Object Methods collection.
https://codeyourfuture.github.io/Codewars-Progress-Checker/#Baba05206

Image

b. A link to your completed pull request for “Alarm Clock App”.
CodeYourFuture/Module-Data-Groups#900

c. A link to your completed pull request for “Sprint 2 Coursework”.
CodeYourFuture/Module-Data-Groups#873

d. A link to your completed pull request for “Quote Generator App”.
CodeYourFuture/Module-Data-Groups#892

e. A link to your “Brag Diary”. (It’s ok if this is a private document; you don’t need to share it if you don’t want to, but please include the link for your own reference).
https://docs.google.com/document/d/10J-jrzj6MSNoFSm3ghhkf72eJYr4E40rzhi_tKsXy5I/edit?usp=sharing

f. An explanation of how you have used your “Brag Diary” to record your progress.
I've made it my mission to earn at least one bragging right every single day, and my Brag Diary is the tool that makes this happen. Rather than waiting for big milestones, I've trained myself to notice and capture daily wins—no matter how small. Did I finally understand how closures work? That's going in. Debugged a tricky error independently? Documented. Helped a classmate solve a problem? Worth celebrating.
This daily practice has completely shifted how I approach learning. Instead of just consuming information and moving on, I actively look for moments where I've pushed myself forward. It's become a challenge I set for myself: What can I do today that's brag-worthy? This mindset keeps me engaged, motivated, and constantly progressing—even on days when I don't feel like I've achieved much.
When I sit down to update my diary, I don't just list what I did—I dig into the details. What was hard about it? What approach did I take? What can I do now that I couldn't do yesterday? This reflection turns everyday tasks into evidence of real growth. Over time, these small daily wins compound into a comprehensive record of my development as a coder, from struggling with basic JavaScript to confidently solving JavaScript katas.
The diary has also transformed how I see myself. Looking back at weeks of consistent entries, I can't deny the progress. I'm building proof—not just for others, but for myself—that I'm capable of learning hard things and pushing through challenges. On tough days when I doubt myself, I scroll through past entries and remember: I've earned a bragging right every day.
Beyond personal motivation, this daily documentation is incredibly practical. I'm building a library of real examples for interviews, complete with specific details about problems I've solved and skills I've developed. When someone asks "Tell me about a time you overcame a technical challenge," I don't have to scramble—I have dozens of documented examples to choose from.
The daily bragging right challenge has become more than just a diary—it's how I hold myself accountable, stay present in my learning, and build unshakeable confidence in my abilities. And I'm not stopping when this course ends. This is now part of how I operate as a developer.

g. A screenshot showing that you took part in an online study session with at least one other trainee. This could be a video call, a Slack thread, or something else!

Image

h. A screenshot showing that you gave a demo in a demo session with particular members of staff present.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions