Turn Bad Code into Good Code (Javascript, TypeScript, Node, Jest, unit Testing)

Wow it was a really helpful video, especially the testing part since i was always skeptical of testing and just trusted my eyes and the console logs😅. Could you please also make a video about file or folder structures? Whenever i visit an open source repo, they have folders like utils, lib etc. I know it differs based on each project but I think it would be helpful to have a middle ground on where we should put our files and why the folders are named as such.

I have a question, when you removed the data to the test file, where did you get data to test the code after being removed?

nice video to motivate me to write clean code

thank you!
how did you become so good at unit testing?
it seems there isn't a whole lot of content out there that goes beyond the basics.

that was pretty interesting

outdated..

This is actually so helpful

Great explanation !. What is the link from github repo ?

Everyone keeps telling me to learn testing, so I’m super thankful for this vid :)

what is vs code theme name?

Dude, your videos are on fire! 🔥It almost makes me want to switch to full on TypeScript already over vanilla JS.

omg and testing and refactoring so much information , thank you

I wish to see more videos like this from you. Nice job.

This content is so great. I'm a mid node.js dev, i wish i knew this channel when i was getting started. Finally understood the purpose of testing :D

Not all heroes wear capes ;)! No, but seriously I'm starting to binge on your videos and I feel like you're one of the few yt lecturers who is so practical and actually helpful. I'm at the stage of my learning, where I struggle precisely with writing more readable, maintainable code and proper tests and you manage to choose example(s) easy enough to follow, but complex enough to explain the issues. I always found the other yt tutorials lacking the comparisons between good and bad code/ good and bad practice. It always seemed like something you can only improve if you're getting some sort of feedback on your program irl. I look at my code and I am fully aware it looks kinda all over the place, some functions are way too long, but what do I do exactly,, that's the question. It's hard to keep track of all the things you need to do >in the first place<, when starting to write a more complex app, so you don't end up dreading the smallest refactor afterwards, because everything starts to get convoluted and messy, and just breaks x'd. So thank you so much, really, you're great!

good and old null students, yeah. always the troublesome kind. null people.

Really amazing video! Subscribed :)

thank you so much this is the content i m looking for ♥

Exactly what developers should watching

this was supeeer helpful, thanks!!! Please keep doing more videos like this one!!!!

The reason you shouldn't export a private function to test it is so you avoid making refactor a burden.
If you export "implementation details"; there's high change this function could just be reused in other places as a utility function for me, and it might be the case for your "getAverageCourseGrade", it could just have been less aware of it's context, and just have been "getAverage(numbers: number): number"

It is sooo helpful, thank you

Beautiful and helpful. You thought we were going to lose interest but we were impressed.

Great video!

That is actually really helpful. I'm a typescript noob, and you pointed all the problems i definitely still have in my code.

never watched your video before, but this one made me surprised. A lot of important things in just one video. Subscribed!

Great video! Testing is so important, I've been trying to include more testing in my videos.

Helpful human being, missed you sir

Good job babe!!!!!! What a coder!!!