Debugging has always been a draw back for me because I never had a good teacher or resource like this. Thanks!

I like how you explain everything slowly and going into every detail. Most of the KZfaq bloggers shoot the words like they had to pay KZfaq for every second of their videos.

Thanks for the lesson Tim , I learnt more about debugging than I did in college , continue the great work.

This was actually a lot of fun; it's like a puzzle. You should make a "Debugging of the week" series. Love your content!

Thank you. You are very underrated KZfaqr Sir. Once people come to know about your channel, you are going to become too famous, which shall happen very soon :) :)

4:23 - test the application for bugs and 5 steps to take when dealing with them 11:01 - "boolean" bug (dealing with user input) 15:43 - "do-while loop" bugs 21:53 - "for loop" bugs 26:32 - debugging the "for loop" 30:02 - "global variable" bugs 43:14 - "class instantiation" bugs 52:35 - testing edge cases and finding more bugs 56:25 - dealing with user input 1:13:15 - "if statement" bug. Flawed calculations. 1:18:27 - video summary and a piece of advice

Tim, Thanks for your help. According to me, you are the best teacher on C# and Programming.

Thats a great video on debugging! I appreciate how patiently you explain every step along the way! Really helpful.

You're the best at C# tutorials I've seen so far.

This was a well put together, clearly communicated video. Thank you, Tim!

D on't panic. R ead that error message. I dentify the purpose of the code that broke. F igure out what breaks that code. T ry a new solution. I love how you said to enjoy debugging. I get really frustrated and self-critical when I have issues, but like you said it's part of programming. And programming is awesome.

Simply amazing. Really appreciate the work you put forward, especially the edge cases... and different scenarios.

Might be mentioned but im at work atm. _____THIS is so important._____ It's basically more then half of your work sometimes and always the solution to "Don't know why, but it works", not writing millions of lines of new code. The senior developers at work always starts with breaking points and start searching the call stack and not looking at the code at first. Just a tip for someone who just started out as a junior developer or are in school. Great video as always Tim! Cheers!

Excellent video Tim, even though I'm experienced in this area, I still watched it all. You never know what you tips & tricks you might pick up from others, no matter how experience you are. Couple of my tips - Don't use "double" when you want values for things like currency or hours worked - use "decimal". Decimal is more precise, double is better for fractions. I cringed when I saw you put a double in here :) Breakpoints - Not really covered here, but use it's features (condition breaking, label name). Labels on break points is great, when you have a large application, and currently debugging several issues over a few days. When you look in the breakpoint window (under the debug menu) you can see which breakpoints are for which bugs your trying to fix. e.g. We use "JIRA" A bug system, and I tend to label my breakpoints using the ID number from the jira. I can then quickly disable the ones I'm currently not debugging as debugging sessions can run into multiple days. Comments - Personally I don't like "comments" in code, the code should be clear and variables well named "t", "w", "ttl" - What do these mean? Name them properly - the compiler doesn't care if it's 20 characters long. Pointless comments. I see the below type of comments so many times... // Refresh the form. myFormName.Refresh(); The code tells the developer what it's doing, the comment is pointless and makes the code look messy. However you use use the XML comments - the ones with 3 slashes and comment your classes & methods etc.! Again great video for the new developers!

Brilliant and very realistic lesson! Funny but sad thing is that I had a situation in my life when company paid me less because of the mistake in their software. They did not wanted to fix it and so they just didn’t paid me part of my money. I’ve had to argue with them and only after long and nasty conversations they agree to pay me my money.

Hi Corey. Thank you for the video. Despite all things I learned here, definitely, the last part (piece of advice) was that you rock on!

People always say Mondays are the worse, I look forward because I know Tim will be dropping knowledge. I try to approach debugging by thinking like the user as I write, i.e let me put a letter in number box, this help me track the potential spots to check, appreciate the insight you provide on a weekly basis, looking for to another awful Monday next week 👊

you are like one of the most underrated guys on youtube and that bothering me

thanks a lot for putting alot of effort making this video. really love this.

The reason so many applications look like a mess out in the real world is because your boss wants it RIGHT NOW!!!! You don't have time to do it the right way. Too many software companies are lead by non-programmers that have NO IDEA what object orientation is OR EVEN CARE. You don't have time to write logging classes or create Exception classes that make the program easier to debug later.

Thanks Tim. I will definitely follow strategies you have outlined.

Kudos to the condition using TryParse. Learn’t something new. As always, great tutorial Corey. Keep it coming.

a lot to learn in this video thanks, i think u will do a do while loop in the next video for the first section, and some improvment could be to prevent the user from entering a negative number and not above 100 hour maybe and put the user in loop until he answer clear answer, also for yes or no we can force him to enter yes or no and put him in loop if he answer yeah or naaa until he give clear answer yes or no. and maybe if first question making sure he enter acme or abc if something else we also put him in loop. never trust the user :)

Every programmer needs to watch this video. If they did, the world would be a better place.

man, i really love you thanks a lot

Great session Tim!! Very insightful

Hey Tim, I love your videos. Although as a beginner I feel like they're very difficult. I have a inquery, Would you wanna briefly cover how to communicate through different forms? Example: how to edit a variables value through another form. Thank you so much. And keep doing your thing!

Good example but in real world you have to fight with complex stored Procedure models with complex database. To learn basic debug good video. Thanks for sharing

nice one Tim! ->nuggets in every video

14:43 , if u take true, it will not allow you to enter what what you did.

Nice advice. Thanks!

Could you please do a video on Func and Action in c#???? I love your videos and i think youll be able to thoroughly describe its functions in real world.

Great video! I've learned this the hard way..I'm still fighting the D from DRIFT. This could be referenced in schools

3:41 15 mins to fix it. With explaining every thing step by step, it took one and a half hours. So this raises a some of questions. Was that a reasonable statement? What if one can't do it in 15 mins? How does one knows if he's ready (good enough) to even attempt to get his 1st c# job? How efficient you have to be? How to test your self? Maybe you could expand on issues like these in your dev question series? I know you have a video about "how to get a c# job", but I feel that it's more for people that already has some kind of job experience in the first place. What do you do when you are self taught, have no official education in this field, and have 0 job experience as a programmer (not counting ones own test apps)? :)

Your video fixed bugs in mind :)

Hi Tim! Thank you for the great videos! I tried for the mailing list; gets to 50% and stops. Anyway, good job and thanks again!

Tim, how will you advise new junior developers to read and understand bunch of codes that was written over years. I find myself in such situation ??

Thank you very much.

YOU DESERVE MORE VIEWS !!!!!!!

very good sir

If this is a legacy piece of code would it not be appropriate to keep it so that users putting true will enter something else in the datasheet (as well as using yes)? Some users will have gotten used to that as an entry field and whilst this is a relatively simple application and the changes wouldn't make a huuuge difference to the user experience, on something more complex it could be a bigger issue. Very good video though! Learnt a lot from your stuff, just thought if you're representing it as if it's an active piece of code it would perhaps be a good idea to mention restrictions like backwards compatibility you might be placed under :)

hello @ 21:39 for this code string answer = Console.ReadLine(); cont = false; if(answer.ToLower() == "yes") { cont = true; } I did it like this string answer = Console.ReadLine(); while (true) { answer = answer.ToLower(); if ((answer != "yes") && (answer != "no")) { Console.WriteLine("Please enter yes or no"); answer = Console.ReadLine(); } else { break; } } Is my version better because it can handle input other than yes and no? and is it better to place it in a function?

Thank you. Thank you. Any tips on debugging massssive solutions? Having issue debugging css, everything is labeled !important and overrides everywhere? Again, Thank you!

Wonderful!

It's really useful for beginners. I learned a phrase: I worked at acme. :) Thank you!

Hi Tim... I have two questions... 1. Is there any way to obtain the name of the company from the User input and later using it while writing "Simulating Email..."? 2. I'm trying my best but I couldn't figure out why I'm getting an exception if I enter an instance of Acme then ABC and then again Acme. Could you please help me with that?

Hi Tim, I think I'm doing something wrong here, because when I clicked the link from the YT video to get here for the source code download, I got the source code for your previous video on Events. Although the link to the debugging source code is named Events Demo on your blog site... Love to hear from you, Greetings, Peter

Hello! Question for the debugging professionals: What you think about reverse debugging technology? Have you ever tried it? How does it work in practice? I want to buy RevDebug because it looks promising, especially the ability to debug on production. Is that a good choice?

I clicked for most source codes but still not got them. Is there any problem with posting them?

please can you rectify my problem.. I am getting Breakpoint will not currently be hit. No symbols loaded for this document in visual studio.. please suggest me what to do?

Hi Tim, what do you think about ASP.NET SignalR? Could be useful make a video on this topic too?

hi Tim Thanks for all your content. I could not receive the source code from the source code link after registering

Maaannnnn get to the point instead of saying don't panic for 5 min... Anyway thx for the video :/