« Home

Always complex problems have simple solutions......

It was about a month ago I was put in to new mobile project that landed in Cygnus, chennai.We were to develop a web application accessible thro mobile devices.

Well it was my long time dream come true....Mobile devices...J2ME...I was really kind of happy n excited about the project.

Later on we were explained the functionality by our PL we were to develop those applications different kind of Emulators (Emulators are nothing but tools to simulate the particular service providers mobile device) and also a site.

Basically the team consisted of three people excluding my PL, A guy who was 2.5 yrs experienced other girl with 1.5 years experienced and finally the junior most me. We were given 3 weeks time for R&D on Emulators API packages etc.The difficult part of it was that the emulators interface was all in Japanese and even the javadoc was in Japanese :-)) we had to translate each n everything and then go on..Well it was like I was in a maze.

We managed some how to learn the First Emulator one of the Service providers. Well it was an easy task coz the documentation of that particular emulator was in English...

The next week also was lil not tat tough..We managed to study about the second emulator also...Well I was happy that I found and taught other two in my team how to build and run a project in the emulator using the ant builds :-).I was also satisfied that I was able to explore most of the unknown parts of this emulator.

We had the next week ahead, we were to study about the third one, As usual our system admin helped me install the tool kit. I was happy that I was able to start the tool kit without any errors and exceptions.Well, this emulator was little different from the other two we had two kind of tools inside it. One was to build the codes and other to run the code in the simulated environment.

It took us almost one day to bring up the Build tool, We were not even aware that there was a build tool..Later some one accidentally we invoked a .jar file (A collection of class files similar to .exe file),usssh! it opened up the builder tool like Aladdin's magic lamp.


Next came the difficult part, we were not able to build a single template java file..Not even the example codes which the emulator has in its installation itself, I managed to find out that the JDK's and J2ME's paths was all hard coded in the build tools JAR files, I found out an interface to change the hard coded values and changed it, but still it gave me build time errors, Like the builder was not able to identify even the basic java packages and the methods in side them which were already included in the class path. I was looking about clearing these errors for about a day.

Finally I planned to extract the jar file of the build tool, change the class file through a decompiler and repack it in the jar. So I started my work the next day I unpacked the jar I some how managed to find out the class file in which the environment variables were hard coded and I changed it compiled it, Repackaged the jar file. I thought I did something the best.

With my own pride I started the build tool, loaded the java files and started the build...to my surprise same errors again, I was scratching my head. Wondering how come things can't turn up even after doing such a thing...


I was trying to do all things to solve the issue for about two days, Finally I had no other go other than to go and ask my PL for help coz all the three of us were facing the problem.

The next day morning I went to and told the issue, He asked wat are the solutions I tried I told him all that I did, He was chuckling and said "I think u are doing too much of R&D, basically there must b some simple way to this”, I laughed in myself and thought after even changing the class files it didn’t work, How come there can be a simple way???

After half an hour he called me to help him installation of the tool kit in which I had the problem, I was proud that I installed it for him, I also taught him how to build and run, He created a new project copied the sample code in it and build it...Hurray to my happiness even he got the same errors..

He thought for two mins, Googled to find out about the errors, Google didn’t help much.

Later he unzipped the entire JAR file in J2sdk, jre and found out in which package the method comes and added in the class path. I was wondering, I was very sure it wont work..Finally he was ready for the next build...I was in my own world thinking about class files, jar files etc...

He clicked on the "build" button...

It took about 80 seconds finally we saw the words "Build Successful...."

I was in full surprise...raising my eyebrows...He chuckled at me and said the magic words of advice..."Just try to understand one thing, Even in life and in software field, Most of the complex problems have simple solutions" saying this he chuckled at me.

I gave him a blank smile and returned to my room. I was wondering whether it was his experience or his way of problem solving, I consoled my self saying that it would have been coz of his experience...But wat he said was the truth...Often there would be simpler solutions for complex problems...

The thing we get excited too much about the problem which makes us think too much, if for a second or a two we remain calm n focused sure we would be able to find the solution, if not the solution at least the path that leads to the solution...

very true...
but one problem maashe, we wont think simple once the problem is complex.

Post a Comment