Merge branch 'main' into calculating-area-of-circle

.github/PULL_REQUEST_TEMPLATE.md

@@ -55,6 +55,8 @@ about: A template PR for code review with a checklist
 - [ ] The function's name describes it's behavior
 - [ ] The function's name matches the file name
 - [ ] The function has correct type annotations
+- [ ] The function is not called at the top level of the function file 
+  - _Recursive solutions **can** call the function from **inside** the function body_
 
 ## Strategy
 
@@ -82,5 +84,7 @@ about: A template PR for code review with a checklist
 - [ ] Variable names are clear and helpful
 - [ ] The code follows the strategy as simply as possible
 - [ ] The implementation is as simple as possible given the strategy
+- [ ] There are no commented lines of code
+- [ ] There are no `print` statements anywhere
 - [ ] The code includes defensive assertions
 - [ ] Defensive assertions include as little logic as possible

.vscode/settings.json

@@ -115,16 +115,35 @@
   // Enable/disable update table of contents on save
   "markdown.extension.toc.updateOnSave": false,
 
+  "cSpell.words": [
+    "Falag",
+    "Falaq",
+    "Heba",
+    "Luyando",
+    "Muna",
+    "Raghad",
+    "Saad",
+    "Taqwa"
+  ]
+}
+=======
+
   "[python]": {
+
+    "editor.defaultFormatter": "ms-python.black-formatter"
+  },
+  "cSpell.words": [
+    "catdog",
+    "cathatbat",
+    "Falaq",
+    "Truehello",
+=======
     "editor.defaultFormatter": "charliermarsh.ruff",
     "editor.formatOnSave": true,
     "editor.codeActionsOnSave": {
       "source.fixAll.ruff": "explicit",
       "source.organizeImports.ruff": "explicit"
     }
   },
-  "cSpell.words": [
-    "Falaq",
-    "Youniss"
-  ]
-}
+
+

README.md

@@ -1,37 +1,86 @@
-# WELCOME TO THE CODE COLLABORATORS' REPOSITORY
+# [![Typing SVG](https://readme-typing-svg.herokuapp.com?font=Fira+Code&size=26&pause=1000&width=435&lines=Welcome+to++RepoRangers!+%F0%9F%A4%A0%F0%9F%8C%B2)](https://git.io/typing-svg)
 
-![Visual aid code collaborators are from different parts of the world!](assets/collaboration.jpg)
-We are a collaborative group of problem-solvers who are working together to tackle
-exciting challenges in this particular project.
+![Technology GIF](https://media.giphy.com/media/bGgsc5mWoryfgKBx1u/giphy.gif)
+
+We are a collaborative group of problem-solvers working together to tackle
+exciting Python challenges in this particular project.
+
+## 🤝 Meet Us  
+
+Here's a fun fact about each of us and our GitHub accounts:  
+
+- **[Agnes](https://github.com/lwjskidsister)** 🤓💎  
+  *Fun Fact:* "I'm a nerd when it comes to diamonds."  
+
+- **[Falaq](https://github.com/FalaqMajeed)** ⚽📊  
+  *Fun Fact:* "Watching and analyzing football matches is my ultimate favorite pastime!"
+
+- **[Heba](https://github.com/HebaShaheen)** ☕️😅  
+  *Fun Fact:* "I drink a lot of Nescafe, 2 or 3 cups a day."  
+
+- **[Luyando](https://github.com/Luyando-Chitindi)** 😂😂  
+  *Fun Fact:* "I absolutely love laughing—it’s my favorite thing to do!"  
+
+- **[Marc](https://github.com/MarcDarazi99)** 🍋😋  
+  *Fun Fact:* "I’m a proud mango lover—if coding were a fruit, it’d be a mango:
+  sweet, versatile, and endlessly satisfying!"
+
+- **[Mohammed](https://github.com/Moealfadil)** 🤓📚  
+  *Fun Fact:* "I like mathematical theories."  
+
+- **[Muna](https://github.com/Muna-S)** 🐎❤️  
+  *Fun Fact:* "I’m completely obsessed with horses—they're my passion."  
+
+- **[Raghad](https://github.com/raghad598)** 💇‍♀️  
+  *Fun Fact:* "Every night before bed, I brush my hair and spritz on some perfume."
+
+- **[Saad](https://github.com/sashour82)** 👨‍💻  
+  *Fun Fact:* "Failed my first coding course, but graduated with a great GPA and
+  12 years in tech!"  
+
+- **[Taqwa](https://github.com/TagwaHashim)** 📚😄  
+  *Fun Fact:* "I'm like a hardcover book full of funny stories."  
 
 ## 🚀 Mission
 
-Our main mission is to build a foundation of creativity, collaboration, and learning
-while developing basic solutions that help in the build-up of solutions that
-provide aid to real-world problems.
+Our main mission is to cultivate creativity, collaboration, and continuous
+learning, while crafting innovative Python solutions and documenting them
+in the best possible way. 🐍📝
 
 ## 🔍 Our Current Focus
 
-We are currently exploring the endless world of project challenges.
-Each member of this group will select two challenges and share their progress in
-this repository.
+We are currently exploring the endless world of project challenges. Each member
+of this group will select two challenges and share their progress in this
+repository. 🏆
 
-## Repository Overview
+## 📂 Repository Overview
 
 This repository contains the following:
 
-- Group collaborations
-- Solutions and Tests to individual challenge projects.
+- Group collaborations 🤝  
+- Solutions and tests for individual challenge projects 🔬
+
+## 💡 Contributions
+
+Our aim is to promote collaboration among members. We believe there is always room
+for improvement in everything we do, and we welcome contributions, suggestions,
+and feedback from all members. 🛠️
+
+## 📚 Want to Know More About Our Collaboration?
 
-## Contributions
+- 📝 **[Our Group Norms](https://github.com/MIT-Emerging-Talent/ET6-foundations-group-18/tree/main/collaboration)**
+- 🎯 **[Learning Goals](https://github.com/MIT-Emerging-Talent/ET6-foundations-group-18/blob/main/collaboration/learning_goals.md)**
+- 💬 **[Communication](https://github.com/MIT-Emerging-Talent/ET6-foundations-group-18/blob/main/collaboration/communication.md)**
+- 🚧 **[Constraints](https://github.com/MIT-Emerging-Talent/ET6-foundations-group-18/blob/main/collaboration/communication.md)**
+- 🔄 **[Retrospective](https://github.com/MIT-Emerging-Talent/ET6-foundations-group-18/blob/main/collaboration/retrospective.md)**
+- 🐍 **[Our Python challenges and their tests](https://github.com/MIT-Emerging-Talent/ET6-foundations-group-18/tree/main/solutions)**
 
-Our aim is to promote collaboration among members. As we believe that
-there is always room for improvement in everything we do, we welcome
-contributions, suggestions, and feedback from all members.
+## 🌱 What to Expect?
 
-## 🤩 What to expect?
+As our project and challenges evolve, so will this README. Stay tuned for our
+regular updates! 🔄
 
-As our project and challenges change, so will this README. Stay tuned for our
-regular updates,
+## 💬 Remember
 
-Join us as we grow on this platform together!
+*Let's keep the hard work flowing, grow together, and put our heart and soul into
+every line of code!* 💖  

collaboration/retrospective.md

@@ -1,23 +1,75 @@
 <!-- this template is for inspiration, feel free to change it however you like! -->
 
-# Retrospective
+# Retrospective: Group 18 - Collaborative Work Activity
 
 ## Stop Doing
 
+- **Inefficient Coordination:** Stop relying on informal communication
+  methods that cause misunderstandings or delays.
+
+- **Overloading Tasks:** Avoid taking on excessive responsibilities
+  without proper delegation or prioritization.
+
+- **Passive Participation:** Stop being a silent participant in discussions;
+  ensure to actively contribute to conversations.
+
 ## Continue Doing
 
+- **Effective Teamwork:** Continue fostering collaboration by sharing ideas
+  openly and respecting diverse perspectives.
+
+- **Timely Updates:** Maintain a habit of providing timely progress updates
+  to keep the team aligned.
+
+- **Using Tools:** Keep leveraging collaborative tools
+  (e.g., shared documents, project management software) to enhance productivity.
+
 ## Start Doing
 
+- **Structured Planning:** Begin creating more detailed action plans with
+  clear milestones and deadlines.
+
+- **Feedback Loops:** Start implementing regular feedback sessions to
+  evaluate progress and address challenges early.
+
+- **Skill Development:** Focus on improving specific skills related
+  to collaborative work and presentation to contribute more effectively.
+
 ## Lessons Learned
 
+- Effective communication is crucial to avoid duplication of efforts and ensure alignment.
+
+- Clear roles and responsibilities significantly enhance team productivity.
+
+- Flexibility in strategy allows for better adaptation to unforeseen challenges.
+
+- Regular check-ins help maintain momentum and ensure accountability.
+
 ______________________________________________________________________
 
 ## Strategy vs. Board
 
 ### What parts of your plan went as expected?
 
+- Collaboration tools were effectively utilized to
+  share resources and coordinate tasks.
+
+- The team successfully met initial deadlines for project deliverables.
+
+- Team members demonstrated a willingness to support each other when challenges arose.
+
 ### What parts of your plan did not work out?
 
+- Some tasks were delayed due to unclear task ownership.
+
+- Miscommunication led to redundant efforts in certain areas.
+
+- Time zone differences caused occasional scheduling conflicts.
+
 ### Did you need to add things that weren't in your strategy?
 
-### Or remove extra steps?
+- Yes, we added weekly synchronization meetings to
+  address miscommunications and ensure alignment.
+
+- Included additional training sessions for team members to
+  improve tool usage efficiency.

notes/cheetsheets.md

@@ -0,0 +1,9 @@
+# 📝 Cheat Sheets That We Can Use
+
+## 🚀 These cheat sheets will cover Python and VS Code
+
+- 🔧 [**VS Code Cheat Sheet**](https://code.visualstudio.com/shortcuts/keyboard-shortcuts-windows.pdf)
+ — Boost your productivity with essential shortcuts. 🚀
+
+- 🐍 [**Python Cheat Sheet**](https://kieranholland.com/best-python-cheat-sheet/)
+  — Quickly reference key Python concepts and syntax. ✏️

notes/creating_linking_issue.md

@@ -0,0 +1,34 @@
+# 🚀 How to create and link an issue to a pull request
+
+## 📝 How to Create an Issue
+
+1. Go to the **Issues** tab. 🐛
+2. Click on **New Issue** ➕.
+3. Fill out the issue template with all relevant details. 📋
+4. Assign labels 🏷️ and add it to the project board 📌.
+
+---
+
+## 🔗 Linking an Issue to a Pull Request
+
+1. Create a branch for your changes. 🌱
+2. Make the necessary edits. ✏️
+3. Open a Pull Request (PR) 🛠️:
+   - Use `Fixes #<issue_number>` in the description to close the issue automatically
+  on merge. ✅
+   - For example:
+
+     ```markdown
+     Fixes #123
+     ```
+
+---
+
+### Link the issue manually if needed
+
+- Go to the **Linked Issues** section in the PR.  
+- Search for the issue and add it. 🔗
+
+## 📣 Need Help?
+
+If you're stuck, don't hesitate to reach out! 🆘