From d8dd1c932acb59c80496d2ccc61e4846d6a12b8e Mon Sep 17 00:00:00 2001 From: JosephineHYF <113513079+JosephineHYF@users.noreply.github.com> Date: Tue, 12 Dec 2023 15:49:00 +0100 Subject: [PATCH 01/12] Update README.md --- Week1/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Week1/README.md b/Week1/README.md index 6c240965..fb48afd5 100644 --- a/Week1/README.md +++ b/Week1/README.md @@ -14,7 +14,8 @@ These are the topics for week 1: - Chaining - Benefits 3. [The Event Loop](https://study.hackyourfuture.net/#/the-internet/event-loop) -4. [Career Training II (Interview preparation)](https://github.com/HackYourFuture/interviewpreparation) +4. [Your personal brand](https://github.com/HackYourFuture/yourpersonalbrand) - Continue reading! +5. [Career Training II (Interview preparation)](https://github.com/HackYourFuture/interviewpreparation) ## Week goals From c6267158a3dc12a2ee9d278a7f5cb397946cd2a5 Mon Sep 17 00:00:00 2001 From: JosephineHYF <113513079+JosephineHYF@users.noreply.github.com> Date: Tue, 12 Dec 2023 15:52:47 +0100 Subject: [PATCH 02/12] Update README.md --- Week2/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Week2/README.md b/Week2/README.md index 5c54dfaf..1af57a4e 100644 --- a/Week2/README.md +++ b/Week2/README.md @@ -11,6 +11,7 @@ These are the topics for week 2: 3. [Async/Await](https://study.hackyourfuture.net/#/javascript/modern-js) - Catching errors with try/catch 4. [Interview preparation](https://github.com/HackYourFuture/interviewpreparation) +5. [Career Training I](https://github.com/HackYourFuture/yourpersonalbrand): Not all at once! ## Week goals From 81cdd3ef99f0b58289ae3a895aa7d6507d0dabc7 Mon Sep 17 00:00:00 2001 From: JosephineHYF <113513079+JosephineHYF@users.noreply.github.com> Date: Tue, 12 Dec 2023 15:57:33 +0100 Subject: [PATCH 03/12] Update README.md --- Week2/README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Week2/README.md b/Week2/README.md index 1af57a4e..9b716028 100644 --- a/Week2/README.md +++ b/Week2/README.md @@ -10,8 +10,7 @@ These are the topics for week 2: 2. [Fetch API](https://study.hackyourfuture.net/#/the-internet/fetch) 3. [Async/Await](https://study.hackyourfuture.net/#/javascript/modern-js) - Catching errors with try/catch -4. [Interview preparation](https://github.com/HackYourFuture/interviewpreparation) -5. [Career Training I](https://github.com/HackYourFuture/yourpersonalbrand): Not all at once! +4. [Career Training I](https://github.com/HackYourFuture/yourpersonalbrand): Not all at once! ## Week goals From 603eed90b3b2a1ed9b39c5a6591d10eb436345b3 Mon Sep 17 00:00:00 2001 From: JosephineHYF <113513079+JosephineHYF@users.noreply.github.com> Date: Tue, 12 Dec 2023 16:01:46 +0100 Subject: [PATCH 04/12] Update README.md --- Week2/README.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/Week2/README.md b/Week2/README.md index 9b716028..1e02f210 100644 --- a/Week2/README.md +++ b/Week2/README.md @@ -24,9 +24,12 @@ Last week we learned about Promises and with the increased use of promises, mode You will probably ask yourself now which way is best to handle asynchronous code and the answer is that there is no best way. Generally callbacks are great for simple applications, but get into callback hell if stuff gets too complicated. Promises with `.then` chains are great for more complex situations where the chaining can be very powerful, but can be a little hard to follow for people who do not have much experience with them. Using async/await makes the code look a little more synchronous again and that can make it easier to follow. It does, however, make it a little more complex to handle errors or situations where something absolutely needs to be done (a `finally` is invaluable in these situations). So, it is up to you to decide based on the situation what to use. -## Career training II (Interview preparation) -If you haven't finished all the material yet, then continue with it this week. +## Career training 1 (Your personal brand) -## Finished? +After the project you will have your first project that you can put on your CV! For now that is, as you will want to add many more in the future as you progress in your abilities. It is therefore time to start thinking about all of the steps required to start the job search and getting accepted to your first programming job. The first step to this will be handled in Career training 1: Your personal brand. This is all about making your CV, GitHub, LinkedIn, etc. stand out. These are the first things employers will look at so it is your first impression and has to be great! We have compiled a big list of information about how to go about creating your personal brand in [this repo](https://github.com/HackYourFuture/yourpersonalbrand). -Are you finished with going through the materials? High five! If you feel ready to get practical, click [here](./MAKEME.md). +### Career training 1: Planning + +You don't have to do all of this at this moment. Before the end of the Browsers module you will get a message in your cohort channel about when the Career Training 1 session will be. *Before* that session make sure to have: +- Read the whole [personal brand repository](https://github.com/HackYourFuture/yourpersonalbrand). +- Done the [assignment](https://github.com/HackYourFuture/yourpersonalbrand/blob/main/yourcurriculum.md#4-submitting-your-cv-to-the-hyf-team) for the repository. From 2ed248db9f07cacd28c02fa04d090b572801064a Mon Sep 17 00:00:00 2001 From: JosephineHYF <113513079+JosephineHYF@users.noreply.github.com> Date: Tue, 12 Dec 2023 16:09:20 +0100 Subject: [PATCH 05/12] Update README.md --- Week1/README.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/Week1/README.md b/Week1/README.md index fb48afd5..c399630b 100644 --- a/Week1/README.md +++ b/Week1/README.md @@ -15,8 +15,6 @@ These are the topics for week 1: - Benefits 3. [The Event Loop](https://study.hackyourfuture.net/#/the-internet/event-loop) 4. [Your personal brand](https://github.com/HackYourFuture/yourpersonalbrand) - Continue reading! -5. [Career Training II (Interview preparation)](https://github.com/HackYourFuture/interviewpreparation) - ## Week goals @@ -26,9 +24,6 @@ In this module we are going to learn how to connect our applications with data s Lastly, as we now know everything about asynchronicity, we can look at the browser's [Event Loop](https://study.hackyourfuture.net/#/the-internet/event-loop) which every browser implements. This will help you understand how and when your code gets executed in the browser. This will help you decide where to link up your code with the DOM so that it does what you expect. -## Career training II (Interview preparation) -Finally it is time to continue with developing your soft skills to ace those job interviews. For that, have a look at the [interview preparation repo](https://github.com/HackYourFuture/interviewpreparation). It is a lot to get through, so you may need some time next week as well. There is no assignments for this week, but there is some assignments for the career training next week, you can already have a look at it if you find these things difficult. - ## Finished? Are you finished with going through the materials? High five! If you feel ready to get practical, click [here](./MAKEME.md). From 1176d4b3cd88ffda45e135e5a6f38e74702b9940 Mon Sep 17 00:00:00 2001 From: JosephineHYF <113513079+JosephineHYF@users.noreply.github.com> Date: Tue, 12 Dec 2023 16:10:48 +0100 Subject: [PATCH 06/12] Update README.md --- Week1/README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/Week1/README.md b/Week1/README.md index c399630b..4a45c1f5 100644 --- a/Week1/README.md +++ b/Week1/README.md @@ -14,7 +14,6 @@ These are the topics for week 1: - Chaining - Benefits 3. [The Event Loop](https://study.hackyourfuture.net/#/the-internet/event-loop) -4. [Your personal brand](https://github.com/HackYourFuture/yourpersonalbrand) - Continue reading! ## Week goals From 85a344435677439f0529a4138746d190d1547ccb Mon Sep 17 00:00:00 2001 From: JosephineHYF <113513079+JosephineHYF@users.noreply.github.com> Date: Tue, 12 Dec 2023 16:33:04 +0100 Subject: [PATCH 07/12] Update README.md --- Week2/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Week2/README.md b/Week2/README.md index 1e02f210..bf7f40c3 100644 --- a/Week2/README.md +++ b/Week2/README.md @@ -22,14 +22,14 @@ There are many ways to request data from an API, initially everything was done u Last week we learned about Promises and with the increased use of promises, modern JavaScript introduced some new syntax that can be used with those promises. Have a look at the section on Async/await in the modern JavaScript page of your study book [here]((https://study.hackyourfuture.net/#/javascript/modern-js)) now that you know what promises are so that you know what it does. -You will probably ask yourself now which way is best to handle asynchronous code and the answer is that there is no best way. Generally callbacks are great for simple applications, but get into callback hell if stuff gets too complicated. Promises with `.then` chains are great for more complex situations where the chaining can be very powerful, but can be a little hard to follow for people who do not have much experience with them. Using async/await makes the code look a little more synchronous again and that can make it easier to follow. It does, however, make it a little more complex to handle errors or situations where something absolutely needs to be done (a `finally` is invaluable in these situations). So, it is up to you to decide based on the situation what to use. +You will probably ask yourself now which way is best to handle asynchronous code and the answer is that there is no best way. Generally callbacks are great for simple applications, but get into callback hell if stuff gets too complicated. Promises with `.then` chains are great for more complex situations where the chaining can be very powerful, but can be a little hard to follow for people who do not have much experience with them. Using async/await makes the code look a little more synchronous again and that can make it easier to follow. It does, however, make it a little more complex to handle errors or situations where something absolutely needs to be done (a `finally` is invaluable in these situations). So, it is up to you to decide based on the situation what to use. -## Career training 1 (Your personal brand) +## Career Training I (Your personal brand) -After the project you will have your first project that you can put on your CV! For now that is, as you will want to add many more in the future as you progress in your abilities. It is therefore time to start thinking about all of the steps required to start the job search and getting accepted to your first programming job. The first step to this will be handled in Career training 1: Your personal brand. This is all about making your CV, GitHub, LinkedIn, etc. stand out. These are the first things employers will look at so it is your first impression and has to be great! We have compiled a big list of information about how to go about creating your personal brand in [this repo](https://github.com/HackYourFuture/yourpersonalbrand). +Since you completed Browsers, you now have a first project to write down on your CV! You will add many more in the future, as you progress in your abilities. It is therefore time to start thinking about all of the steps required to start the job search and to get accepted to your first programming job. The first step will be handled in the Career Training I: _your personal brand_. We will cover how to present your CV, GitHub, LinkedIn, etc. to that they stand out. These are the first things employers will look at, so they convey a first impression of you and has to be great! We have compiled a big list of information about how to go about creating your personal brand in [this repo](https://github.com/HackYourFuture/yourpersonalbrand). -### Career training 1: Planning +### Career Training I: Planning -You don't have to do all of this at this moment. Before the end of the Browsers module you will get a message in your cohort channel about when the Career Training 1 session will be. *Before* that session make sure to have: +You don't have to do all of this immediately. Somewhere this week you will receive a message in your cohort channel from Giuseppina to plan the Career Training I. *Before* that session, make sure to have: - Read the whole [personal brand repository](https://github.com/HackYourFuture/yourpersonalbrand). - Done the [assignment](https://github.com/HackYourFuture/yourpersonalbrand/blob/main/yourcurriculum.md#4-submitting-your-cv-to-the-hyf-team) for the repository. From bcbe0c4857485c949f5fe7c098a07c686d2b9148 Mon Sep 17 00:00:00 2001 From: JosephineHYF <113513079+JosephineHYF@users.noreply.github.com> Date: Tue, 12 Dec 2023 16:37:12 +0100 Subject: [PATCH 08/12] Update README.md --- Week3/README.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/Week3/README.md b/Week3/README.md index a743733f..89322456 100644 --- a/Week3/README.md +++ b/Week3/README.md @@ -2,13 +2,13 @@ In the final week of the Using API's module you will put everything you have learned to good use and build your own single page application that is connected to an API! What you build is totally up to you. Maybe you already had an idea in your head for a while, or maybe you will get inspired by all the open API's that are available. -This is quite a big undertaking, so during the project one of the mentors for this module will be assigned to you. Feel free to ask them for help if you are stuck or unsure, but they have been instructed to not write any code for you :). +This is quite a big undertaking, so you will have a mentor assigned to you to assist you in the project. Feel free to ask them for help if you are stuck or unsure, but they have been instructed to not write any code for you :). ## Project requirements We want you to get excited and be free to build something you are passionate about, but there are some things that we need to see you have mastered. This means there are a few requirements: - The app needs to be responsive. -- The app needs to be a single page application. That means there should be only one `index.html` file and JavaScript needs to update the html using DOM manipulation. +- The app needs to be a single page application. That means there should be only one `index.html` file and JavaScript needs to update the HTML using DOM manipulation. - The app needs to interact with an API to grab data. - The app needs to have loading/error handling for the interaction with the API and needs to show this to the user, not just a `console.log`. - The app needs some user interaction such that you need to grab different data from the API. So you cannot just grab everything from the API and store it locally with one fetch. @@ -44,10 +44,10 @@ If you really are stuck and have no inspiration, have a chat with your project m Something like [this extension](https://chrome.google.com/webstore/detail/json-viewer/gbmdgpbipfallnflgajpaliibnhdgobh) will make it easier to work with an API. If your request returns JSON, which the API's do, it will format it nicely in your browsers so that you can easily navigate what the API is giving you. ## Final product -The final product (the repository is the product, not just the application) should be something that you can show off on your CV. So have a look at our technical assignment guidelines [here](https://github.com/HackYourFuture/ta_guidelines) and our design guidelines [here](https://github.com/HackYourFuture/design_guidelines) to see what it entails. By following those guidelines your app AND your code will look great, making it a great thing to show off to employers. You will also get into the habit of doing this with all the technical assignments you will get during your job search. +The final product (the repository is the product, not just the application) should be something that you can show off on your CV. So have a look at our technical assignment guidelines [here](https://github.com/HackYourFuture/ta_guidelines) and our design guidelines [here](https://github.com/HackYourFuture/design_guidelines) to see what it entails. By following those guidelines your app _and_ your code will look great, making it a great thing to show off to employers. You will also get into the habit of doing this with all the technical assignments you will get during your job search. ## Planning and deadlines -There are only 2 deadlines in the project, how you divide your time for the rest is up to you. +There are only two deadlines for the project; how you divide your time for the rest is up to you. ### Deadline 1: Project definition By *Thursday 18:00PM CET* (but the earlier the better) you should send a short description of what your app will be as well as the name of the company whose brand/colour palette you will be mimicking to your project mentor. @@ -74,5 +74,3 @@ _Note: following the technical assignment guidelines will also be a part of the As you are all working on the projects this week there will not be a Q&A session on Sunday. Enjoy getting practical! - - From a30a3362c7cb634accab5370cf6f607801a90ebc Mon Sep 17 00:00:00 2001 From: stasel <2033301+stasel@users.noreply.github.com> Date: Wed, 27 Mar 2024 17:08:29 +0100 Subject: [PATCH 09/12] Added rapidapi.com to the list of API ideas --- Week3/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Week3/README.md b/Week3/README.md index 89322456..38a76b03 100644 --- a/Week3/README.md +++ b/Week3/README.md @@ -19,9 +19,10 @@ We want you to get excited and be free to build something you are passionate abo There are many APIs that are open to get data from, have a look at the following lists to see if there is a topic that interests you: - [publicapi.dev](https://publicapi.dev) -- [public api repo](https://github.com/public-apis/public-apis) +- [public API repo](https://github.com/public-apis/public-apis) - [API list](https://apilist.fun/) - [Public APIs](https://public-apis.io/) +- [RapidAPI](https://rapidapi.com/hub) When looking to see if an API is suitable for you there are a couple of questions to check: 1. Is the API rated, and if so how? From 34033984348cf8a5ad8ca7d9f9204edd3b49b459 Mon Sep 17 00:00:00 2001 From: Stasel <2033301+stasel@users.noreply.github.com> Date: Thu, 28 Mar 2024 11:38:28 +0100 Subject: [PATCH 10/12] Update README.md Fixed a broken link --- Week3/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Week3/README.md b/Week3/README.md index 38a76b03..43b63a04 100644 --- a/Week3/README.md +++ b/Week3/README.md @@ -21,7 +21,7 @@ There are many APIs that are open to get data from, have a look at the following - [publicapi.dev](https://publicapi.dev) - [public API repo](https://github.com/public-apis/public-apis) - [API list](https://apilist.fun/) -- [Public APIs](https://public-apis.io/) +- [Public APIs](https://publicapis.io/) - [RapidAPI](https://rapidapi.com/hub) When looking to see if an API is suitable for you there are a couple of questions to check: From 00497df47d3ccc32ea67c067516e78741e90a525 Mon Sep 17 00:00:00 2001 From: stasel <2033301+stasel@users.noreply.github.com> Date: Wed, 12 Jun 2024 12:10:33 +0200 Subject: [PATCH 11/12] Added CORS section to Week 2 readings --- Week2/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Week2/README.md b/Week2/README.md index bf7f40c3..5e63ef86 100644 --- a/Week2/README.md +++ b/Week2/README.md @@ -7,7 +7,7 @@ These are the topics for week 2: 1. [Application Programming Interface (API)](https://study.hackyourfuture.net/#/the-internet/api) - Public/private APIs - Connecting with APIs -2. [Fetch API](https://study.hackyourfuture.net/#/the-internet/fetch) +2. [Fetch API](https://study.hackyourfuture.net/#/the-internet/fetch) and [CORS](https://study.hackyourfuture.net/#/the-internet/cors) 3. [Async/Await](https://study.hackyourfuture.net/#/javascript/modern-js) - Catching errors with try/catch 4. [Career Training I](https://github.com/HackYourFuture/yourpersonalbrand): Not all at once! From decde37d0beacc7a12cb1484cf4e0da6022763d1 Mon Sep 17 00:00:00 2001 From: stasel <2033301+stasel@users.noreply.github.com> Date: Wed, 12 Jun 2024 12:11:12 +0200 Subject: [PATCH 12/12] Added CORS section to Week 2 readings --- Week2/README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Week2/README.md b/Week2/README.md index 5e63ef86..a05fd1c4 100644 --- a/Week2/README.md +++ b/Week2/README.md @@ -7,10 +7,11 @@ These are the topics for week 2: 1. [Application Programming Interface (API)](https://study.hackyourfuture.net/#/the-internet/api) - Public/private APIs - Connecting with APIs -2. [Fetch API](https://study.hackyourfuture.net/#/the-internet/fetch) and [CORS](https://study.hackyourfuture.net/#/the-internet/cors) -3. [Async/Await](https://study.hackyourfuture.net/#/javascript/modern-js) +2. [Fetch API](https://study.hackyourfuture.net/#/the-internet/fetch) +3. [CORS](https://study.hackyourfuture.net/#/the-internet/cors) +4. [Async/Await](https://study.hackyourfuture.net/#/javascript/modern-js) - Catching errors with try/catch -4. [Career Training I](https://github.com/HackYourFuture/yourpersonalbrand): Not all at once! +5. [Career Training I](https://github.com/HackYourFuture/yourpersonalbrand): Not all at once! ## Week goals