I’m still alive

Hello everyone,

It’s been almost a month, I haven’t updated my website.  Just 3 weeks left to my final exams for 2 years technical diploma (ANIIT) from NIIT.  And i will have to attend 2 exams ( EJB 3.0, and Software Testing / Quality Assurance ) plus I will have to submit a project before i can attend those exams.  My topic for project is “Image processing”. I’m not really worried about exams and project. Project is almost done. 🙂

My current research topics :

Computational linguistics , and Continuous Speech Recognition Algorithms

Now a days, I’m working with Spain based company named <UNDEFINED> is Official Adobe’s Enterprise Solution Partner. They have a long list of technologies for developing Desktop and Web based RIA’s but they mainly work on : Adobe Flex, Adobe AIR, Adobe Flash With PHP and Java.  Company’s Website

That’s it for now ! Signing off.

Puneet Kalra

October Update

Hey everyone,

First of all, Wishing you a very Happy Diwali. 😀

Just to let you all know that I’m still alive. The first reason that kept me away from updating my blog was Text-to-Speech ( FreeTTS ) and Speech-to-Text ( Sphinx ). I have got really great response from my followers and guests. I have created few sample applications on both of them.

And, the second reason is Exams. The next and the final one for this session is Java Servlet, JSP And Apache Struts on 24th of this month. I’m not really worried about the exam, right now my focus is on SphinxTrain and SphinxDecoder.

That’s it for now, I will be updating again soon.

Finally FreeTTS Worked :)

Hello everyone!

After long long research on Speech Synthesizer and working on projects based on Speech Recognizer.  Finally I made FreeTTS work using Eclipse SDK. I have tested it on Windows XP, Vista and Mac, Working fine on all the Operating systems. I found it little confusing but once you start working on something, Everything starts to solve out one by one.

About FreeTTS :

FreeTTS is a speech synthesis engine written entirely in the Java(tm) programming language. FreeTTS was written by the Sun Microsystems Laboratories Speech Team and is based on CMU’s Flite engine. FreeTTS also includes a partial JSAPI 1.0

Link To FreeTTS Website

Soon, I will be posting a “FreeTTS with Eclipse” tutorial.

So , Stay tuned!


Hello everyone,

Today I’m sharing my experience with you about FreeTTS. After spending many hours working on FreeTTS, I’m still unable to run a simple demo provided by them. Its really horrible that i posted in their forum about error 4 days ago and i haven’t received any reply back till now. I tried to figure it out myself but there’s no such info about it on related sites.

FreeTTS is a speech synthesis engine written entirely in the Java(tm) programming language. FreeTTS was written by the Sun Microsystems Laboratories Speech Team and is based on CMU’s Flite engine. FreeTTS also includes a partial JSAPI 1.0

Link : Project FreeTTS

Still waiting for their reply.

Stay tuned for more updates!

Happy Independence Day

First of all, Wishing you all a very Happy Independence Day!

Finally website is up on this great day. I have moved my website to new hosting provider.

I have some good news for you, I will be updating you guys shortly.

Stay Tuned!


10 Things to go Intermediate Developer

Here are 10 things you need to do to go beginner to intermediate developer.

#1: Learn another language

It doesn’t matter which language you learn, but learning another language will make you a better developer. Even better is to learn one that is significantly different from what you already use on a regular basis. In other words, if you are a C# developer, learning VB.NET or Java will not help you as much as learning Ruby or Groovy.

#2: Learn advanced search techniques and strategies

More and more, being a good developer is not just about your skill, but your skill at finding information. Simply put, modern languages and development frameworks are too large for most people to remember much of them. As a result, your ability to get work done is often dependent upon your ability to perform research. Unfortunately, knowing how to find accurate, high-quality information is more than just heading to TechRepublic for the answer or typing a few words into your search engine of choice.

#3: Help others

Teaching others is invariably one of the best ways to learn anything. It is understandable to think that you don’t have much to offer because you are relatively new to the development field. That’s nonsense. Remember, everything you know you learned from someone or somewhere; so try being the someone that another person learns from. Spend a few minutes a day trying to answer the questions on DaniWeb or another site as best you can. You can also learn a lot by reading other members’ answers.

#4: Be patient and keep practicing

Research shows that it takes “about ten to twenty thousand hours of deliberate practice” to become an “expert.” That’s a lot of time. Furthermore, becoming an expert does not always mean doing the same task for 10 years; it often means doing a wide variety of tasks within a particular domain for 10 years. It will take a lot of time and energy to become an “expert”; working as a developer for a few years is not enough. Want to become a senior developer in your early 30s? Either start your education/training sooner or be willing to do a lot of work, reading, and practicing in your spare time.

#5: Leave your dogmas at the door

Beginner developers probably don’t know enough to state that there is One Best Way of doing something. It’s fine to respect the opinion of a friend or an authority figure, but until you are more experienced, don’t claim their opinions as your own. The simple fact is, Some foolish piece of advice or followed some “expert” who really didn’t know what they were talking about. A great example of this is the abuse of object-oriented architecture. For example, many beginners read some information about OO, and suddenly the class diagrams to their simple applications look like the Eiffel Tower.

#6: Learn a few advanced ideas in-depth

Much of what goes into being an intermediate developer is having a few concepts that you are really good at working with in code. For me, it is multithreading/parallelism, regular expressions. How did this happen? Multithreading and parallel processing came about because I read articles on it, thought it sounded interesting, and figured it out on my own; I keep writing apps that use those techniques. Find something that has you really hooked. It might be image manipulation or maybe database design or whatever.

#7: Learn the basic theories underlying your field

It’s one thing to write “Hello World”, but it’s another to understand how the words appear on the screen. By learning the “groundwork” that supports the work you do, you will become much better at it. Why? Because you will understand why things work the way they do, what might be wrong when things are broken, and so on. You will become better by learning what happens at a lower level than your work.

#8: Look at senior developer’s code

At your job, take a look at the code the senior developers are writing and ask how and why things were done a particular way. If you can, check out open source projects as well. Even if other developers don’t have the best coding habits, you’ll learn a lot about how code is written. Be careful not to pick up bad habits along the way. The idea here isn’t to just blindly imitate what other developers are doing; it’s to get an idea of what works and what makes sense and try to imitate it.

#9: Learn good habits

Nothing marks an inexperienced coder like stupid variable names, poor indentation habits, and other signs of being sloppy. All too often, a developer learned how to program without being taught the less interesting details such as code formatting — and it shows. Even though learning these things will not always make your code better or you a better developer, it will ensure that you are not viewed as an entry-level developer by your peers. Even if someone is a senior developer, when variables are named after their 97 cats or their functions are called “doSomething(),” they look like they do not know what they are doing, and it makes their code harder to maintain in the process.

#10: Have fun

Want to be stuck on the career treadmill? Hate your job. What it takes to move up in this business is not merely dogged determination to bring home an ever growing paycheck but an actual enjoyment of your work. If you do not like your work and you are a junior developer, what makes you think that being an intermediate or senior developer will be any better? Change jobs or change careers. On the other hand, if you love the work you are doing, great! I guarantee that you can become a better developer if you keep at it.