Ashenafi: Check-Ins

[ashenafykebede]

Exercise repository (Week 1)

Learning Objectives (Week 1)

• 🥚 Git Remote/Local Connection: I can:
  • [x] create a local git repository
  • [x] commit changes
  • [x] connect a remote repository
  • [x] push changes to the remote.
• 🥚 Linting: what is it? why does it matter?
  • [x] can write CSS & Markdown that passes a linting check
• 🥚 Git Branching Workflow: I can:
  • [x] manage your work locally using branches
  • [x] pull remote changes
  • [x] create a new branch
  • [x] push the branch to the remote repository
  • [x] open a PR with passing Continuous Integration checks
  • [x] merge changes to main/master.
• 🥚 Command Line Interface (CLI): I can:
  • [x] navigate a directory
  • [x] manage folders/files
  • [x] make small changes in a file using nano/vim, and much more (list coming soon).
• 🥚 NPM: You can:
  • [x] install npm dependencies
  • [x] use npm scripts (dev, lint and format)
• 🥚 Browser + DevTools: I can:
  • [x] open a local HTML/CSS project in your browser
  • [x] inspect the elements
  • [x] emulate different devices
  • [x] inspect the source
• 🥚 File Extensions: I can:
  • [x] identify all of the languages covered at HYF and give the correct file extension. (You don't need to know the languages, just recognize them!)
• 🥚 VSCode: I can complete these workflows in VScode, and can use keyboard shortcuts when possible:
  • [x] Opening a repository in a new window
  • [x] Opening the repository in VSCode terminal
  • [x] Adding a new file
  • [x] Adding a new folder
  • [x] Deleting a file
  • [x] Deleting a folder
  • [x] Previewing a Markdown File
  • [x] Opening an HTML file with the LiveServer extension
  • [x] Viewing the repository's git history with Git Graph extension
• 🐣 Touch Typing: I can:
  • [x] write a README without looking at my keyboard to find any letters, numbers or special characters. (slowly is ok!)

[ashenafykebede]

Check-In [Week 1]

Exercise repository (Week 1)

What went well?

• Creating issues and pull requests

• Assigning people (including myself) for an issue and PRs

• Cloning a repository using SSH

• Creating a branch from the cloned (local) repository

• Creating files in different directories/folders, making commits with commit messages to the branch using both Terminal and VS code

• Pushing changes to remote repository

• Creating a pull request and assign reviewers

• Created a list of Git terminal commands and pull request for the vocabulary deliverable in the class repo

• Discussions and supports among our group members

What went less well?

• Unable to pass lint checks :wink:

• Learning a lot of github jargons at the same time.

• Unable to get a common time to discuss with all group members

I need help with

• linting

Lessons learned

• Git terminal is fast and reliable if you can use it correctly.

• I realized GitHub is not only version controlling but much more than that.

• I should spend more time exploring GitHub features

• Googling when you stuck is a life-saver.

• Stack overflow is like a programming encyclopedia. A lot of questions and helpful answers and discussions

• I still need to learn a lot.

Study time

• I have dedicated at least a few hours a day for my HYF class related activities

Preparation for Sunday class

• I have briefly skimmed the contents of the planning and collaborating topic

[gelilaa]

Unable to pass lint checks 😉

We are really sorry that you are getting this problem on your first projects. To clarify what was happening follow this discussion

https://github.com/lab-antwerp-1/home/issues/28

Learning a lot of github jargons at the same time.

You are not expected to learn everything about GitHub in the first week. We will be using the platform for the duration of the program so you will have enough time to get everything. 🎩 off to you for doing so😊

Unable to get a common time to discuss with all group members As @colevandersWands put it neatly

“Working with a group is really hard. If I could summarize the first 5 weeks of the course into a single goal it would be just that - planning and collaborating. So no rush here, you're expected to have all sorts of challenges at first. Each project in the coming weeks will be too quick to finish - the goal is to practice getting together as a group to plan a project and start dividing tasks. You'll get more time to finish projects later on”

[ashenafykebede]

Thank you @gelilaa for the comments and feedbacks.

I really hope I will be able to master Github in the coming weeks to take advantage of its features.

👏🙏🙏

[ashenafykebede]

Exercise repository (Week 2)

Learning Objectives (Week 2)

• 🐣 User Stories: Given pictures of a website, I can:
  • [x] describe the page with user stories: As a type of user I can do something so that something good happens.
• 🐣 Planning and Collaborating: I can comfortably complete these steps of the Planning and Collaborating process described in the Student Guidebook:
  • [x] Repository Setup
  • [x] Project Definition
  • [x] Communication Plan
  • [x] Backlog
  • [x] Wireframe
    • 🐣 Development Strategies: I can:
  • [x] work as a group to follow the steps in a development strategy
  • [x] reconstruct a web page when the code is provided.
• 🐣 Atomic Commits & Feature Branches: I can:
  • [x] organize your development process using small single-purpose commits on feature branches. You will learn to develop each of these features on a separate branch and to merge it to main/master on GitHub when the feature is complete.
• 🐣 GitHub: I can:
  • [x] create new repositories
  • [x] turn on GitHub Pages
  • [x] connect the repository to my local computer
  • [x] push/pull different branches
  • [x] pass Continuous Integration checks for code linting and validation.
• 🐥 GitHub Collaboration: I can:
  • [x] collaborate in a single repository and contribute a markdown file.
  • [x] create a new branch
  • [x] create and edit a file on that branch
  • [x] send a pull request
  • [x] address any requested changes
  • [x] review +merge a classmate's pull request. (this can all be done from the GitHub UI)
• 🐥 Code Review: I can:
  • [x] use a code review checklist in a Pull Request to check a classmates code before merging.

[ashenafykebede]

Check-In [Week 2]

Exercise repository ( week 2)

What went well?

• My experience on how to use GitHub is getting better and better
• Collaborating with teams to build a project
• Creating exercise repo
  • setting up access management,
  • adding group members to the group repo,
  • setting up project board,
  • turn on discussions,
  • setting up live URL,
  • adding rules for code review for PRs, etc of the exercise repo which is generated from a template repo .
• Contributing to a project by following the planning and collaborating guides
• Creating group issue in the class repository.
• Creating pull request
• Reviewing PRS
• Able to write a code that passes all the checks

What went less well?

• We couldn't manage to have a meeting with all members
• Differences on understanding the assignment instructions among our group members. This opened a discussion that takes longer time than the actual project task. I guess this is expected. :smile:

I need help with

• I feel I understand the lessons and assignments so far. Hence, I have no questions or don't need any help for now. :wink:
• I am using googling for minor questions and doubts :smile:

Lessons learned

• I learned the basic planning and collaborating skills every programmer/developer has to learn.

• Working in a group makes a task simpler and manageable

• Being a programmer is not only about being an expert on a programming language , rather it is how well:

  • you plan the design,
  • you put a clear achievable targets,
  • you make task divisions,
  • you understand target users of the design,
  • you create a communication,
  • you define your constraints (time, budget, skill level, technology) etc

• Googling, asking group members, participating on online meeting by our respected coaches when I stuck is a life-saver.

Preparation for Sunday class

• I am reading on some of the suggested study materials for chapter 3 : Agile Development

[colevandersWands]

We couldn't manage to have a meeting with all members Differences on understanding the assignment instructions among our group members. This opened a discussion that takes longer time than the actual project task. I guess this is expected. 😄

If this is what went less well, then you're on 🔥 . it is expected ; )