Skip to main content

Coding dojo - Dictionary

I conducted an Open registration coding dojo in Pune, last Saturday. This was a short four hour dojo.

The topic for the dojo was Dave Thomas' Kata Eight. As always we started with a discussion and design session and started coding. As we worked on the solution, several interesting learning opportunities came up:

  • Designing for readability

  • Using the decorators in Java's IO library

  • Using various collection classes and understanding their performance characteristics

  • Iterating through collections using an Iterator (we will also touch upon the Iterator design pattern)

  • Design tradeoffs to make code faster

  • Various coding conventions

  • Some programming best practices

  • Refactoring support in Eclipse

Many thanks to ITVidya.com for organizing the dojo and to Pune IT Labs for hosting it. 

Participants feedback showed that everyone though coding dojos offer a much better learning mechanism than traditional lectures. Everyone enjoyed the practice oriented approach. Some people found the exercise a bit simple and said they would prefer to deal with more complex topics like "web based development" and "Enterprise Java". Some participants would have prefered a greater time duration.

Thanks to all the participants for your feedback. I will try and incorporate your suggestions in forthcoming dojo sessions. 

Please stay tuned if you would like to participate in the  next open dojo. I will announce it here as soon as soon as the date is finalized.



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


-----
COMMENT:
AUTHOR: Freeman Murray
EMAIL:
URL: http://wheresfreeman.blogspot.com
DATE: 05/15/2007 05:12:55 AM
This is great !! When is the next one ?
-----
COMMENT:
AUTHOR: Parag
DATE: 05/15/2007 06:01:16 AM
Hello Freeman,

Thanks for your comment and interest in the coing dojo. I do plan to have an open registration dojo again, but have not yet been able to set a date.

I will announce it on this website as soon as I am able to schedule it.

--
Regards
Parag

Comments

Popular posts from this blog

My HSQLDB schema inspection story

This is a simple story of my need to inspect the schema of an HSQLDB database for a participar FOREIGN KEY, and the interesting things I had to do to actually inspect it. I am using an HSQLDB 1.8 database in one of my web applications. The application has been developed using the Play framework , which by default uses JPA and Hibernate . A few days back, I wanted to inspect the schema which Hibernate had created for one of my model objects. I started the HSQLDB database on my local machine, and then started the database manager with the following command java -cp ./hsqldb-1.8.0.7.jar org.hsqldb.util.DatabaseManagerSwing When I tried the view the schema of my table, it showed me the columns and column types on that table, but it did not show me columns were FOREIGN KEYs. Image 1: Table schema as shown by HSQLDB's database manager I decided to search on StackOverflow and find out how I could view the full schema of the table in question. I got a few hints, and they all pointed to ...

Commenting your code

Comments are an integral part of any program, even though they do not contribute to the logic. Appropriate comments add to the maintainability of a software. I have heard developers complain about not remembering the logic of some code they wrote a few months back. Can you imagine how difficult it can be to understand programs written by others, when we sometimes find it hard to understand our own code. It is a nightmare to maintain programs that are not appropriately commented. Java classes should contain comments at various levels. There are two types of comments; implementation comments and documentation comments. Implementation comments usually explain design desicisions, or a particularly intricate peice of code. If you find the need to make a lot of implementation comments, then it may signal overly complex code. Documentation comments usually describe the API of a program, they are meant for developers who are going to use your classes. All classes, methods and variables ...

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 ...