Eclipse Forum India - Day 3 ...

Todays tidbits:

• Neal Ford's "10 ways to improve code" was good. One of this bullet items: Use IntelliJ. The money you invest in it will be compensated by the 4 days of developers paid time to configure Eclipse. 4 days to configure Eclipse? I'd create a small & fully functional plugin in that time
• Vishal Puri's session on Spring 2.0 was nice. If he had added few slides on AOP, it would have been better for the audience
• In the non-techie topic "You can't buy an open source community", Neelan Choksi said, if some projects weren't open source, it might not have been this successful. In the examples he mentioned Eclipse. I don't think so. I think there are two reasons that mainly pushed its wide spread adaptation are:

1. PDE bundled with the default download. Any Eclipse user (at least a Java Developer) who wants to try out plugin, don't have to download anything.
2. Usability of PDE. Anyone can create a Hello World plugin and run it in less than 5 mins. That gives a good start.

• I visited Parasoft's booth for more details about SOATest. I happened to see a demo of JTest as well. Its a nice Eclipse plugin that helps in testing Java code. One of the main features they emphasized was the ability to automatically create the test code based on the program's logic. The tool browsed thru the code of a method for the if/while/for constructs and generates different test cases for the different values. So you write the code, generate the test case on the logic and verify your code whether it works? I don't understand! What do they call this? Test Last Development?
• Impiger has an online contest. Try it out here.