Code Like a Pro : Linters | How to Write Code Professionally (With Examples)

preview_player
Показать описание
Code Like a Pro : Linters | How to Write Code Professionally (With Examples)

► MY COURSES
My Courses with huge discounts:

► MY MERCH
My Coding Merch - Shirts, Mugs etc.

► BOOK RECOMMENDATIONS
- The Complete Software Developer's Career Guide:
- The Total Money Makeover
- Clean Code

► AFFILIATE LINKS FOR PRODUCTS I LOVE:
- Check out items I love on Amazon
-Humble Bundle (Low price games, books, courses etc.)
-Robinhood - Trade Stocks App (Sign up and get 1 share of stock valued between 5 and 200 dollars)
-Acorns - Easy Investment Portfolio (Sign up with my link and get $5 when you deposit)

► DONATE & SUPPORT
- Paypal

► MENTORING
- Tutoring, Mentoring and Course Walkthroughs available:

► SOCIAL MEDIA
- Patreon
- Code, Tech and Caffeine Facebook Group
- Twitter
- Website
- Instagram
Рекомендации по теме
Комментарии
Автор

on VS Code, just use aufoFormat(alt + Shift + F). Would do most of these.
Also, I think the problem with the CSS declaration was that you used ":" instead of "=". Good job! Love your channel!

finnfrican
Автор

Looking forward to the progression of this series. Thanks for your ongoing work on this side-side-project Dylan.

somethingwitty
Автор

Love this series thank you for starting it. What are some of your favorite plugins for VS code?

TheBrettmchatton
Автор

I did not know most of this, very useful.

empiricistsacademy
Автор

Thanks Man well i dont have that app but i have sublime text 3 Thanks New suscriber!!

assasingtroll
Автор

ESLint and Prettier (format on save) for me.

Heffsta
Автор

So I just spent a few hours setting up ESLint with the AirBnB settings and let me just say that it was worth it.

the rules no-param-reassign and no-use-before-define still need to be followed but I'm not sure if I agree with those rules, or maybe I don't understand how to deal with them yet.

no-use-before-define makes it so you cannot follow the 'top-to-bottom' principle from Clean Code because it complains when you do:
const higherLevelFunction = () => {
// stuff
lowerLevelFunction();
// more stuff
};
const lowerLevelFunction = () => {
// compute something
};
// Bottom of file...
higherLevelFunction();

no-param-reassign makes it so you cannot do stuff like:
someNodeList.forEach((el) => {
el.style.display = 'none';
});

EddyVinck
Автор

Please make one video for visual studio code in which please explain some important tool which are useful for developers

artisticarina
Автор

I totally thought const was for constant and should be used for variables that wont change.

Bobbidigi
Автор

To get high salary package in an IT company which programming languages should I learn...plz reply

kedaralande
Автор

13:51 I think you just removed the code that was supposed to shuffle the answers.
Now the correct answer is always the first one.

mudshark
Автор

Oh yeah, That code looks familiar? lol

Bobbidigi
join shbcf.ru