[tweetmeme source=”snarayan” only_single=false]
Some time back, I had finished up one of my pet projects and was looking for something new to work on.
It’s amazing to see the number of choices one has right now in terms of choosing a software project to work on. I primarily develop web applications and like to focus on Rich Internet applications. So was looking around for things in that section. Thought of checking out with people to what they tend to choose..
Wow. I mean, look at the list. and its not all.. we’re just getting started.
Each one of them have their own pros and cons, and choosing among them is really interesting and difficult too.. I started to compare some of these to decide where to start. After few weeks, I was still at the same point and had not been able to make any decision. I always felt like missing something.
Then I realized that I was doing it all wrong.
Nowadays, there are so many things that one can’t keep on top of all thats happening. So I started thinking about how I should approach this thing. Sometime later, in one of the podcasts from Joel and Jeff (from Stackoverflow), I listened to an interesting conversation about choosing what to work on, and I totally agreed and understood the concept behind it.
Technology is a means to get something done. If you’ve found what to work on, as in a domain (or) a problem to solve, it’s fine with what technology you’ve chosen.
One needs to find something worth doing, a problem worth solving and then choose the technology that should back that up. Thats the trick.
Frankly, if you’re doing something really good, it doesn’t matter even if its in php.. nothing against php folks.. :)
Ok, fantastic. So then I started looking for a good problem to solve. Found couple of interesting ones. Started working on them.
The technology chosen is grails, was a good fit for our kind of team and nature of the project. Well.. lets see how it goes.