Problem

You need to differentiate between build numbers. For example, you’ve just redeployed your application and need to ensure that the new version is what you are viewing. Or, you need to keep track of how many times you build. There could be many reasons why you want to know the build number that you are on. I use it for reporting bugs against specific builds.

Solution

maven-buildnumber-plugin. This Maven2 plugin will generate a unique build number each time your build your project. You can even configure which maven phase triggers the increment of the number. This plugin can also fetch data from SVN to ensure that a team of developers all get unique build numbers.

As a bonus, it generates a buildNumber.properties file so that you can read in this build number from anywhere in your project. Here is how I use the plugin.

First, update your pom.xml. You need to setup the build trigger.

<build>
  <plugins>
    <plugin>
      <groupId>org.codehaus.mojo</groupId>
      <artifactId>buildnumber-maven-plugin</artifactId>
      <version>1.0-beta-3</version>
      <executions>
        <execution>
          <phase>validate</phase>
          <goals>
            <goal>create</goal>
          </goals>
        </execution>
      </executions>
      <configuration>
        <doCheck>true</doCheck>
        <doUpdate>false</doUpdate>
        <format>${version}.{0,number}</format>
        <items>
          <item>buildNumber0</item>
        </items>
      </configuration>
    </plugin>
  </plugins>
</build>

Now, you’ll need the build number and append it to your artifact’s final name. Add this to your pom.xml

<build>
  <finalName>
    ${project.artifactId}-${project.version}.{buildNumber}
  </finalName>
</build>

Now you’re package goal will output a file named

projectname-1.0.1.war

This is a great start and now you can differentiate each and every build. However, I need to take this a step further.

I need to see the version on my application’s index page. To do this, I use an ant filter to write the version and timestamp to a version.html file, and then copy it to my project’ web app directory. Add this to your pom.xm.

<build>
  <plugins>
    <plugin>
      <artifactId>maven-antrun-plugin</artifactId>
      <executions>
        <execution>
          <phase>compile</phase>
          <configuration>
            <tasks>
              <!-- versioning -->
              <echo message="[build version]"/>
              <delete file="target/projectname/version.html"/>
              <tstamp>
                <format property="rightNow" pattern="d MMM yyyy" locale="en"/>
              </tstamp>
              <copy todir="target/projectname">
                <fileset dir="src/main/webapp">
                  <include name="version.html"/>
                </fileset>
                <filterset>
                  <filter token="VERSION" value="${buildNumber}"/>
                  <filter token="BUILTON" value="${rightNow}"/>
                </filterset>
              </copy>
              <echo message=" version is ${buildNumber}"/>
            </tasks>
          </configuration>
          <goals>
            <goal>run</goal>
          </goals>
        </execution>
      </executions>
    </plugin>
  </plugins>
</build>

Version.html is simple.

<p class="version">Version: @VERSION@</p>
<p class="built">Built on: @BUILTON@</p>

Finally, in my index page…

<jsp:include page="/version.html"/>

Almost everything you want to know about this plugin can be found on the plugin’s site: http://mojo.codehaus.org/buildnumber-maven-plugin/

Alternatives

As an alternative to writing and importing version.html, you can read buildNumber.properties in an MVC controller and put the version in your page model. This is what I for my login pages. I use a java class to read the build number, format it, and cache it. I start the first build number at 00100, then format that to 0.1.0. So the next build is 00101 which gets displayed as 0.1.1.

Update:Tips

Here is a usage tip. You can move the create goal into a build profile so that the build number only increments in specific situations. I use a profile for my Continuous Integration builds so that our version increments only when Hudson builds our apps. This also makes it possible to synchronize our Hudson build numbers to our module versions.

Feedback

What do you use to track build numbers? How do your format it?

Related Posts

• New and Unknown Java Libraries
• PropertyPlaceholderConfigurer with Default Values

Summary
This is a high level summary of the basic .Net API’s for interacting with a database. This includes a short description of each and how they relate to each other. As a developer with mainly a Java and PHP background I was unclear about how ADO.Net related to OleDb and I had no idea what was meant by the term “.Net Data Provider”. I created this because the msdn documentation is HEAVILY focused on ADO.Net and does not give a clear picture of how the many namespaces, interfaces, and classes interact. Please add comments to correct or enlighten. Note at this time the relation of .Net Providers to Nhiberante, LINQ to SQL, and Entity Framework is not covered in this post.

.Net Data Provider

• http://msdn.microsoft.com/en-us/library/a6cd7c08(v=VS.71).aspx
• A .NET Framework data provider is used for connecting to a database, executing commands, and retrieving results. Those results are either processed directly, or placed in an ADO.NET DataSet.
  What that actually means is that a .Net Data Provider implements the interfaces defined in the System.Data namespace.
• A .Net Data Provider is similar to a JDBC driver in Java
• http://en.wikipedia.org/wiki/Java_Database_Connectivity

System.Data

• http://msdn.microsoft.com/en-us/library/system.data.aspx
• This page contains text that makes you believe that ADO.Net is the CORE part of .Net data access, however the reality is that ADO.Net is the highest level of data access and is built upon the .Net Data Providers that implement the interfaces in the System.Data.
• In my opinion it almost seems like microsoft is trying to hide how database connections work, so that users are trapped using controls provided by visual studio.
• This namesapce contains the Interfaces that need to be defined by ALL .Net Data Providers
• Core Interfaces
  • IDbConnection
  • IDbCommand
  • IDataAdapter
  • IDataReader

Four examples of System.Data Implementations

• The below namespaces include classes that implement the core “.Net Data Provider” interfaces defined in System.Data

ADO.Net

• http://msdn.microsoft.com/en-us/library/27y4ybxw(v=VS.71).aspx
• ADO.Net is a database query and manipulation API built on top of the basic .Net Data Provider classes. ADO.Net focuses on disconnected, multi-tier database interaction. In my opinion the core ADO.Net classes should be in a separate namespace like System.Data.ADO just for the sake of clarity.
• Core Classes
  • DataSet
  • DataTable
  • DataColumn
  • DataRelation

Related Posts

• PHP Framework Comparison
• Read HTML with Java – Then 7 Fun Things to do to It
• List of Version Control Web Sites

The early bird registration is about to end for the Strange Loop 2010 conference. This is the second year of the conference. The first year was awesome, hopefully they can only make it better.

Go to the site to see the speaker list, because it’s too long to list here.

http://strangeloop2010.com/speakers?

Early bird registration for Strange Loop is open until 8/6/10. Don’t miss out – sign up now for just $150 through Aug. 6th.
Prices:

• Early bird – $150 (till Aug 6th)
• Regular – $190 (till Oct. 1st)
• Late – $250

Strange Loop 2009 posts

http://blog.codehangover.com/strange-loop-2009-day-1/

http://blog.codehangover.com/strange-loop-2009-day-2/
php

Related Posts

• Strange Loop 2009 – Day 2
• Strange Loop 2009 – Day 1

Book on Amazon

Finally someone has written an in depth beginners book for nhibernate.  Nhibernate 2.0 Beginners Guide written by Aaron Cure is just that and more.  Wow do I sound like a car salesman.  I was a little disappointed when I read Nhibernate In Action last year, because it was more of a reference than a tutorial.  This book is definitely what the title states, which is a beginners guide.  The book contains step by step examples of how to find, setup, and use nhibernate.  I highly recommend this book to anyone wanting to learn nhibernate.  By the way I think all .netters should do just that.

Pros

• love the beginning paragraphs
  • In simple terms, NHibernate does all the database work, and we reap all the benefits! Instead of writing reams of SQL statements or creating stored procedures that “live” in a different place than our code, we can have all of our data access logic contained within our application.
    With a few simple “tricks” that we’ll discuss in Chapter 4, Data Cartography, not only will our queries be effective, but they will also be validated by the compiler. Therefore, if our underlying table structure changes, the compiler will alert us that we need to change our queries!
• starts slow, which is perfect for a “beginners” book.  lots of hand holding and explanations of basics.  this is truly meant for somehow with no experience with ORMs.
• clearly shows you how to use log4net!  great bonus in a nhibernate book.
• briefly mentions all the major players in the nhibernate world, which is great for demonstrating options
  • Examples: fluent nhibernate, nhibernate.burrow, castle, spring ioc, etc.

Cons

• book uses basic aspx pages with custom controls in the examples.  I firmly suggest ASP.Net MVC over webforms.  But it may be too much to learn at one time if you aren’t familiar with either nhib or MVC.  So learn one first and then learn the other.  You won’t regret it.
• most examples are in c# and vb.net.  that’s good or bad depending on your opinion of vb.net.
• No HQL examples.  All query examples use the Criteria class.  This isn’t totally bad especially for beginners, but HQL should have at least been mentioned.

Chapter Notes

• chapter 1
  • clearly denotes which version of nhib the book uses and where to get it
    • Even explains the nhib release verbiage of “generally available”
  • shows basic examples of mapping file and how it relates to POCOs.  Good stuff for a ORM newbie.
• chapter 2
  • good advice for designing your database in logical way that avoids data duplication.
  • clear steps to download and setup a database using sql server express
    • Does mention that nhib works in almost any database, however all the book examples use sql server express
  • nice explanation of how tables relate to your classes
  • great introduction to OTM, MTO, MTM, and OTO relationships
  • good summary of left joins and how joins matter in queries for the different relationship types
• chapter 3
  • starts creating a simple class library application.  clear steps and good examples.
  • even addresses the somewhat hated nullable types and how to handle database columns that need to be mapped to types that can be null.
• chapter 4
  • nice explanation of what mapping means in terms of ORM software and how it functions as the glue that binds your objects to the database.
  • summary and examples of the most common used mapping types
  • gives examples of two mapping styles
    • xml
      • lists the two main complaints which are.. 1) too much xml 2) xml files are not compiled, so you don’t find bugs until run time.
      • provides great tip of adding the hibernate XSD to  your project so that visual studio will provide code completion for you and validate your mapping files.
      • important info about how to make sure the xml mapping files are compiled into your dll
    • fluent nhibernate
      • short example given that shows how using the “side” project http://fluentnhibernate.org/ can work without the xml mapping files.
      • pro is that mappings have to be compiled, so bugs/typos are found earlier
• chapter 5
  • creates console application to test the nhib code
  • shows step by step how to add references to the nhib dlls that you need to download
  • good definition of what a nhib session is and how it relates to an actual database session
• chapter 6
  • why you should and how to use log4net with your nhib project
  • excellent and thorough tutorial for using log4net
• chapter 7
  • nhib config details
  • mentions how easy it is to change databases by simply changing one config line
  • shows how to config nhib in an app.config or web.config
• chapter 8
  • provides example of Singleton DOA pattern
  • shows example of using a structure that holds all the column/property names for a class/entity.  this is done so that the column names in the structure can be used in criteria queries.  all this effort is done to avoid run time exceptions.  seems like a waste of time to me because you if you don’t update your structure every time your db is updated then you will still get runtime errors.
  • query examples using Criteria (at this point all examples have been using Criteria, none in HQL)
• chapter 9
  • in depth examples showing how to create custom controls to display data retrieved using nhibernate
• chapter 10
  • shows how to implement the login controls with nhibernate
• chapter 11
  • covers 11 code generation tools used to limit manual boiler plate coding.  I actually hadn’t heard of many of the ones listed.  Great bonus chapter.
  • nhib-gen, mygeneration, NGen NHibernate Code Generator, and T4 hbm2net seem promising
  • these tools create everything from POCOs to DAOs to services.

Related Posts

• NHibernate in Action – Book Review
• Outliers – A non technical book every freelancer/developer should read
• Configuring NHibernate in a Multiple Project Layout

There’s an underused feature of Hibernate that I’ve been using recently called “auxiliary database objects“. With these guys, you can finally let Hibernate manage all of your schema creation and deletion. No more using Hibernate to generate mapped tables and then coming behind with another tool to finish the job.

A good example of where this is useful is in the fairly common case of using Quartz for scheduling with a JDBC job store. Quartz provides a SQL script for generating its tables. Before auxiliary database objects, the most common way to get the Quartz tables into the database was to include a separate *.sql file in your build and run it using Ant’s sql task or some other SQL executor. Setting it up this way means there are two steps to either creating or dropping your schema: the Hibernate schema export and the Ant task. That ties this mechanism specifically to your build, eliminating a very useful feature of Hibernate.

With auxiliary database objects, you can include the Quartz create and drop scripts directly in your Hibernate mappings and have Hibernate run those scripts along with its normal schema export. Then there’s only one step to creating and dropping your schema, and more importantly, Hibernate is completely in control of the schema. This gives you the immense benefit of being able to set the SessionFactory’s “hbm2ddl.auto” property to “create” and run an in-memory database–like the awesome H2 database–for development and unit testing, and the schema will be generated for you on startup. This is what you lose if you have scripts outside of Hibernate.

Auxiliary database objects have actually been around for a few years, but it only made it into a general availability release a year and a half ago with version 3.2.6.GA. Below are a couple of simple examples on how to use them.

Besides Quartz tables, I’ve used auxiliary database objects to make a fake “dual” table. It’s common to use the “select * from dual” query on Oracle databases as a validation query for your connection pool. When you run a different database for development, like H2 or MySQL, you’ll have to manually add a dual table so that your validation queries won’t fail. Here are the two ways that you can do that using Hibernate’s auxiliary database objects:

First, you can embed the SQL directly in the mapping file:

<hibernate-mapping>
    <database-object>
        <create>
            create table dual (x int);
        </create>
        <drop>
            drop table dual;
        </drop>
        <dialect-scope name="org.hibernate.dialect..." />
    </database-object>
</hibernate-mapping>

Note that you can have zero to many of the dialect-scope elements, indicating what database platforms this database object applies to. Listing zero dialects means apply to all databases.

The second way to do it is to implement the AuxiliaryDatabaseObject interface. To make it simple, use the AbstractAuxiliaryDatabaseObject subclass:

public class SampleObject extends AbstractAuxiliaryDatabaseObject {
    public String sqlCreateString(...) {
        return "create table dual (x int)";
    }

    public String sqlDropString(...) {
        return "drop table dual";
    }
}

Then you have to specify your class in your mapping file, like so:

<database-object>
    <definition class="rds.hibernate.AuxDBObjectTest" />
    <dialect-scope name="org.hibernate.dialect..." />
</database-object>

The examples should be pretty self explanatory. Create statements are run after Hibernate’s own generated create statements, and drop statements are run after Hibernate’s generated drop statements. I’ll make one additional recommendation: while it’s technically possible to put multiple SQL statements separated by semicolons in a single create or drop block, it’s best to only put one. There are two reasons for this. First, multiple statements in a single block won’t work with Oracle, so if any of your target environments are Oracle, that’s right out. The second reason is that Hibernate runs each create and/or drop using one JDBC Statement, so if you pack 100 create statements into one create block, and one of them fails, then none of the other 99 will take affect, either. If, on the other hand, you use one statement per block, you guarantee that all statements will run, and only the ones that fail will not take effect.

That’s all! It’s very handy to have all your extra SQL managed by Hibernate. All you have to do is point Hibernate at a database, tell it to create your schema, and all your tables, views, stored procedures, etc. will appear.

Related Posts

• PHP Framework Comparison
• Read HTML with Java – Then 7 Fun Things to do to It
• List of Version Control Web Sites

I wrote this for consideration for the upcoming 97 Things Every Programmer Should Know book. Alas, I didn’t submit it before the deadline. I’m OK with that that because I had another submission that I think has a good chance to make it in the book.

I particularly like to apply this phrase in every-day software development and could easily apply it to entrepreneurship.

The city of Rome has a history of over two and a half thousand years. The city was the center of the Roman Empire and was the capital of the civilized world. It supported hundreds of thousands of inhabitants only by providing the proper foundation for the city. Its roads.

The roads of the Roman city were essential for the growth of the Empire. These roads were used to move goods and services enabling its citizens to prosper. The Roman armies used these roads to defend the Roman territories and to conquer new lands. The roads provided a network for information to be gathered and disseminated. The Roman roads were critical in for its expansion. Roads were the foundation of this great city.

When you think of Rome, you don’t think about its roads. But what would Rome have been without its roads. How big could it have grown? How could the armies defend the Empire? The Roman roads were required for the city to thrive. The roads are not what made the city great, but were what made the city’s success a possibility.

Every organization has its roads and your organization is no exception. What infrastructure have you put in place to foster the growth of your business and lead to its success? Do you have any infrastructure at all? How far can your organization proceed without this infrastructure?

Perhaps for you this is how you communicate. Not just among your team but with your organization, with your customers, and with your community. It could be how you notify your users of new features, how your users submit bugs, or how your managers communicate deadlines.

Maybe its not communication but your product management. From your code repositories and automated build processes to your deployment and monitoring suites. These might be the factors that contribute to the ultimate success of your organization. Without the proper infrastructure in place the city will fail or cease to grow. Without the roads Rome could not prosper and without a strong foundation your organization will fail or hit a wall.

If your users can not submit bugs they will be forced to use your product day after day with known issues. They will become frustrated and find alternative software. If your organization can not communicate its goals and strategies with you then you can not support your organization and so it will fail.

Find out what it is the supports your organization and fortify it. Be aware of its presence and its importance.

With that said, also consider this: the Roman’s roads played an important part in the Roman military defeat by offering avenues of invasion to the barbarians.

From If You Want to Have Cities You’ve Got to Build Roads

Related Posts

• Outliers – A non technical book every freelancer/developer should read

Book on Amazon

Outliers “The Story of Success” by Malcolm Gladwell is a popular book. I heard about the book in a freelance discussion group at a developer conference. I quickly ordered a used copy from Amazon. It’s popularity became very apparent when multiple people, that saw me reading it in an airport terminal, asked if it was any good because they had heard it was. My answer is yes. The book has been reviewed many times (795 on amazon alone) so to avoid duplicate statements I will give my brief summation along with my comments about how the theories in the book apply to software development. If you have read the book please comment with your thoughts. If not I suggest you do because it’s a quick, thought provoking read.

Summary: The book is NOT a 12 steps to success type book, I really hate those books. Gladwell presents the theory that success is not a trait or a gene that only some people have. Gladwell proposes that there are no simple rags to riches stories where a person builds an empire solely on their own. With scientific studies and research to back up the theories Gladwell explores how opportunities and advantages provide the gateway to success.

• 10,000 hours (very popular topic from the book)
• No one succeeds without many, many hours of preparation. No one.
• Examples from Bill Joy(co founded Sun) to The Beatles are given.
• My thoughts: Turn off the xbox360 and the TV and learn a new language, framework, or pattern. Then repeat.
• Luck
• Some people that prepare will be rewarded with incredibly rare opportunities.
• My favorite example in the book is a list of the richest people ever. A large number were from a 10 year period in the mid 1800’s. That time period gave a few lucky individuals the opportunity to become tycoons because of culminating economic and technical advances.
• My thoughts: So if you are not lucky enough to be learning the types of technical skills that will benefit you, then take it upon yourself to make your own luck and find a position that will.
• IQ is not all you need
• The book covers in depth the story of Chris Langan who has an IQ of 195, but has never attained a college degree or high profile professional career.
• My thoughts: To succeed in software development you need communication skills, imagination, and technical skills(IQ). You need to know how to inform/educate non technical people and how to debate effectively with colleagues.
• It takes a village
• No body makes it alone. We all need support from family, friends, and colleagues.
• Every freelance book or article I read says to have a partner.
• Love what you do
• Great quote from the book: “Hard work is a prison sentence only if it has no meaning”
• My thoughts: You know if you love your job or not. Stop thinking about finding a satisfying job. Update your resume and go find a job you will love. It won’t find you, unless you are one of those really lucky people the book mentions.

Another excellent review of Outliers: http://www.markhneedham.com/blog/2009/01/06/outliers-book-review/

Related Posts

• NHibernate 2 Beginner’s Guide – Book Review
• If You Want to Have Cities You’ve Got to Build Roads
• NHibernate in Action – Book Review

I was looking for a good prototyping tool the other day and I came across ForeUI. This little gem packs quite a punch. Whether you want to create mockups of a desktop application or a web application, ForeUI has everything you need. A six minute demo of the application is available. ForeUI is available for Windows, Mac, Linux, or Solaris.

The canvas where all the work is done is called a plot. Each plot can have 1 or more pages of mockups, similar to Microsoft Excel workbooks. To assist with prototyping of cross-platform applications, the mockups can be drawn in four different modes – Hand Drawing, Wire Frame, Windows XP, and Mac OS X. The canvas width and height can be adjusted and can even be made to look like wrinkled paper for that real hand-drawn prototype look.

Just about anything your imagination can come up with, can be mocked up. The palette comes with over 40 widgets and whatnots that can be used to mockup anything from a simple windows application to a complicated web site. Frequently used mockups such as dialogs and navigation panes can be saved as custom widgets in the palette. Go check out some screenshots and samples of the software in action. Anything placed on the canvas can have an action associated with it. This allows for the creation of an interactive mockup that can be used to simulate what the application will do in a real environment.

Plots can be exported as an image, PDF, or DHTML. A plot can be ran as a slideshow. In slideshow mode, the mockup can be marked up with a red pen. This mode is good for demonstrations and team discussions. Plots can also be run in a simulation mode. In simulation mode, a new window is opened in the default web browser. If any actions were setup for the mockup, such as clicking buttons and activating menus, those things can be interacted with in the browser window.

At $79 for a single user license, ForeUI is a great deal. There are also pricing plans for multiple users. A 7 day trial can be downloaded for evaluation.

Related Posts

• PHP Framework Comparison
• Read HTML with Java – Then 7 Fun Things to do to It
• List of Version Control Web Sites

My notes and thoughts about day two of strange loop 2009.

Also be sure to check out my Day one notes.

jQuery – Matt Taylor

• http://weblog.dangertree.net/
• Showed numerous examples how easy jQuery makes it to select and edit HTML elements. Made me realize I should use jQuery even in small apps.
• Also showed examples of the jQuery AJAX functionality

Mobile Development 101

• http://www.slideshare.net/michael.galpin
• http://fupeg.blogspot.com/
• This session was full which doesn’t surprise me since mobile development is about to get easier thanks to Android.
• Started off going how to develop apps for the iPhone
  • The emulator and development software only run on a Mac
  • Has to be written in Objective C
    • I wanted to throw up when I saw the objective c examples
    • No garbage collection. Memory is limited on phones so this is an important issue.
    • Maybe I’m just to much of a simpleton, but I really don’t ever want to write any objective C
  • MVC framework – cocoa touch
  • No background processing on iphone
• Android
  • Can run any language that is built on the JVM
  • XML format for UI develoment
  • Does not use standard MVC pattern. Uses something called Activities and Intents.
  • There are multiple android emulators
• Mobile dev best practices (not specific to android or iphone)
  • Need lean web services
  • Limit network traffic
  • Limit audio/video/images
• Mobile Web Application
  • Alternative to writing an iPhone/Android app
  • A lot of phones have the same browser now
  • Some mobile browsers leak memory

Entrepreneur Talk – Panel Discussion

• This book was mentioned, Outliers: The Story of Success
• Someone said that you need irrational arrogance to start your own company.
• Another person said that start ups are all offense and no defense. Just keep putting stuff out, early and often
• The idea was presented that everyone has risk even the person working for a company because you can be fired at any time
• The current work culture is sort of like having one client at a time because developers change jobs so often.

Polyglot Grails – Jeff Brown

• http://www.nofluffjuststuff.com/conference/speaker/jeff_brown
• http://javajeff.blogspot.com/
• You can use many languages with Grails. Jeff even gave an example of Grails with a simple language he created
• methodMissing(string name, args) is a very interesting feature of Groovy

Minimalism – Alex Payne

• http://twitter.com/Al3X
• http://al3x.net/books_talks.html
• Interesting talk about little m minimalism and how it be applied to code
• Alex made a few comments about how programming is a young field

List of slides on strangeloop.com
Day two sessions

Related Posts

• Strange Loop 2009 – Day 1
• Strange Loop 2010 – Early Bird Registration

A new developer conference has started in St Louis this year named Strange Loop. Normally I don’t go to developer conferences because they are either in a different country or on the coasts. This one was close by in St Louis, MO. And from the quality of speakers and diverse sessions I predict next years conference will sell out very quickly unless they increase the capacity. Below are my overall topics/themes I took away from the conference and some interesting points from each talk I witnessed along with links to the speaker’s site and slide show if available.


Day two

Strange Loop Thoughts Overall

• open source, open source, open source
• every talk envolved open source. The FUD around open source is finally withering away.
• DRY constant theme
• Mobile development is upon us and will be for maybe ever
• Scala, Clojure, Groovy are HOT languages on the JVM
• Great conference that covered many relevant topics
• All the talks were technical, no boring management oriented sales pitches

Functional Ruby – Dean Wampler

• http://deanwampler.com/
• Link to slide show
• I atteneded this talk because I’m interested in the functional programming line of thought. And I don’t get to see much ruby code.
• Recommends learning a functiona programming language: Scala, Hascal, Cojure
• Multiprocessor systems are making it more important to use threads. Threads and synchronizaton is hard to get right. So functional languages that have immutable objects/values are easier because immutable objects/values don’t require synchronization.
• Try to avoid a bloated domain objects that have numerous properties to fullfill multiple requirements for different use cases. Have smaller objects for seperate uses.

Polyglot Programming – Dean Wampler

• Link to slide show
• polyglot programming: using more than one programming language. Not like using CSS, JS. But like using Groovy and Java or Groovy and Clojure.
• Dean thinks that Scala could become very popular in the future
• Hybrid object and functional language
• Multiple cpus is driving the need for functional languages
• Mentioned the famous quote: “Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”
  – Antoine de Saint-Exuper

Griffon (Swing just got fun again) – James Williams

• http://jameswilliams.be/blog/entry/index
• http://groovy.codehaus.org/Griffon
• Mentioned that the swring application framework is dead
• Griffon is the unofficial grails for the desktop
• It really did looks rails like from the project layout to the build process
• Suggested Groovy In Action for anyone that wanted to earn Groovy

Future of Java – Bob Lee

• http://crazybob.org
• Writes his talks in Java. I’m serious. Here is the SVN repo for his talks
  • http://crazybobs-talks.googlecode.com/svn/trunk/
• Talked about how/why he wanted better resource management in Java.
• Said he searched the JDK and found that 74 out of 110 the JDK has leaks for a certain IO functionality.
• Talked about his work on JSR-330 dependency injection in JDK
  • @Inject annotation
• New quicksort that was developed for Android JVM (Harmony)

Day two


Day One Sessions

Related Posts

• Strange Loop 2009 – Day 2
• Strange Loop 2010 – Early Bird Registration