Dev-Day at Tikal - Second Round

Hi All,

After listening to all comments for the previous Dev-Day post, we've decided today on the tech meeting on the following points:

  1. The format for the dev-day will be 1 hour session followed by “hands-on”.
  2. We will use several technologies which integrates with JVM, but not necessary pure Java language only.
  3. The work will be with pairs sitting on one laptop – We think that heterogeneous pairs would be great (i.e. one “server” developer and one “client” developer).
  4. We will concentrate on technologies, rather on business. So we will reuse and enrich the same application on our meeting.
  5. All team will develop the same application above, and the chosen application will be used for Tikal-Fuse (repository of sample applications). We make use of this repository on our kick-off projects as well as training sessions.
  6. All artifacts will be saved on source control repository.
  7. The chosen application is a very simple CRUD application for managing sample applications. An example of such a application can be seen on sample application at ExtJS sample site.
  8. The first dev-day will concentrate on building the application with technologies Spring/Hibernate on the server and Flex on the client. We can use several binding options, but in my opinion it would be great to use Spring-BlazeDS
  9. We will use Maven2 as our build mechanism. IDE is free to choose.
  10. We'll expect start our first dev-day on September.

 

Any more improvements suggestions/ recommendations are more than welcome...

Thank you

Comments

Anyone who wants a head start on maven2 can find a nice tutorial here:

http://sujitpal.blogspot.com/2006/07/maven2-step-by-step.html

hi,

though late in coming...

let's try to make the application interesting enough for it to have added value and encourage participation, not just technological showcase...
for example, we could develop app that will run embedded inside the community site, and that will do (voting) polls about next forum meeting topics.

or something more generic; a flex/ajax/wsdl-launched twitter client that talks with twitter server via web calls, that can be used for chats as well, with search capabilities. anyway, I think we need a neat cookie for an app. hello worlds won't cut it

Guys,
Aside of Maven - please specify any preconditions to the first session. What participant must know or install before the session ?

I will state my view on this again. I strongly think we should concentrate on core Java and important building blocks rather then newly emerging technologies.

Of course we do not wish to be left behind, however the benefits of having a strong Java foundation (generics, collections, threads, OO class design) far exceeds those of acquiring a new technology.

why don't you want to use new technologies? As much as important, writing collection code, threads, etc., will have a very low appeal factor and in my view will likely to attract much fewer people than up-to-date technologies, including the ones posted by Yanai

Besides, one of the designated targets is to help building Tikal's technologies code sample repository.

what about execution environment? how about GAE? there's a great series of articles posted recently on IBM:
http://www.ibm.com/developerworks/java/library/j-gaej1/
http://www.ibm.com/developerworks/java/library/j-gaej2/index.html