Skip to main content

Live Web Based Training

A couple of days back, we conducted a training session for a client over the Internet using collaboration tools like Vyew, and Skype. An account of the details is posted on Webcast Academy's website (where I am an intern in the class of 1.2).

Below is a summary of the discussion, posted as a podcast.














[Time: 3 mins 15 secs]






What are your views on online training? Feel free to write to me if you would like to try something similar for your organization.



Notes: This text was originally posted on my earlier blog at http://www.adaptivelearningonline.net
Here are the comments from the original post

-----
COMMENT:
AUTHOR: Ranjan
EMAIL:
URL: https://ranjanjha@blogspot.com
DATE: 10/03/2006 12:02:34 PM
Hi Sir

I totally agree with you on this,Infact Sun's philosophy while marketting(I hope I am using the right word) java was " Write once, run anywhere"... obviously Sun was promoting a feature over here.
Infact Software portablility has more todo with Microsoft Vs Others fight and Java was one of the first programming language which gave portability a serious thought and provided APIs where software programmer has to bother less about it at the same time.

Here is one of the articles on java portability:
http://www.javaworld.com/javaworld/jw-05-1997/jw-05-portability.html

Regards
Ranjan

COMMENT:
AUTHOR: Parag
DATE: 10/03/2006 02:22:46 PM
Hello Ranjan,

That's a nice link. A must read for someone who wishes to understand what the team at Sun had in mind when they designed the Java language.

Comments

Popular posts from this blog

Fuctional Programming Principles in Scala - Getting Started

Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path

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