Why does Java support exception handling?

Here's a nanocast on why we should we use use exceptions to handle error conditions in programs. I hope you enjoy it :-)

This is the first episode in a multi-part series on Exception handling in Java.

-----
COMMENT:
AUTHOR: Azagu
EMAIL:
DATE: 01/23/2007 10:24:36 AM
Hi There,

Greetings and Wish you a Happy New Year. I am following your website for the past couple of months and I liked it very much.

Are you planning to put the mp3 version of this series as well on the website? It will help the users to load it to their mp3 player and listen to them.

You are doing a great job.
-----
COMMENT:
AUTHOR: Parag
DATE: 01/24/2007 03:26:09 PM
Hi Azagu,

Thank you for your kind words and a very happy new year to you too. Most of the mp3's heavily depend on some code or an example also posted as part of the blog post. I am not sure if the mp3 will be very useful independantly. Also, once I make them downloadable, my hosting bandwidth requirements will increase significantly, and I am not sure if my current plan will support that. I am talking to some people about sponsorships. Once that works out, bandwidth will not be an issue, and I can make a lot of material available for download as a podcast.

I have also been thinking about how I can improve the readers experience and help them understand programming best practices in a better way. After some thoughts I feel that these MP3's are a bit limiting because you have to also look at the accompanying code sample.

Very soon I hope to start a series of screencasts, which will show code being written in an IDE along with an audio explanation of the code. I also have plans to record my dojo sessions and upload them as 'Flash' videos.

Thank you for your comments... feedback helps me understand if I am able to help people improve their skills... so keep the feedback coming and also suggest the kind of samples you would like to see on the website in future.

--
Regards
Parag

Comments

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- prismnet.com As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other

Planning a User Guide - Part 3/5 - Co-ordinate the Team

Photo by Helloquence on Unsplash This is the third post in a series of five posts on how to plan a user guide. In the first post , I wrote about how to conduct an audience analysis and the second post discussed how to define the overall scope of the manual. Once the overall scope of the user guide is defined, the next step is to coordinate the team that will work on creating the manual. A typical team will consist of the following roles. Many of these roles will be fulfilled by freelancers since they are one-off or intermittent work engagements. At the end of the article, I have provided a list of websites where you can find good freelancers. Creative Artist You'll need to work with a creative artist to design the cover page and any other images for the user guide. Most small to mid-sized companies don't have a dedicated creative artist on their rolls. But that's not a problem. There are several freelancing websites where you can work with great creative ar

Adaptive Software Solutions

Search This Blog