How to Code Like a Pro (with Dylan Israel)
video description
compliments for the first hour -- then a bit confused; a teacher may have an opinion. I agree when you talk about small objects and classes; inheritance and being aware of consequences in your programming/development tree --> whether it's the coffee-table or a formal meeting -- this will always remain a discussion - you summarize the internet debate in a clear and sympathetic way.-
But the second hour: hop skip and jump without explanation. Elaborate examples where here just the details count. (I know backticks but I am not so sure you are using them in the right way - that is a step back to assembly programming and who wants to do that these days??).-
Waiting for another video and hoping that you take a step back.-
Benny-
P.S. 1,// You recommend not to but I do use comments in my code: e.g.:-
- it makes a difference whether I study through Mozilla or Google - I like to refer and explain my choise. it's all ES?? newest but approaches are different and I like to follow the debates.-
- I always refer to web-sites where I get my info; e.g. Processing (p5.js) is an example. That takes \\ here and there but does not influence the code.-
- Readers / programmers can skip tricks that I use while programming but are a complete independent unit. E.g. I have growing trees in a natural environment; studied and programmed through courses at processing.com; Not an animated GIF but pure JavaScript. This requires (1) reference / thanks to the teacher I started with (2) explanation to the way I implement a -stolen- function and still try to be honest.-
P.S. 2, Hope I am not too harsh - rereading the above - you gave me a good course and a little debate. Keep on with it :)
Date: 2022-03-14
Related videos
Comments and reviews: 9
Rachelle
I watched this even though I've been working professionally as a JS coder. I was hired before I finished all of my training (bootcamp, Freecodecamp, etc.) so I've been anxious about the quality of my code. I'm glad to see that my practices are not too far off what have been suggested here.
Overall, I really liked this video and I'm leaving it with new ideas and feeling relieved for the most part about my code quality.
The only thing I can say though is that I would have loved to see what the best practices are for dealing with chained Promises, embedded callbacks, proper use of async/await and lastly for using middleware functions. Chained promises or embedded callbacks can make extremely ugly code even if it doesn't necessarily mean that the code is unstable. Async/await isn't always the solution: some of my colleagues who have used it saw their functions resolving too early or doing something unexpected and generally had less of an idea how their code worked than when they use Promises. I haven't had time to experiment with async/await so I'm still on Promises unless it's more appropriate to use callbacks. Lastly, the (infamous) next() function... it's great when you can figure out what is actually being called and what the function stack is but sometimes when a person doesn't know the code they're reading, it can be completely obscure what is going on. This is particularly a problem, I find, in Express.js and not so much in front-end frameworks that might employ 'middleware' like Vue-Router.
reply
I watched this even though I've been working professionally as a JS coder. I was hired before I finished all of my training (bootcamp, Freecodecamp, etc.) so I've been anxious about the quality of my code. I'm glad to see that my practices are not too far off what have been suggested here.
Overall, I really liked this video and I'm leaving it with new ideas and feeling relieved for the most part about my code quality.
The only thing I can say though is that I would have loved to see what the best practices are for dealing with chained Promises, embedded callbacks, proper use of async/await and lastly for using middleware functions. Chained promises or embedded callbacks can make extremely ugly code even if it doesn't necessarily mean that the code is unstable. Async/await isn't always the solution: some of my colleagues who have used it saw their functions resolving too early or doing something unexpected and generally had less of an idea how their code worked than when they use Promises. I haven't had time to experiment with async/await so I'm still on Promises unless it's more appropriate to use callbacks. Lastly, the (infamous) next() function... it's great when you can figure out what is actually being called and what the function stack is but sometimes when a person doesn't know the code they're reading, it can be completely obscure what is going on. This is particularly a problem, I find, in Express.js and not so much in front-end frameworks that might employ 'middleware' like Vue-Router.
reply
Tobias
1:27:37 Some of the explanations make me cringe, e.g. what static means: -it essentially means that this is a property or a function on a class (..) and it's not going to be something that you're ever going to necessarily redo- I know what you are trying to say, but thats not what static means. It means the function can be called without instantiating the class, only the reference to the class is needed. Essentially, you end up having a class with only one function that is static. So why didn't you make the class abstract? -Code Like a Pro- for sure, but you should respect basic OOP principles ...
reply
1:27:37 Some of the explanations make me cringe, e.g. what static means: -it essentially means that this is a property or a function on a class (..) and it's not going to be something that you're ever going to necessarily redo- I know what you are trying to say, but thats not what static means. It means the function can be called without instantiating the class, only the reference to the class is needed. Essentially, you end up having a class with only one function that is static. So why didn't you make the class abstract? -Code Like a Pro- for sure, but you should respect basic OOP principles ...
reply
iVuDang
Great video. Some concepts are over my head as I am not experienced enough. May need to revisit later. My takeaways:
- Principles: Searchable, Readability, Understandable.
- Naming of variables should indicate what it does/what it is. A good name would eliminate the need for a comment.
- Books: Clean Code and The Clean Coder by Robert Martin
reply
Great video. Some concepts are over my head as I am not experienced enough. May need to revisit later. My takeaways:
- Principles: Searchable, Readability, Understandable.
- Naming of variables should indicate what it does/what it is. A good name would eliminate the need for a comment.
- Books: Clean Code and The Clean Coder by Robert Martin
reply
moofymoo
idk, take this video with grain of salt, it have good points, but also lot of personal preference.
I'm sick of pointless meetings about indentantion and then doing long crunch time, because half of project time was wasted in 'architecting' endless abstraction layers because SOLID good, man wrote principle in book.
reply
idk, take this video with grain of salt, it have good points, but also lot of personal preference.
I'm sick of pointless meetings about indentantion and then doing long crunch time, because half of project time was wasted in 'architecting' endless abstraction layers because SOLID good, man wrote principle in book.
reply
Raju
You don't have to worry about code formatting like replacing single quotes to double quotes or indentations of your code. Let Prettier do that for you, I believe that this is just wasting a dev's time, rather than focusing on the important part that is solving the problem.
reply
You don't have to worry about code formatting like replacing single quotes to double quotes or indentations of your code. Let Prettier do that for you, I believe that this is just wasting a dev's time, rather than focusing on the important part that is solving the problem.
reply
Matthew
When using vs code you can right click on the variable and select rename symbol. This will rename variables throughout the file. I use this frequently and can be a real time saver when renaming variables that are used in a lot of different places.
reply
When using vs code you can right click on the variable and select rename symbol. This will rename variables throughout the file. I use this frequently and can be a real time saver when renaming variables that are used in a lot of different places.
reply
itech
A decent guy, no bs, just does him and rocks it! he is funny,clued up. I seen this guy go from zero to hero. mad respect. I got your back. All the best my friend,tutor and mentor. Peace out! 'Looks like Elon musk, and just as dedicated as Elon musk'
reply
A decent guy, no bs, just does him and rocks it! he is funny,clued up. I seen this guy go from zero to hero. mad respect. I got your back. All the best my friend,tutor and mentor. Peace out! 'Looks like Elon musk, and just as dedicated as Elon musk'
reply
moofymoo
press -windows key- and -r- key at same time
type -cmd- and press enter
click on that weird black rectangle that shows up
type -color 2- and press -enter-
type -tree- and press -enter-
looks like pro enough..
reply
press -windows key- and -r- key at same time
type -cmd- and press enter
click on that weird black rectangle that shows up
type -color 2- and press -enter-
type -tree- and press -enter-
looks like pro enough..
reply
Rui
0:43 analogy
1:07 sort of like comparing a treehouse to a home
2:57 what is a -linter-
4:28 example
6:04 -var- is forbidden, use -let- for variables and -const- for constants
1:08:50 SOLID principle
reply
0:43 analogy
1:07 sort of like comparing a treehouse to a home
2:57 what is a -linter-
4:28 example
6:04 -var- is forbidden, use -let- for variables and -const- for constants
1:08:50 SOLID principle
reply
Add a review, comment
Other channel videos
