Exactly 💯

Glad to hear that!

@@WebDevCody learning the small things makes so much impact , it’s not about getting the job i feel it’s more how curious i am towards this and eager to learn as much as i can and seeing you build small stuff makes me so much motivated and just build stuff

it's build into mac os for taking screenshots

I'd rec learning vim motions, speeds up that kind of thing a lot once you get used to it. Awkward as hell to start with though but worth powering through it.

I have a few videos on my vs code shortcuts I use

In description

Because the data is fetched when the form is submitted. Why do you think we’d need an effect?

@@WebDevCody i didn't think we needed one, i kinda just didn't understand why we dont need it :D i was under the impression that i have to use useEffect every time i want to fetch data.

@@battimi2647 nah useEffect is whenever you want react to watch a state variable and run a side effect when that variable changes. It’s similar to a vue watch or angular watcher. It’s also useful when you need to run code when the component mounts or rerenders, which is usually what we see, fetch data from api on mount

In description

how about making it like making it autocomplete where the results are coming up as the user types without hitting the submit button

Every company has different requirements for a junior. I personally want to verify the person can at least code something basic

@@WebDevCody As long as is not through live coding, otherwise your screening for other things besides dev skills, which aren't always needed. If the job doesn't demand being able to code under high pressure (which no one should under right management), then live coding is pointless. Live coding puts the person interviewing in such a vulnerable state that it takes them back to sort a professor/teacher relation with the interviewer.

@@JoseRodriguez-zt5it what should an interview consist of if not quizzing their technical abilities? There are people who can easily memorize terms for interviews and not know how to solve real problems in code.

Since I'm aspiring to be junior dev in some near future i asked my friends that already are devs how junior interviews look they all agreed it's completely different from company to company. Some can even hire you if you didn't do that good but they have seen that you do have potential and understanding of what your doing they will be willing to teach you and invest in you, some don't even require react or anything other then stock js but on the other hand some have almost same requirements for junior as for senior they just want to pay you less...

@@WebDevCody you could test by giving them a technical challenge to do within a certain time frame, like 2-3 days. Then review the code they deliver, and confirm they wrote the code by having a call and ask them questions about the implementation. I think it's a way more accurate indication of how a dev will actually work than doing something like a React tic tac toe in a live coding scenario.

you can create types which you use in other places of the code base to add to function parameters so that typescript can verify if you are passing the proper things around

Fetch data when data should be fetched. If the api doesn’t need to be hit until you click a button, you don’t need an effect

Why would I need to? If the fetch happens on the form submit, why do you think it needs to be in an effect?

Since I saw many developers wrap it up with useEffect i dug deeper and found out it's side effect, I guess we need an useEffect only when we fetch initially let's say on on page load

Awesome! Hope you did well

@@WebDevCody Yes! Ill start next month :)

I typically don’t work that way so I don’t want to record a video demonstrating a way I don’t actually work

if you are building a SPA, then yes I would, or use Next.js

Thank you!

@@opie0818 exactly what i was thinking

setTimeout. Put up a spinner before then.

That would be very expensive because you would have to make an API call on every keystroke.

no clue what you just wrote.

@@WebDevCody me too. Probably using a different react.

Never met someone so butt hurt from interview questions in my life

Not too sure, maybe questions deeper about react performance, design choices for building abstract components, questions on order of execution for life cycle events and hooks

Probably, or my kids 😂

That’s actually bad practice. If you use index your stuff can easily render incorrectly if you add or remove from your array. I made a video on that issue

@@WebDevCody Good to know...thanks!

Bad practice? Since when?

The react literally say this: “In most cases, we recommend using controlled components to implement forms”

​@@WebDevCody Maybe 'bad practice' was too harsh there. I meant that chaning it to ref will result in small performance gain, because component doesn't need to rerender itself everytime you type.

I avoid uncontrolled inputs. But if that works for you that’s cool. The react docs explicitly say “In most cases, we recommend using controlled components to implement forms”, so if you want to do something non standard that’s fine I guess

@@WebDevCody Do you have a specific reason?

@@lukasvaic7159 because now you’re living in a world outside of a react and doing vanilla dom manipulation for no good reason. Just use vanilla js if you want to manipulate dom objects manually

​@@WebDevCody The performance improvement is significant when employing the use of uncontrolled inputs. There's a reason why the most used form library (react-hook-form) embraces uncontrolled inputs.

@@John-mj1kk significant is a stretch for an average form with validation. It maybe saves you 2ms for a form with 20 inputs

I though vite is fast because it uses esbuild under the hood and CrA uses webpack

@@WebDevCody That's another reason! There's a lot of stuff that makes CRA slow lol

Not sure why that seemed to have bothered you enough to leave a comment 😂

@@WebDevCody I'm having a rough time and it comes out in weird ways.