I wanted to know if anyone was interested in coming together for
a small group ‘side project’ we could collectively place on our CV, Resume
and/or LinkedIn profiles to boost our hire-ability in the future?
Prospective employers love to see how we’ve taken the initiative in our
self-teaching programming journey here . But, what if we could
gather in tiny pods here at FCC to create small group
projects that will display not only our skillsets in coding, but also some
‘soft skills’ we possess amongst one another?
Right now I’m still working on my JS courses here so, any idea
that WE can join together to execute a ‘side project’ with HTML,
Maybe a game, or…something else? Anyone could do a small
group and engage here as well. In fact I encourage you to do
so if and when you are comfortable. Who knows, maybe our
Parent Objects will embed this later on in FCC’s future updates
to the site? Then any Child Object will be able to fall into a small project
group to “do/while” engaging in team-building exercises.
Maybe this option already exists and I’m not aware of it yet.
Employers love seeing: Self-Starter, Leadership, Teamwork
Listening, and Accountability on your resumes and “Reference Letters”
Dunt dunt duuuun!
Okay. I have the conceptual understanding of it. However, we need to find a mentor to assist with the repository in copying partial open source code.
Also, to make sure we are crediting the source-code creators properly.
When I discover this experienced person to get us started I will hit you back up.
However, I am wondering: maybe we can start the discussion about ‘what exactly do we want to build’ without this person? What do you think? Since you suggested the whole thing, maybe you have some ideas for project?
Hmm, I can see the HTML structuring. The text inputs, labeling, color choices.
There are various fonts and h-tags.
I can see there are action buttons, Hover buttons, a-tags that lead to the GitHub link where the repository is located. The team has also added a Site-Visit counter that when hit links to the team members involved in building the project on GitHub.
There is a scroll bar to the left. An advert in a ‘side’ column.
Okay, hold on, Admit8490…
I see the textbox and the p-tags explaining how to utilize the site.
I love it!
This does not appear too daunting. Hey everybody, how about this cool side project? I am ready.
I do not believe this project will take us 30 days. More like 7 to 14 days. I will ask the proper manner to setup things.
I think we all will be able to preform this project via CodePen for front-end
programming. How does everyone feel about this choice?
As said above, this project may be a good opportunity to learn more about git/github. I think we should use it, because this is important skill.
Codepen is also cool of course, but as far as I know, whole point of git is to manage cooperation and versions of projects.
Btw if you have GitHub account, I would like to follow.
That idea of mine about contrast-ratio app was literally the first which came into my head. I would like to build it, but maybe we should wait a little bit(not very long of course), maybe somebody will have more ideas and we will choose one option from several ones.
Good day to you!
Thanks for advice about repo.
I have some basic knowledge about GitHub, use it to manage my own code, but I am having hard time to find decent guides about… how the whole system works I guess
I mean issues, pull requests. How the whole cooperation thing goes together.
Guides which I encountered so far were not enough beginner-friendly I guess.
Maybe you can point me to some articles/links etc about the above?
I think this question is appropriate in this thread, but, if not, I believe as a moderator, you can split it into different thread.
It covers the basics of getting started and how to work with branches.
Once you guys decide on the project, then you will need to break up the work.
That is where the issues come in.
Break down the issues into manageable bits and add them to the issues tabs on github.
For example, one issue could be creating the basic setup files that everyone will be using.
In this case, your files would be an index.html, styles.css and index.js.
When the issue is created it is available for anyone on the team to grab.
If you interested in working on an issue, make sure to assign yourself to it so everyone knows that it is taken
Don’t worry about labels right now.
Once you pick up an issue, then you will create a new branch off of main.
That is covered in the video I linked.
Then you will do the work speficied in the issue.
When you are ready, then you will commit your changes on that branch.
You will then create a PR which shows all of the changes you made and want to merge into the main branch.
Then it is ready for review.
You will ask the team to take a look and make sure it is good to go.
Then you will merge it into main.
That is it in a nutshell.
The video will do a good walking through all of that fun stuff.
The main things you guys will learn during this project are the following:
How to break a project up into steps
How to pull down a repo and get it working on your local machine
How to create PR’s and how to make changes to your PR’s
How to review PR’s and approve them
How to deploy your app. I would suggest using Github pages or Netlify
How to deal with merge conflicts and keeping your local copy of the repo up to date when changes have been made to the main branch
I do have an account on CodePen, but I think that the idea of using Git/Github (which I know nothing about) is a good idea to help us maximize our real-world learning.
While I don’t have any other project ideas, I am sure there are some good ones on YouTube. For me, this project is more about learning how to work remotely in teams to create a project, so I am not picky about what we choose.
@jwilkins.oboe, thanks for the video and long post! I will watch this later today.