Wherein we write down some stuff that we know.

Presenting at JA-SIG Summer ‘07

I got word today that one both of my two proposals were accepted. Here are the executive summaries:

Lessons Learned from Rails Development

So you’ve deployed uPortal, CAS, Confluence, and JIRA. You’ve conquered Maven and your entire life is represented in XML configuration files. You’ve got Java application deployment down to a science. Now some guy from Denmark comes along and says you’ve got it all wrong. The nerve!

We treaded lightly into the world of Rails but over the past year we have learned a lot of valuable lessons that can be applied to web development in general.

  • Convention over configuration in the right measure
  • Deployment needs to be easy
  • Deployment needs to integrate with your SCM

Rails has benefitted from a tremendous hype cycle, but a lot of the benefits are real and can translate to other frameworks.

Pragmatic Issue Tracking with JIRA

As technology workers and managers we often have more things to do than we have time, so we are constantly on the lookout for time savers. They say that time is money and we all know that to make money you have to spend money. A similar concept applies to time in that you have to spend time to save time. We’ll look at how JIRA helps you do this, but also focus on how to implement JIRA to make sure it’s a success.

Specific topics will include:

  • Who should get a JIRA project
  • Setting realistic expectations
  • How usage will differ between types of users
  • Using JIRA to Get Things Done

Comments are closed.