I had once done a project in which we loaded lots of XML in prefetch and then did java script to do cool effects like drill downs or search. Why was this exciting?

For multiple reasons:

1. This was done in early 2000.
2. It was amazing concept for web UI application to prefetch the data and in java script use the data to render runtime on browser without refresh.
3. In complex applications like supply chain where multi-tier complex widgets make web ui's refresh very slow, this was very fast. Everyone was excited about the potentials for the product.

The company cashed on the concept and did some amazing demos. It was a huge selling point for the company. But what we failed as developers was to instituionalize the framework and give it back to the community as pattern. Today, if I look at AJAX I find it does similar things but only its not limited to a multi-million dollar company with deep pockets. The technology is available for everyone and anyone to use. This is the power of design patterns.

In those formative years when design patterns was still evolving; I remember having this chat with my boss who was a seasoned teacher. I was asking him what does he think is the use of design pattern apart from being theoretical concept. The answer though vague to me at that point was - "As engineer we start writing programs and solutions as languages. We always think either object oriented or procedural or database. We don't try to abstract the problem fundamentals. Design patterns are the exercise in understanding and refining what we are solving, so that all language practioners can then implement it." E.g. web application data, business logic and view management implementation details are so different for all langauges. In PHP you will probably start with smarty templates, php files and some ini and httpd.confs. In Java you would have XML descriptors and some servlets and JSP jars. The code and the structure everything is different. It seems from bottom up there is no meeting point and these are very diverse implementations. But if you do a top down view, the problem definition is same. Render the data from database in specific view after applying required business logic . The requirement does not change for any language or any implementation. So why is there not a common blueprint for solution. This is where design patterns come in. For this you can use MVC pattern. I am not going into details of MVC pattern here but what essentially it says is that separate your implementation in three components with each individually handling only one specific such as view or control.

Now, when I see AJAX and see how the niche technology that we thought was only specific to our application is commonality to all web apps I understand what is Design Pattern. Every language has implemented AJAX in its own way. It different library, used differently but its same design pattern.

What did I learn?
As a developer I need to see beyond the implementation and learn to abstract the design pattern and give it to community for reuse.

Posted by Shekhar Yadav at 11:13 AM | Permalink | Comments (0)

Every developer goes through the pain of learning different languages so as to increase his expression. Each language has its own differentiation and reason to learn:- perl makes you good at regular expressions and text processing, php teaches you fast web development, C++ makes you learn through object orientation, C is pure old system language etc. Where does JAVA fit in all this? and more importantly why should I learn Java?

I tried to find the answer to this question and this is what I find:

Bad Points

• Java is object oriented. But compared to C++ you will realize that Java is toy-gun by which you don't accidentally blow yourself up but at the same time you can not kill with it


• Java coding style after having used C++ style makes you feel at loss. Simple things like prepend member variables with "m_" are not followed.

Now Good Things

• Java has rich set of libraries ranging from socket, string basic types to more specific ones like Mail apis etc


• Java has rich set of frameworks around it like application servers, messaging server etc


• Java is community effort with formalism to it

Going back to original question why should I learn java, the reasons are:

• It is the only language that is object oriented and has big community following. Like in C++ nobody contributes to community development which maybe because either C++ programs are system programs or there is no corporate backing.


• It is the only language that has rich set of pattern libraries implemented and documented for all use cases ranging from networking, web architecture to content management etc.


• There are most numbers of developers talking in Java which means most problems and solutions are being discussed in Java.

And most importantly like any other culture, you need to Java for the heck of it. So "Do Java TODAY !!"

Posted by Shekhar Yadav at 08:10 AM | Permalink | Comments (0)

On a site like Flukiest the biggest assets are its users and the community that they build. So why am I writing about the technology and what is technology@flukiest?

Well, would it not be wonderful to know how Flukiest is not a fluke but a different and innovative approach to photo and music sharing. When we first heard Duc think aloud about Flukiest (some people did experience it first hand, for the rest of you the proof is in the pudding) the first thing that we wanted him not to do was to create another networking or photo blogging site. The agenda was clear, don't create yet another photo site. Don't have pathetic technlogy that will not survive years to come. If someone starts using Flukiest, he should come back and be fluked forever. His photos, music, community are forever and so is Flukiest.

With this agenda, hard work and continous feedback from users Flukiest has come a long way. This blog will be offering some insight into behind the scenes technology and the future direction of Flukiest.

Welcome !!

Posted by Shekhar Yadav at 08:07 AM | Permalink | Comments (0)