|
6 | 6 | 2. Practice exercises
|
7 | 7 | 3. PROJECT: HackYourTemperature II
|
8 | 8 | 4. Code alongs
|
9 |
| -5. Optional: Side project ideas |
| 9 | +5. Career Training 2 (If not completed yet) |
| 10 | +6. Optional: Side project ideas |
10 | 11 |
|
11 | 12 | ## **1. Prep exercises**
|
12 | 13 |
|
@@ -137,23 +138,30 @@ Enjoy!
|
137 | 138 |
|
138 | 139 | - [Ebook Sales Application](https://www.youtube.com/watch?v=QT3_zT97_1g)
|
139 | 140 |
|
140 |
| -## **5. Optional: Side project ideas** |
| 141 | +## **5. Career Training 2 (If not completed yet)** |
| 142 | + |
| 143 | +Remember that the Career Training 2 session is coming up (check your class channel on slack for the exact date). Before the session make sure you have: |
| 144 | + |
| 145 | +- Read the whole [‘Interview Preparation’ Repo](https://github.com/HackYourFuture/interviewpreparation). |
| 146 | +- Done the homework: make a copy of [this file](https://docs.google.com/document/u/2/d/114rTGS4eG6tpkrMAyVIdvgTrnpmkRL6ax_smkw1B0HI/copy) and submit your answers to the team [here](https://hackyourfuture.typeform.com/to/s6zYAugm). |
| 147 | + |
| 148 | +## **6. Optional: Side project ideas** |
141 | 149 |
|
142 | 150 | > A part of the HackYourFuture curriculum is to work on as many side projects as you can throughout the time you have. This is a nice way to add extra knowledge to your arsenal and show in your CV that you are motivated to learn new technologies. There are plenty of people available to help you out in the `#get-help` channel on Slack so definitely make use of that! Have a look at the [hyf_projects repo](https://github.com/HackYourFuture/hyf_projects/blob/main/README.md#project-2-a-try-out-application) for more details.
|
143 | 151 |
|
144 |
| -### 5.1 Document your API! |
| 152 | +### 6.1 Document your API! |
145 | 153 |
|
146 | 154 | When using API's in the `Using API's` module you will have noticed that those API's all have extensive documentation on how to use it. As developers like to build tools for everything there are quite a few good tools to semi-automatically document your API from your code! Saves a lot of work and makes sure that you don't forget to update the documentation if the code changes!
|
147 | 155 |
|
148 | 156 | Add automatic documentation to your API by using one of these tools (Swagger, apiDoc or docbox)!
|
149 | 157 |
|
150 |
| -### 5.2 Web Sockets |
| 158 | +### 6.2 Web Sockets |
151 | 159 |
|
152 | 160 | It is becoming normal that all webpages automatically refresh whenever there is new data available. Think about the live news feeds that tell you when there is a new item, or that there is a new message on twitter. This is all implemented using Web Sockets, where you as a programmer can set up a link between your page and the server.
|
153 | 161 |
|
154 | 162 | Have a go by building a simple full stack chat application with an express websocket server!
|
155 | 163 |
|
156 |
| -### 5.3 GraphQL |
| 164 | +### 6.3 GraphQL |
157 | 165 |
|
158 | 166 | We focused solely on the REST way of building an API, but there is a different way called `GraphQL`. This allows the frontend to define in their query the data that they want to get back. Very cool, but also quite complex. If you are up for a challenge, try to recreate your project using GraphQL (`express-graphql` package is probably the easiest way)!
|
159 | 167 |
|
|
0 commit comments