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

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