Daniel: workflows, 2

[denrique-alvarez]

my fork of the exercises repo

Learning Objectives

• [x] Git Remote/Local Connection: You can create a local git repository, commit changes, connect a remote repository and push changes to the remote.
• [x] Linting: what is it? why does it matter? can write CSS & Markdown that passes a linting check
• [x] Git Branching Workflow: You can manage your work locally using branches: pull remote changes -> create a new branch -> push the branch to the remote repository -> open a PR with passing Continuous Integration checks -> merge changes to main/master.
• [x] Command Line Interface (CLI): You can navigate a directory, manage folders/files, make small changes in a file using nano/vim, and much more (list coming soon).
• [x] NPM: You can install npm dependencies and use npm scripts (dev, lint and format)
• [x] Browser + DevTools: You can open a local HTML/CSS project in your browser and inspect the elements, emulate different devices, and inspect the source
• [x] File Extensions: You can 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!)
• [x] Touch Typing: You can write a README without looking at your keyboard to find any letters, numbers or special characters. (slowly is ok!)
• [x] VSCode: You 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
• [x] User Stories: Given pictures of a website, you can describe the page with user stories: As a type of user I can do something so that something good happens.
• [x] Planning and Collaborating: You can comfortably complete these steps of the Planning and Collaborating process described in the Student Guidebook:
  • Repository Setup
  • Project Definition
  • Communication Plan
  • Backlog
  • Wireframe
• [x] Development Strategies: You can work as a group to follow the steps in a development strategy and reconstruct a web page when the code is provided.
• [ ] Atomic Commits & Feature Branches: You can 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.
• [x] GitHub: You can create new repositories, turn on GitHub Pages, connect the repository to your local computer, push/pull different branches, and pass Continuous Integration checks for code linting and validation.
• [x] GitHub Collaboration: You can collaborate in a single repository and contribute a markdown file. This includes: creating a new branch, creating and editing a file on that branch, sending a pull request, addressing any requested changes, and reviewing+merging a classmate's pull request. (this can all be done from the GitHub UI)
• [ ] Code Review: You can use a code review checklist in a Pull Request to check a classmate's code before merging.

[denrique-alvarez]

Week 1

• [x] I have pushed my progress to my fork of exercises repo

Check-In

I Need Help With:

Formatting and passing all the checks. What does "Staging" actually mean?

What went well?

I understood most of the processes in GitHub, GitHub desktop, and VScode.

What went less well?

I didn't completely understand how to run the commands in the terminal but I do have a better grasp now.

Lessons Learned

It was very good for me to practice using the different functionalities of GitHub, GitHub desktop and vs code, all together. I also learned about what certain concepts actually mean, such as PR, Issue, Fetching, Projects, and Project's board, Merging, and how to keep track of all of these parts/aspects of a repository in GitHub.

Sunday Prep Work

I will try to check as much material as possible from the recommended sources to keep improving my general understanding of the tools we have learned so far.

[colevandersWands]

Formatting and passing all the checks.

You're able to fix all the errors locally before pushing? @gelilaa pointed out to me there was actually a mistake in the linting action, that could be why you have no errors locally but it still doesn't work. you can copy-paste this updated file into yours (directly on main so you don't have to deal with a failing check)

[colevandersWands]

What does "Staging" actually mean?

Staging is one of the steps in adding changes to a git tree, I think of it this way:

• staging moves the changes from being just on your file system to also being in a little git waiting room. You could remove the file from your computer's standard folder system and it will still be in staging (until you git add again). staged changes are not pushed
• committing moves changes from the waiting room to the git tree (those circles and lines you see in the git games). then the changes are "permanently" in the git history and will be pushed.

[denrique-alvarez]

Thanks for your help @colevandersWands !

[denrique-alvarez]

Week 2

• [x] I have pushed my progress to my fork of exercises repo

Check-In

I Need Help With:

Nothing so far. I think I just need to get some more practice with CLI. I am just being lazy and using Github desktop most of the time.

What went well?

I keep gaining some more confidence with Github and some more processes like reviewing someone else's PR's, setting up a repository, checking the general project status, running different types of commands locally, among others.

What went less well?

I think there were three challenges this week. One related to teamwork and agreeing on some basic things, which was of course the main purpose of the assignment. The other challenge had to do more with clarity about what should be done in the assignment. In the end, @colevandersWands gave us the necessary clarifications and we did what we were supposed to do -I think :sweat_smile:

Lessons Learned

I learned about different aspects of web development that are very important and have everything to do with it, but not necessarily imply coding. I guess that's the main lesson here: coding is just a small part of the job.

Sunday Prep Work

I will re-read the Planning and Collaborating section of the student's book. I think having a good understanding of each document and its purpose will help a lot in future projects.

[colevandersWands]

and we did what we were supposed to do -I think 😅

👀

I will re-read the Planning and Collaborating section of the student's book. I think having a good understanding of each document and its purpose will help a lot in future projects.

no worries if you aren't comfortable with these documents right away. That chapter is also the main objective of next module, and you'll get a chance to practice it with almost every module from now till the Final Project.

I guess that's the main lesson here: coding is just a small part of the job.

100% -> https://home.hackyourfuture.be/curriculum#programming-is-communication

[denrique-alvarez]

Thanks! @colevandersWands

[colevandersWands]

and we did what we were supposed to do -I think 😅

It looks really good! Overall using issues and PRs to plan seems to be working for you. Some room for improvement but nothing that looks like your group is headed in the wrong direction. For example some PRs include two changes, one updated CSS and the communication plan.

You can also be more proactive with the project board, I see lots of cards have been added to the board but were not moved to any column. This makes it harder to see what's going on

No worries that you haven't made it through much of the HTML & CSS this week, you'll be planning two more projects in the next module. With each project the planning will go smoother and you'll be able to make it further through the code