Hey Sam I just discovered your channel a couple days ago and think it’s just fantastic. Really easy to follow, and one can tell you know exactly what you’re talking about. Makes me hate my school just a little less for forcing us cybersecurity majors to learn Java.
that's the first video i saw in your channel and it's really good, just saw 3 others video of yours. The explanations are really easy to understand, keep up the great work :)
You don't have enough likes or views for this video for what you deserve; this solved so many doubts I had... Definitely awesome. You got a new subscriber. Keep it going that way!
No lie this at the moment is way over my head. But I never turn away from a challenge and want to learn to code. Not only for the money but the challenge to learn. Already speak 5 languages fluently so hopefully I should pick it up easier then not
great video man. just one critique. when showing the execution of the code, zoom out so we can see the code and also the execution. helps to better understand what the code is doing. instead you just made camera transition to the run section.
Thank you for this quick and easy explanation about Exception handling. Even if the new cool kid in town is Python, I still love Java. Even if Java is a statically typed language and is very verbose, it forces me to stay disciplined with my coding. Keep up the good work, mate! Cheers~
It's better to write the message in the catch block to System.err, not System.out, so the user can redirect the error stream into a separate log file, or suppress errors altogether (> /dev/null) or suppress everything but the errors.
I'm assuming if the catch blocks tries to terminate the program, the finally block will still run while just leaving code outside the try-catch won't run in that instance.
... this is the chapter in the book that I always used to skip...... oh, someone is talking about me!!! lol I'm currently working on my project using Spring framework and ur channel helps me a lot to go over Java again. thank u and plz keep uploading great content!
Hey Sam! I currently am in the Seattle area and studying CS, I am a rising sophomore in a community college and will have to transfer next year to a 4 year university. I wanted to know what you think of life as a Software Engineer in SF, in the Seatlle area, you get pretty much the same stuff, but you can live in a house for the price of a small studio in SF. I am currently thinking of applying to the UC schools, but I don't know if it's worthwhile. What would you recommend?
Whichever language is relevant to what you are trying to accomplish by learning to program. Java is a good start because it’s very general purpose. But if you want to learn, for example, iOS development, Swift would be more relevant. For web development it would be JavaScript (which is not at all related to Java).
Is try/catch a good/common practice for interviews? I’ve noticed many times if I do a leetcode problem, I go out of bounds but overall I am “almost there” for solving the problem. But I feel like try/catch is lazy handling of the logic in an interview setting? Or no? I’ve never interviewed and still have two semesters left in undergrad haha so I dont know. I’m naive
Catching exceptions when using arrays would give the impression to the interviewer that you dont understand the data structure you are using. So dont do it. Its like catching an arithmetic exception for a division by zero instead of validating with an if block.
Hey Sam! My name is Quan and I have a friend who is developing a game in Java. He’s hit a road block and needs a mentor. I’m on the 2D animation side of things so my skill level at coding is ass lol. I was wondering if you have an email so I can connect y’all together & he can ask about these difficult problems he’s having like clearing a level. Hope to hear from you soon!
Yeah not a big fan of Java/JS/Python etc error handling, don't really think it's that much of an improvement over C. Try-catch is very uncomfortable to work with, and you still don't really know the type of exceptions that could happen and you're often not aware that some code could throw an exception, which leads to the issues you mention where some rare exception kills the whole Applikation. You then often try to handle that exception with some global error handling, which is tricky to do right and really not elegant. Very much like Null-Safety Error handling in Java should be handled with the type system. Like Rust does it. With Rust you have a "Result" enum provided by the language. Thanks to the match expression (more powerful and expressive switch case) and some provided helper methods - unwrap(), expect(), unwrap_or(), or_else() - you can still I. E. ignore error handling while prototyping (but you do so explicitly and can find it more easily afterwards) or replace an error value with a default or execute some cleanup on errors. And that Result type is generic and thus has information about the error type that also often helps greatly I. E. when different errors could occur.
I love your videos, but I have to say , there are a lot of mistakes in this video , first the definition of exception is wrong, not only while the progame is running have exception ,in fact this 's called RuntimeException , you can't miss unCheckedException when you write your code , another thing is that we could just have try without catch , they both do not have to exist at the same time.
Exceptions can occur at compile time too, bro. They are called Checked Exceptions. (Ex:- FileNotFoundException) . Nice video overall ❤❤ Just be careful to always proofread the script before the video
Brother if u read this plz reply . I just completed oops and I know arrays and sorting . So now I will practise problems on them and parallely learn data structures .. Is that the right way to learn .. 👀 nice video
you doesnt covered the structure of expections! like why you use sometimes expection e and sometimes a specific arithmetic exception e. I hate the fuckin internet, you find everywhere infos and nowhere everything together in a quick understandable format. everybody just touches topics. fucken bullshit
good tutorial but can you please show us the code while you are showing your face. i mean just put your face at any corners of the screen instead of putting it in the whole screen and not showing the code.
☕Want to master Java? Get my complete Java course: bit.ly/42mQlXE
Simple and easy to understand, love the videos
Thank you!
@@moisesantonio2632 spammers
Hey Sam I just discovered your channel a couple days ago and think it’s just fantastic. Really easy to follow, and one can tell you know exactly what you’re talking about. Makes me hate my school just a little less for forcing us cybersecurity majors to learn Java.
Java for cybersecurity seems a bit strange. Glad you’re enjoying the content though!
First off and foremost... I enjoy your videos. Good way to use your spare time. Microphone and lighting is awesome by the way. Good job
Major thanks for your video. You're one of the few programming instructors who explains it in a way that beginners like me can understand.
Awesome video! I didn't even know the finally keyword until today. Thank you!
Love the way you keep the things simple. Thank you.
you are truly a good teacher
You need to make more videos. You're a gifted teacher.
Hey man Shout out to your videos. They are actually helpful. Also love your setting. Respect.
that's the first video i saw in your channel and it's really good, just saw 3 others video of yours. The explanations are really easy to understand, keep up the great work :)
Great tutorial. I come back to your java content when I am stuck in exercises. thank you.
Effortless delivery, keep on keeping on mehn. You're gifted.
You don't have enough likes or views for this video for what you deserve; this solved so many doubts I had... Definitely awesome. You got a new subscriber. Keep it going that way!
🙌🏼
I wish you were my Java Programming Professor. You explain everything so well. Thank you for sharing your knowledge :)
The tutorial structure is insane!
I love your channel bro!
Exception - An error that occurs in a program during nighttime.
Boy, am I glad you did this. Thanks!
ohhhh! THAT'S what exceptions are- processing errors without halting the flow of the program! Thanks! :D
You explain the topic really well! Thank u!
Thank you so much for making these videos!
No lie this at the moment is way over my head. But I never turn away from a challenge and want to learn to code. Not only for the money but the challenge to learn. Already speak 5 languages fluently so hopefully I should pick it up easier then not
Hello fellow language lover!
my teacher took 2 hours to explain this and still failed. loved your video !!
cant believe an 11 minute video taught me more than a 50 minute class that takes place three days a week did
True
great video man. just one critique. when showing the execution of the code, zoom out so we can see the code and also the execution. helps to better understand what the code is doing. instead you just made camera transition to the run section.
Thank you for this quick and easy explanation about Exception handling. Even if the new cool kid in town is Python, I still love Java. Even if Java is a statically typed language and is very verbose, it forces me to stay disciplined with my coding. Keep up the good work, mate! Cheers~
You never mentioned the hierarchy of exceptions :(
this man is saving lives in college 🤝
Awesome video! Easy to understand. Love from Indonesia. ❤️❤️❤️
Very lucid explanation
Ash: Gotta catch them all
I didn't know Oscar Isaac was a part time Java teacher! and a very good one! Great video: simple, organized, direct, and clear. Suscribed!
thank you, know i can create my demo in Exception
Very easy to follow. Thank you! 🥰
Awesome video.! So helpful
It's better to write the message in the catch block to System.err, not System.out, so the user can redirect the error stream into a separate log file, or suppress errors altogether (> /dev/null) or suppress everything but the errors.
Most useful and interesting as always.💗
Can you tell us all the shortcuts that you use during the video?
I love your video's please do a complete JAVA for absolute beginners !
What's the difference between using finally and just leaving something outside of the try-catch blocks?
I'm assuming if the catch blocks tries to terminate the program, the finally block will still run while just leaving code outside the try-catch won't run in that instance.
Hey, thanks for this video. Super helpful!
... this is the chapter in the book that I always used to skip...... oh, someone is talking about me!!! lol I'm currently working on my project using Spring framework and ur channel helps me a lot to go over Java again. thank u and plz keep uploading great content!
Thank you, very helpful !
You rock.....Amazing
Thank you Sam
Nice smooth video
Pls make one on abstraction.
I think it's already there bro like I think oops video probably
Great vid!
Minor comment: 01:40 - not entirely correct. Catch requires Try, however Try requires either Catch OR Finally.
simple and clarity is very important and then super and thread life cycle video i want may be sent it
thank you !
very cool explanation :)
Hello Sam, You mentioned at 1.41 seconds in the video that we can't have a catch without a try and visa-versa, I can have try {
after finally block is executed does it run remaining lines of codes after finally block?
Why is it that after the return; the code still goes to the finally section of the code?
Hey Sam! I currently am in the Seattle area and studying CS, I am a rising sophomore in a community college and will have to transfer next year to a 4 year university. I wanted to know what you think of life as a Software Engineer in SF, in the Seatlle area, you get pretty much the same stuff, but you can live in a house for the price of a small studio in SF. I am currently thinking of applying to the UC schools, but I don't know if it's worthwhile. What would you recommend?
Hey Sam which platform are u coding Java on? I use Eclipse and I absolutely hate it
IntelliJ
nice and simple
beautiful
Is studying flutter worth it?Do reply
That was good 👍
If you’re beginner which language do I need to learn?
Whichever language is relevant to what you are trying to accomplish by learning to program. Java is a good start because it’s very general purpose. But if you want to learn, for example, iOS development, Swift would be more relevant. For web development it would be JavaScript (which is not at all related to Java).
but you didn't explain why it does not return it was not clear at all please consider clarifying the last statement
Is try/catch a good/common practice for interviews? I’ve noticed many times if I do a leetcode problem, I go out of bounds but overall I am “almost there” for solving the problem. But I feel like try/catch is lazy handling of the logic in an interview setting? Or no? I’ve never interviewed and still have two semesters left in undergrad haha so I dont know. I’m naive
I’ve never used try/catch in a DS&A interview.
Catching exceptions when using arrays would give the impression to the interviewer that you dont understand the data structure you are using.
So dont do it.
Its like catching an arithmetic exception for a division by zero instead of validating with an if block.
anyone else studying for amazon technical academy? funny hes wearing the shirt
Good job! very obvious
Solid
Hey Sam!
My name is Quan and I have a friend who is developing a game in Java. He’s hit a road block and needs a mentor. I’m on the 2D animation side of things so my skill level at coding is ass lol. I was wondering if you have an email so I can connect y’all together & he can ask about these difficult problems he’s having like clearing a level. Hope to hear from you soon!
thanx
Yeah not a big fan of Java/JS/Python etc error handling, don't really think it's that much of an improvement over C.
Try-catch is very uncomfortable to work with, and you still don't really know the type of exceptions that could happen and you're often not aware that some code could throw an exception, which leads to the issues you mention where some rare exception kills the whole Applikation. You then often try to handle that exception with some global error handling, which is tricky to do right and really not elegant.
Very much like Null-Safety Error handling in Java should be handled with the type system. Like Rust does it.
With Rust you have a "Result" enum provided by the language. Thanks to the match expression (more powerful and expressive switch case) and some provided helper methods - unwrap(), expect(), unwrap_or(), or_else() - you can still I. E. ignore error handling while prototyping (but you do so explicitly and can find it more easily afterwards) or replace an error value with a default or execute some cleanup on errors. And that Result type is generic and thus has information about the error type that also often helps greatly I. E. when different errors could occur.
I hope you can vietsub in Vietnamese in the next videos
nice
I love your videos, but I have to say , there are a lot of mistakes in this video , first the definition of exception is wrong, not only while the progame is running have exception ,in fact this 's called RuntimeException , you can't miss unCheckedException when you write your code , another thing is that we could just have try without catch , they both do not have to exist at the same time.
Exceptions can occur at compile time too, bro. They are called Checked Exceptions. (Ex:- FileNotFoundException) . Nice video overall ❤❤ Just be careful to always proofread the script before the video
Brother if u read this plz reply .
I just completed oops and I know arrays and sorting .
So now I will practise problems on them and parallely learn data structures ..
Is that the right way to learn ..
👀 nice video
Yes. Eventually you’ll want to learn linked lists, binary search trees, and hash maps.
@@KeepOnCoding ah ok brother.
Ty so much for the reply ☺️♥️
you doesnt covered the structure of expections! like why you use sometimes expection e and sometimes a specific arithmetic exception e. I hate the fuckin internet, you find everywhere infos and nowhere everything together in a quick understandable format. everybody just touches topics. fucken bullshit
good tutorial but can you please show us the code while you are showing your face. i mean just put your face at any corners of the screen instead of putting it in the whole screen and not showing the code.
wait so you dont just put everything in try-catch with an empty catch block?
Its called bad code
Bro go on teaching something new in java.