If you've found this useful in anyway, I'd really appreciate sharing it where you can so that more people can enjoy this resource! Watch out for a personal video I'm making on my own journey and how I changed career in my 30s from boring monotony to an exciting software engineering role. If ever you needed motivation or wanted my own specific advice on how to become a self-taught developer, then you make sure you don't miss it. Will be available next week!
@@sansamman4619 : You statement about Indian accent is very unfortunate. I feel sorry for learner's like who instead of focusing on the message focus on the messenger especially when things are given free.
@@manojshetty4 I don''t understand what is meant when it's said "It's free so you shouldn't say a thing about it" , it's free, so what? I don't like it! The guy makes money from it even if it is free! My point is that, since they make money, they should try to make something that's the best they could offer for their own good. I stated how I truly felt, it's completely normal to dislike an accent, and it is nothing "unfortunate", the voice really does matter when it comes to sending your message, and I think that the message that Indians try to make their voice more like the English accent, I think if they put more effort into it the message would be sent more fluently. It's not my fault that I get headaches when I listen to the Indian accent in the first place, I would love to listen to them without getting a headache honestly, it's just that I am that way and I am the one who suffers from it since Indians have very useful content...
A good explanation that requires a basic grasp of object orientation. Do not expect to understand by passively watching instead of actively learning by experimenting with your own classes, using trial and error, and becoming frustrated when things go wrong as well as elated when they go right!
I concur with other comments in that, the way you explain is geared towards people with technical knowledge already, but those type of people are less likely to need to watch this video. The target audience isn't clearly defined. I think it's more useful to show us exactly why the init method is useful compared to just using normal definitions.
I'm conflicted. On one hand, I'm happy you made this video, obviously bc I'm watching it, but on the other hand, it's not super helpful -- I think you need to take a step back and think about what you're actually saying and to whom you're speaking to b/c those who are watching this, may find it hard to follow, and the folks who could easily understand this content, aren't watching.
Agreed. I really appreciate the effort, but most people ( could be wrong ), wont understand a lot of your terminology. If this video is for more experienced programmers then I'm probably in the wrong place. But thanks for making it anyway.
I highly disagree with that, I'm still very much a beginner in this language and after watching this a few times and making my own examples, I understood perfectly. @Live Code this video is genius, keep up the good work
Agreed. I had read a few tutorials prior to watching this and I feel like if I hadn't, I would've been lost and needed a few play-throughes. That being said, I did find the video helpful.
I have to say, this video was incredible! I'm in uni, and I'm doing a class on data analytics and comp. modeling, we'reusing python and just started with OOP and we were introduced to classes and objects. It started out okay, but I quickly became confused when we started using __init__ and self, it became like a foreign language fast. Your video got straight to the point, I didn't even know instantiated objects could have their OWN properties and methods, the idea that you just showed me of __init__ and self being used to deliver class attributes and methods to objects instantiated by that class clears almost ALL of my doubts. Young programmers need more educational videos like this!
Simple and straightforward treatment of a somewhat confusing topic. I watched it about three times and now understand 100% of what you said. Off to start making my own classes. Thank you.
I gotta agree that although the content is obviously well articulated, I have trouble following it, as you don’t pause enough and it’s a bit robotic in its delivery. Good for those who know something about classes already maybe but not for noobs
It took me a few times of watching it but I finally wrapped my head around it. Just started 3 days ago and no previous machine language experience. Big thanks 👍🏼
@@BethanyLowe8773 What are you talking about he is explaining every step: - A *class* is like a factory pattern: - You take the "pattern" called *class* and build a "copy" object of the class by assigning the class call to a variable. This "copy" is called "instance". - The instance inherits all attributes and methods from class. - The instance also holds its own "namespace" which means you can access instance attributes and methods from the instance itself without having to reference the parent class. - To build this separate namespace on every instance you use a constructor method on the class which need 1 argument widely called _self_ . - _self_ will reference the instance itself every time you create a new object from the "parent" class. But how is this required behavior explained? - This means, internally every time you call an instance method you are calling the parent class and passing the instance to it so the class method takes the instance as a parameter and That's why class methods needs _self_ as a required argument. The computer takes advantage from reusing the class logic and passing only the changed values on the instance attributes so all the logic is not replicated. You must use _self_ on constructor and every method to keep this logic only referenced and not replicated in memory. So by calling a instance method, python takes the parent class feed it with the instance changes and reuses the methods replacing _self_ with the instance changes and executing the logic.
@@TyrannicalNoob Well some TI concepts could be trivial to be explained on a few lines. But you cannot expect to understand OOP topics relaying on heavy complex memory allocation and reuse of resources, in a minute. Those things occurs on "the background". Those background clockwork pieces need some language keywords like "self", ___init___ etc to work. While this explanation on the video is still "high level" you are expected to research about basic terminology to understand this video. I don't want to be tough with this words but this is not a Candy crush topic you can explain in 30 seconds for guitar hero players. This is playing classic guitar and practicing daily with commitment. You shoud come to this video when you actually know basic OPP terminology like Class, instance, parameters, arguments and methods. Draw every single concept of it. This terminology is not buzzwords intended to confuse new people by the "draw a horse" effect. Is much like you need words to simplify the act of differentiate things like parameter which is "any" from argument because you cannot say "hey take the value of the parameter as input on this function call" every single time. This video topics needs specialized terminology as shortcuts for complexity and that is what we need to hard work daily to build that terminology understanding.
I'm sure this guy gets this all the time, but this is excellent. I'm taking a course that didn't explain this very well, but this patches some holes in my understanding.
it was hard to follow: in the dialog few words has repeated so much and it made the video, hard to follow plus the computer_like voice and the speed, low pauses and ....
I agree, it's good but too fast scrolling like it's fast forwarded. You talk to fast as well. Plus some of the naming kinda confused things a bit. Also would like to see more in depth things. Maybe that's in other videos though
when i just listened it, quite confusing as all method name so similar, but after i step by step followed, (cause u can see the actual result in real time),this video does help me clear how to use the 'self, class'thing. i suppose it is just not easy to learn . not his problem,
I was unsuccessfully trying to understand it from reading different articles and you just explained all errors I was getting when playing with it in one video! Shut up and take my money!
Very nice explanation of 'self' I would add that each object (instance) has its own data, but all all instances are using the same methods code and this is the reason that self needs to be passed to let the methods know on which data they should access/operate-on
This is a good explanation. Even though I was being the lazy student and didn't follow you writing my code, you cleared many little blackboxes left from other, more skippy explainations on classes. _Init_, self, single-instance attributes... Now makes a lot of sense
Dude you have explained everything so well thank you. The only thing I would say is maybe take a pause after a couple of lines of code. I had to pause the video myself to actually read what is going on, specifically in parts where an error would occur and you would keep going.
Nice video! The whole concept is fairly straight forward once you know the specific 'fancy terminology'. The most confusing thing to wrap your mind is all the i.e class variable, instance class, instance attributes, instance objects
I guess we're all learning together. I'm learning how to best get the knowledge of Python that I have across to you. I'm certain that the quality of the tutorials will continue to increase over the next year.
after i step by step typing it, do learn something. it is 1 step deeper than an ordinary 'class' tutorial.just what i want as a fresher. thanks a lot for make this video :) ---from china
I just found this video today and Ive got to say that I've gone to StackOverflow and multiple sources but never really understood the explanations that well. But man are you good at explaining this topic. Amazing work, I finally understand self and __init__ definitely subscribing. I was gonna say if you could do one on Lambda but you already have it done on to that one.
super video made. Suggestion for NOVICES: 1) set playback speed to .75 and type in a similar code in some other tab to check for yourself. 2) pause his video and let the concepts sink in.
before watching this video, i have no idea wtf they taught me earlier but now you just killed it. keep up this good work, you might help lots of people like me.
I'm listening to this at 1.25 speed because the instructor speaks really slowly and it actually makes it harder for me to follow along. Other than that, great explanation!
I found this super helpful, I'm somewhat new to programming and I had no Idea why self kept cropping up when I was looking at sample code, this is exactly what I was looking for, thank you.
I asume its a good and valid explanation and i like that it goes in depth but i find it rather confusing. But im a beginner so maybe thats the problem. Im at least less confused then i was before i guess its just a lot to take in for a non native speaker with all of these new terms and so much information in so little time
A very nice resource, based on the other comments maybe this is the most helpful for people who are not complete beginners, but like another commenter, I've struggled to understand this from SO and this was super helpful. Thanks for sharing mate!
How to take multiple user input in an oop? User input would be put in a list. Specifically, the user 's input would contribute to the polynomial function python code.
My understanding of the video: 1. Dundee methods are the first ones to be called when a class is instantiated. 2. so __init__ is called which contains initialization steps. 3. Whenever a class object is called, the instance is always passed as the first argument. "self" refers to that instance of the class (object) which is being passed to the method reason why define "Self" in init method. 4:07. 4. If a class object needs to call a method of the class, it needs to have "self" as the first parameter. 5. Methods of the class can still be accessed even without "self". But not by class objects. But only by the class namespace itself. eg: a.method() won't work. But class_name.method() will still work
I am new to python, been learning for a few months. I got completely lost watching this. Thank you for making the video though. I gave a thumbs up. However, as many people mentioned in the comments, consider your audience. If your audience is me.. your explanation is not layman enough. I dont understand self nor init still. If its people that know python, does it provide any value to them? Idk, im not in that camp. But Thank you! Please Make another one for neebs like me!
Been programming in C for 40+ years and like you totally confused. Give this cryptic mess a miss and learn C it'll be far more productive for you and without most of the cryptic mess that python seems to have for a so called modern and beginners language ( Not ).
3:27 What do you mean by "overidden" in this context? do you mean that the __init__ method you used overode the invisible one thats created every time a new class is created? Or that specifying that the emthod prints "Hi" somehow overode something else?
Stupid question: Is „self“ always used when working with classes or are there examples where „self“ is better not be used (and why)? -> If self has always to be used, then why make it mandatory to declare it?
This was an amazing explanation! Thank you! I am taking Meta's Back End Develop certificate right now and the lesson they had on this(along with a good few other ones) didn't explain the concept very well, so I was a bit confused. But I have a much better understanding now!
Thank you so much for this!!! Your explanations are cristal clear! I hit suscribe button so enthuasistically like never before (an odd number of times)
Amazing. You've explained this concept better than anywhere else, and I was having trouble understanding it until this video. Thank you - I'll certainly be sharing your channel.
first time watching didnt get anything, we i rewatched it i understood everything . thank you bro , and can you do like 10s breaks between each topic hahahahaha
I have a question. I want to use 20 element or node labels(numbers) in the python script. I am trying to prepare a code with a loop that code checks these elements or nodes during 10 steps and when each of those nodes or elements temperatures reaches a certain amount for example 500 C, the code saves the stress and strain results related to those elements or nodes. I want to know do can I refer to element and node labels and how can write this kind of code.
I have just started learning Python from "Automate the Boring Stuff with Python" and am a beginner and I don't understand this at all. How do I fix this knowledge gap? I don't even know where to start.
![What exactly is 'self' in Python? [Easy explanation]](http://i.ytimg.com/vi/JH4q65dZPvY/mqdefault.jpg)
If you've found this useful in anyway, I'd really appreciate sharing it where you can so that more people can enjoy this resource! Watch out for a personal video I'm making on my own journey and how I changed career in my 30s from boring monotony to an exciting software engineering role. If ever you needed motivation or wanted my own specific advice on how to become a self-taught developer, then you make sure you don't miss it. Will be available next week!
Thank you very much! My brain hurts so much when i hear the Indian accent, you are my saviour, your voice is awesome
@@sansamman4619 : You statement about Indian accent is very unfortunate. I feel sorry for learner's like who instead of focusing on the message focus on the messenger especially when things are given free.
@@manojshetty4 I don''t understand what is meant when it's said "It's free so you shouldn't say a thing about it" , it's free, so what? I don't like it! The guy makes money from it even if it is free! My point is that, since they make money, they should try to make something that's the best they could offer for their own good. I stated how I truly felt, it's completely normal to dislike an accent, and it is nothing "unfortunate", the voice really does matter when it comes to sending your message, and I think that the message that Indians try to make their voice more like the English accent, I think if they put more effort into it the message would be sent more fluently. It's not my fault that I get headaches when I listen to the Indian accent in the first place, I would love to listen to them without getting a headache honestly, it's just that I am that way and I am the one who suffers from it since Indians have very useful content...
Hello @Live Python. How to type double underscore in python . Thanks
@@abdullahmalik1006 I'm not OP but it's simple, just find the single underscore on your keyboard i.e. '_' and type it twice: '__'. Does that help?
A good explanation that requires a basic grasp of object orientation. Do not expect to understand by passively watching instead of actively learning by experimenting with your own classes, using trial and error, and becoming frustrated when things go wrong as well as elated when they go right!
eat my shorts i never programmed before watching this and now i can easily make AI programs that can piss and fart
Absolutelly
I love learning programming that way
This is what is happening to me
I concur with other comments in that, the way you explain is geared towards people with technical knowledge already, but those type of people are less likely to need to watch this video. The target audience isn't clearly defined. I think it's more useful to show us exactly why the init method is useful compared to just using normal definitions.
I'm conflicted. On one hand, I'm happy you made this video, obviously bc I'm watching it, but on the other hand, it's not super helpful -- I think you need to take a step back and think about what you're actually saying and to whom you're speaking to b/c those who are watching this, may find it hard to follow, and the folks who could easily understand this content, aren't watching.
Agreed. I really appreciate the effort, but most people ( could be wrong ), wont understand a lot of your terminology. If this video is for more experienced programmers then I'm probably in the wrong place. But thanks for making it anyway.
I highly disagree with that, I'm still very much a beginner in this language and after watching this a few times and making my own examples, I understood perfectly.
@Live Code this video is genius, keep up the good work
Use pause and rewind and a pen and notepad. I did and got it after 4 views
Agreed. I had read a few tutorials prior to watching this and I feel like if I hadn't, I would've been lost and needed a few play-throughes. That being said, I did find the video helpful.
I was gonna say exactly this. In a nicer way though
3:48 - Thumbs up for "WOTS GOING ON ?"
I have to say, this video was incredible! I'm in uni, and I'm doing a class on data analytics and comp. modeling, we'reusing python and just started with OOP and we were introduced to classes and objects. It started out okay, but I quickly became confused when we started using __init__ and self, it became like a foreign language fast.
Your video got straight to the point, I didn't even know instantiated objects could have their OWN properties and methods, the idea that you just showed me of __init__ and self being used to deliver class attributes and methods to objects instantiated by that class clears almost ALL of my doubts.
Young programmers need more educational videos like this!
Yeah but we don’t need Self when calling the methods. It’s a brain fart bastard child of python that adds only redundancy and confusion.
this video is a staple in how I know what self is, every time I come back to this video I have learned more.
Simple and straightforward treatment of a somewhat confusing topic. I watched it about three times and now understand 100% of what you said. Off to start making my own classes. Thank you.
I gotta agree that although the content is obviously well articulated, I have trouble following it, as you don’t pause enough and it’s a bit robotic in its delivery. Good for those who know something about classes already maybe but not for noobs
The feedback is really appreciated and I'll be sure to work on the points you've raised for the forthcoming tutorials. Thanks!
It took me a few times of watching it but I finally wrapped my head around it. Just started 3 days ago and no previous machine language experience. Big thanks 👍🏼
"how to draw an owl: first you draw two circles. Then, you draw the rest of the owl."
Perfect analogy! The first half made sense, then he started saying a load of technical terminology without reference.
@@BethanyLowe8773 What are you talking about he is explaining every step:
- A *class* is like a factory pattern:
- You take the "pattern" called *class* and build a "copy" object of the class by assigning the class call to a variable. This "copy" is called "instance".
- The instance inherits all attributes and methods from class.
- The instance also holds its own "namespace" which means you can access instance attributes and methods from the instance itself without having to reference the parent class.
- To build this separate namespace on every instance you use a constructor method on the class which need 1 argument widely called _self_ .
- _self_ will reference the instance itself every time you create a new object from the "parent" class. But how is this required behavior explained?
- This means, internally every time you call an instance method you are calling the parent class and passing the instance to it so the class method takes the instance as a parameter and That's why class methods needs _self_ as a required argument.
The computer takes advantage from reusing the class logic and passing only the changed values on the instance attributes so all the logic is not replicated. You must use _self_ on constructor and every method to keep this logic only referenced and not replicated in memory.
So by calling a instance method, python takes the parent class feed it with the instance changes and reuses the methods replacing _self_ with the instance changes and executing the logic.
@@moracabanas I understand what ur saying but u cannot be serious lmfao
@@moracabanas full marks for effort!
That’s great what you did here
@@TyrannicalNoob Well some TI concepts could be trivial to be explained on a few lines. But you cannot expect to understand OOP topics relaying on heavy complex memory allocation and reuse of resources, in a minute.
Those things occurs on "the background". Those background clockwork pieces need some language keywords like "self", ___init___ etc to work.
While this explanation on the video is still "high level" you are expected to research about basic terminology to understand this video.
I don't want to be tough with this words but this is not a Candy crush topic you can explain in 30 seconds for guitar hero players.
This is playing classic guitar and practicing daily with commitment.
You shoud come to this video when you actually know basic OPP terminology like Class, instance, parameters, arguments and methods.
Draw every single concept of it.
This terminology is not buzzwords intended to confuse new people by the "draw a horse" effect.
Is much like you need words to simplify the act of differentiate things like parameter which is "any" from argument because you cannot say "hey take the value of the parameter as input on this function call" every single time.
This video topics needs specialized terminology as shortcuts for complexity and that is what we need to hard work daily to build that terminology understanding.
I'm sure this guy gets this all the time, but this is excellent. I'm taking a course that didn't explain this very well, but this patches some holes in my understanding.
it was hard to follow: in the dialog few words has repeated so much and it made the video, hard to follow plus the computer_like voice and the speed, low pauses and ....
I agree, it's good but too fast scrolling like it's fast forwarded. You talk to fast as well. Plus some of the naming kinda confused things a bit. Also would like to see more in depth things. Maybe that's in other videos though
when i just listened it, quite confusing as all method name so similar, but after i step by step followed, (cause u can see the actual result in real time),this video does help me clear how to use the 'self, class'thing. i suppose it is just not easy to learn . not his problem,
I think this explained it better:
ruclips.net/video/M1BAlDufqao/видео.html
I was unsuccessfully trying to understand it from reading different articles and you just explained all errors I was getting when playing with it in one video!
Shut up and take my money!
"Dunder init"? I keep waiting for a reference to the Office... But it never comes
__mifflin__(self):
Exactly my thoughts hahaha
@@111ark underrated reply
That's what she said...
Very nice explanation of 'self'
I would add that each object (instance) has its own data, but all all instances are using the same methods code
and this is the reason that self needs to be passed to let the methods know on which data they should access/operate-on
This is a good explanation. Even though I was being the lazy student and didn't follow you writing my code, you cleared many little blackboxes left from other, more skippy explainations on classes.
_Init_, self, single-instance attributes... Now makes a lot of sense
Single most concise video on the internet for starters!
You just confused me more lol
but the way u talk, daaaaaaaaaaaaaaaaaaaaaaaaaaamnnnnnnnn keep up the good work
Perfect pacing. I feel many other programming videos drag on a good bit but this video got straight to the point.
Finally someone explained it properly, thank you very much!
Dude you have explained everything so well thank you. The only thing I would say is maybe take a pause after a couple of lines of code. I had to pause the video myself to actually read what is going on, specifically in parts where an error would occur and you would keep going.
@ ;-) Parentheses are curved ( ), brackets are square [ ], and braces are curly { }. Thanks for making! I learned some stuff!
Nice video! The whole concept is fairly straight forward once you know the specific 'fancy terminology'. The most confusing thing to wrap your mind is all the i.e class variable, instance class, instance attributes, instance objects
one of the few tutorials that says things correct. Objects are created with the __new__ method and initialized with __init__
I have been following this since the first 3-4 videos and I love them. But videos that you can actually follow along are way way better.
I guess we're all learning together. I'm learning how to best get the knowledge of Python that I have across to you. I'm certain that the quality of the tutorials will continue to increase over the next year.
@@LivePython Yeah, I know. I'm starting an educational channel (not this account) and it is pretty hard. But you are doing already a good job
after i step by step typing it, do learn something.
it is 1 step deeper than an ordinary 'class' tutorial.just what i want as a fresher. thanks a lot for make this video :) ---from china
OMG Thank you. I've been struggling to get my head around this for hours. Great explanation.
I just found this video today and Ive got to say that I've gone to StackOverflow and multiple sources but never really understood the explanations that well. But man are you good at explaining this topic. Amazing work, I finally understand self and __init__ definitely subscribing. I was gonna say if you could do one on Lambda but you already have it done on to that one.
Thank you, finally understood how it works. I don't know why people say you are not clear in the second part
super video made. Suggestion for NOVICES: 1) set playback speed to .75 and type in a similar code in some other tab to check for yourself. 2) pause his video and let the concepts sink in.
Thanks for the suggestions for novices and hope you're enjoying our other videos as well!
As scattered as this massively ADHD explanation was, it's still the best one I've come across so far. So there's that.
Fantastic work. Really great succinct explanation - I have been dabbling in classes but never really got it until now!
Really appreciate it! Any other topics/concepts that you would like covered?
I hope you pick back up where you started, this channel has a lot of potential - great videos.
Good explanation. Felt like Dwight when I googled this question, but after this video, I'm back to feeling like Jim.
before watching this video, i have no idea wtf they taught me earlier but now you just killed it. keep up this good work, you might help lots of people like me.
my long time doubt cleared, than you so much....
Awesome video! Thank you!
I feel more confused after watching this video. But thanks for making it none the less.
Thanks for this explanation. This just cleared my issues with __init__ and made me even learn more on how does class work.
For me it is good. It requires some knowledge to understand which I have so thumbs up
I always only knew how to use it but never really understood why, your video helpsssss a lot
I'm listening to this at 1.25 speed because the instructor speaks really slowly and it actually makes it harder for me to follow along. Other than that, great explanation!
You're welcome! I often change the speed when watching various videos. Fortunately, everyone can adjust the speed to a rate that suits them.
I found this super helpful, I'm somewhat new to programming and I had no Idea why self kept cropping up when I was looking at sample code, this is exactly what I was looking for, thank you.
very very nicely explained. Thank you 😊
Great explanation.
Thanks for the video very informative.
at 3:27 what do you mean you overwritten the thunder init method? def __init__():
Great Explanation. Thank you
Wow very insightful, interested to incorporate this thank you!
completely understood thankyou so much
This was SUPER helpful! I've been so confused on this for quite some time now. Thanks for the help!
This was the concise explaination of self, that I needed. Thanks for the good content!
I was so confused about this, but this video cleared it right up for me. Thanks!! I will subscribe and follow.
Thank you so much! It finally makes sense to me!!
I asume its a good and valid explanation and i like that it goes in depth but i find it rather confusing. But im a beginner so maybe thats the problem. Im at least less confused then i was before i guess its just a lot to take in for a non native speaker with all of these new terms and so much information in so little time
The best explananation! It was really helpfull. Thank you so much!
A very nice resource, based on the other comments maybe this is the most helpful for people who are not complete beginners, but like another commenter, I've struggled to understand this from SO and this was super helpful. Thanks for sharing mate!
Great Video Helped alottt Thanks
Somethings I understood others I had issues with. Mind you I am a beginner.
super, díky, dandr init je parádní
Absolutely Straight and neat ! watchful video ! Benefitted! Thanks:)
How to take multiple user input in an oop?
User input would be put in a list.
Specifically, the user 's input would contribute to the polynomial function python code.
Thanks for this. Just wanted a quick iea what the (self) was being passed into class functions and this answered that.
Wow! super concise really!
Thank you. It took me time but i do understand. Thanks again
Great video! Thank you so much! fantastic explanation.
Great and simple explanation. Thanks !!!!
Great explanation Thanks!!!
This was really helpful thank you
Brilliant, I liked your way of teaching "No non-sense" :) Keep it up
Great explanation, I have been looking for a clarification of the self argument, and this video just made it super clear for me, thumbs up!👍
My understanding of the video:
1. Dundee methods are the first ones to be called when a class is instantiated.
2. so __init__ is called which contains initialization steps.
3. Whenever a class object is called, the instance is always passed as the first argument. "self" refers to that instance of the class (object) which is being passed to the method
reason why define "Self" in init method. 4:07.
4. If a class object needs to call a method of the class, it needs to have "self" as the first parameter.
5. Methods of the class can still be accessed even without "self". But not by class objects. But only by the class namespace itself.
eg: a.method() won't work. But class_name.method() will still work
I am new to python, been learning for a few months. I got completely lost watching this.
Thank you for making the video though. I gave a thumbs up. However, as many people mentioned in the comments, consider your audience. If your audience is me.. your explanation is not layman enough. I dont understand self nor init still. If its people that know python, does it provide any value to them? Idk, im not in that camp.
But Thank you! Please Make another one for neebs like me!
Thanks for the feedback, will do!
I think this explained it better:
ruclips.net/video/M1BAlDufqao/видео.html
Been programming in C for 40+ years and like you totally confused. Give this cryptic mess a miss and learn C it'll be far more productive for you and without most of the cryptic mess that python seems to have for a so called modern and beginners language ( Not ).
What Python concept/feature would you like to see covered next (in a similar format)?
Matrix rotation or convertinga. Square matrix to lower triangular matrix like examples expected
This same concept, but drawn and illustrated with sketches in spacial terms.
3:27 What do you mean by "overidden" in this context? do you mean that the __init__ method you used overode the invisible one thats created every time a new class is created? Or that specifying that the emthod prints "Hi" somehow overode something else?
Finally somebody who doesn't task in fast forward mode.
is this a joke?
@@marcomalley2516 talk, not task :)
I meant are you joking about the speed that he talks at... If this isn't fast forward mode then I don't want to hear your version of it 😅
Stupid question: Is „self“ always used when working with classes or are there examples where „self“ is better not be used (and why)?
-> If self has always to be used, then why make it mandatory to declare it?
This was an amazing explanation! Thank you! I am taking Meta's Back End Develop certificate right now and the lesson they had on this(along with a good few other ones) didn't explain the concept very well, so I was a bit confused. But I have a much better understanding now!
I'm taking Meta's back-end dev cert right now as well!
very well explained, thank you so much
Thank you so much for this!!! Your explanations are cristal clear! I hit suscribe button so enthuasistically like never before (an odd number of times)
Thanks I find it very helpful
My pleasure! Do let us know if you have any requests for future videos.
Amazing. You've explained this concept better than anywhere else, and I was having trouble understanding it until this video. Thank you - I'll certainly be sharing your channel.
Really glad you found it useful. Remember to keep the requests coming in. The sky's the limit in terms of what you'll be able to do with Python!
first time watching didnt get anything, we i rewatched it i understood everything . thank you bro , and can you do like 10s breaks between each topic hahahahaha
Really good explanation 👌👌
Are you init to winit?
very good thank you
Explanation was really good and to the point. Appreciate it! Thanks a lot for it
what editor/program are you using?? it looks very nice..
Excellent explanation
I have a question. I want to use 20 element or node labels(numbers) in the python script. I am trying to prepare a code with a loop that code checks these elements or nodes during 10 steps and when each of those nodes or elements temperatures reaches a certain amount for example 500 C, the code saves the stress and strain results related to those elements or nodes. I want to know do can I refer to element and node labels and how can write this kind of code.
Nice and short explanation
I don't think I know enough to understand. Might have to watch this a few times.
Nice video and a great explanation.
Thanks for the kind words, hope you enjoy all the content so far and all the content to come on this new channel!
I have just started learning Python from "Automate the Boring Stuff with Python" and am a beginner and I don't understand this at all. How do I fix this knowledge gap? I don't even know where to start.
it was helpful thank you
Great video. Short and on the point. It would be great if you could speak a bit slower the next time.
Thanks for the clear explanation!
What is the font you use for the terminal?
4:32 just saying that "self (or 'this' in C#) meaning new created instance's (or object) itself" is enough, Thanks.
Was following somewhat okay until the example at the VERY end, where you passed in the instances, then it all clicked, thanks!