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 :)
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.
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!
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~
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?
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.
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
... 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!
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.
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.
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).
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.
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
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
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.
