I was just introduced to Yare.io. Its pretty sweet. It helps you practice your Javascript skills while doing something really fun.. Anyone learning should check it out. I've been streaming it on twitch. I'm pretty knew to it but if you have questions or just wanna see it being played come check it out. I think people new to Javascript would really benefit from the game.

This video is just a friendly hello to say I have not forgotten this tutorial series and was refactoring some things to work better before I shared them in a tutorial. I have finished what I planned for the next 10 tutorials and decided to show a video of some things to come, which include enemy pathfinding using A*, merchant logic to buy things within the game, item drops from the enemies, expanded map to include the whole overworld, and the beginning and hopefully the completed start/inventory screen and logic by tutorial 22. Hope this video finds you well and look forward to getting back to recreating Zelda with you.

Link to video teaser:

https://www.youtube.com/watch?v=uZbmhJjCRT8

The whole tutorial playlist can be found here:

https://www.youtube.com/playlist?list=PLGvgepw5e1awJDB8KynZiM5ZL1SrqIwUr

We are hiring at my company, and I saw a resume today from a young developer fresh out of bootcamp. The resume listed a couple of projects (probably school assignments) but had no links to the code. She did have her github, but almost no actual code she wrote was on it. It was mostly just untouched forks of Bootcamp homework assignments.

I taught myself JS and got hired with no relevant experience, and I was told after the fact that having code samples online made them take me more seriously than they would have otherwise.

You don't have to have an amazing personal project you've completed. If you are doing /r/dailyprogrammer challenges, or Project Euler, put your solutions in a project folder on Github. Something is better than nothing. You don't have to over-represent your skills, but you should still represent them a little bit. Personality may be enough to get you an interview and a takehome challenge, but you need code samples online to get that E for Effort, and the E also stands for Employment.

That is all.

it's response:

Certainly! Promises are a way to handle asynchronous tasks in JavaScript.

Imagine you have a toy box, and inside the toy box are different toys. Some of the toys are easy to get to, like balls or blocks. But other toys, like puzzles or games with lots of pieces, are harder to get to because they are buried under the other toys.

Promises are like those harder-to-reach toys. They represent an action that is happening in the background, while the rest of your code keeps running. You can think of a promise as a "placeholder" for a value that you don't have yet, but will have in the future.

Here's an example: let's say you want to get a toy car from the toy box, but it's buried under a bunch of other toys. You could ask someone to go and get the toy car for you, and while they are doing that, you can keep playing with the other toys. When the person comes back with the toy car, they will give it to you and you can start playing with it.

In JavaScript, we can use a promise to represent this action of getting the toy car from the toy box. We can use the .then()method to tell the promise what to do when the toy car is retrieved. Here's how it might look:

const getToyCar = () => {

return new Promise((resolve, reject) => {

setTimeout(() => {

resolve("toy car");

}, 1000);

});

};

getToyCar().then((toy) => {

console.log(`I got the ${toy}!`);

});

In this example, the getToyCar() function returns a promise that will resolve with the value "toy car" after a delay of 1 second. The .then()method is called on the promise and logs the message "I got the toy car!" to the console when the promise resolves.

Promises are useful for handling asynchronous tasks because they allow you to chain together multiple asynchronous actions and handle the results in a predictable way.

I hope this helps explain what promises are and how they work! Let me know if you have any questions or if you would like more information.

Exact dialog: "Could you teach me javascript promises like you teach to a child? "

Not sure if this is the right place to even post this, but can somebody explain to me why do I have to know E V E R Y T H I N G just to land a job as a JUNIOR, I repeat, J U N I O R front-end developer?

I applied for a JUNIOR FRONTEND developer job, and they gave me a pre-interview assignment, in which they want me to complete a FULL STACK PROJECT using databases, backend frameworks, and all kinds of back end libraries and stuff. Granted I did say I can work with node.js and express, and I can, but I am not a back end developer, and I am not applying for a back-end position, or a full stack developer position, so why do they want me to know all of this? My back-end knowledge is limited to things like setting my own server, and doing stuff like chat apps with socketio. It's not my area to know how to work with databases, and the whole bunch of frameworks and libraries that goes with it.

I am curious how do they hire backend developers? Do they just hire a bunch of junior frontend developers do their job? If I can do a full stack projects, why on earth should I be applying for a JUNIOR frontend position? Shouldn't I be just given a full stack position? And if I need to know both frontend and backend just to be hired as a JUNIOR frontend, then I can only imagine what I would have to know to be a senior. Somehow I really doubt that actual backend developers know anything about frontend development. It seems that the frontend people need to know both sides, while the backend people just the server side.

This is so frustrating and annoying, because every time I invest time in learning something new, like React, basics of node.js and stuff, they just keep wanting more and more. This is BS.

Been working on the exercises from The Odin Project, was going great and my confidence was building after each one that passed all the tests. Then I decided to look at a solution for a project I had already completed and it completely demoralized me when I saw how simple their solutiuon was when compared to mine. Already told myself that if I had a better understanding of array methods it would be better but now I know my day is probably done as far as studying.

Does this happen to anyone else?

Edit: went outside for a little bit and I feel better. Was thinking about some PHP I wrote last year and how horrible I thought it was when I looked at it again last month. Im sure I’ll come back to projects im doing now and feel the same, also I am doing what many suggest, no matter how I feel about my solution vs theirs I always read through the solutions I look at and make sure I try to understand what they are doing and why.

These Courses are available for free for a short period of time so redeem them as fast as you can

JavaScript Basics to Advanced - FREEAPR1

JavaScript Ultimate Course - TRY10FREE42103

Modern JavaScript for React JS - FREEAPR1

If this isn't the right sub lemme know. But I recently moved from automation qa to a dev role in react native. And I'm looking for resources to help me get up to speed in react and mobile dev. Any resources would be appreciated :)

Watch the full Youtube video