JavaOne / JIRA Studio

I’m in San Franciso at JavaOne this week, and we announced the JIRA Studio launch this morning. I’m the product manager for Studio, and its pretty awesome after so many months of work to finally make the announcement:

Atlassian today announced the release of JIRA Studio, the all-in-one, on-demand development suite. JIRA Studio is a hosted development environment that solves one of the biggest headaches for developers: the deployment and maintenance of their tools. JIRA Studio includes many of Atlassian’s award-winning products and provides a world-class issue tracker, an enterprise wiki for collaboration, as well as the ability to manage the code repository and manage code reviews.

Not sure what JIRA Studio is? Check out the website, or watch the video:

This year’s Atlassian / JavaOne tshirt is pretty sweet:

Leopard Time Machine in action

I upgraded my MacBook Pro to Leopard a week or so ago, and to be honest except for some UI tweaks and improved search results I hadn’t really noticed much different.

Today’s my last day in the office before leaving to the States, and so of course the backlight on the MBP failed on me. Luckily, we had a loaner that I could borrow for the trip, though I was a bit bummed about not having access to all my apps etc.

As I was copying over some absolutely must-have data from old laptop to new, I noticed that the loaner had a faster processor and twice as much RAM as mine. I asked the sysadmin if I could just trade, and he said sure.

So I embarked on a test of one of Leopard’s shiniest features, Time Machine. As far as backup apps go, it doesn’t seem particularly different than any of the other apps I’ve used, except that it senses external drives and proactively asks you if you’d like to use it as a backup drive, which if you respond to in the affirmative, will automatically run backups periodically in the background. Given that I’ve already lost my home MacMini to two hard drive failures, I set Time Machine up on it immediately after upgrade to Leopard.

So anyway, my goal was to completely transfer the contents of the old MBP to the new one (using an external monitor on the old one so I could see what I was doing). I ran a manual backup from the old one, which took about 3 hours to a SATA drive for about 100gb. I then ran restore from the Leopard installation disk utilities, and it ran for about 2 hours.

Results = completely almost shockingly successful. All applications, preferences, iTunes libraries, etc. were copied seamlessly. My computer booted up and looked exactly like the old one. Quicksilver still knew my shortcuts, FireFox still knew my history, Adobe CS3 ran fine and remembered my recent docs, everything. The iPhone even synced fine. I’m pretty damn impressed.

Heading to California

I’m flying out Thursday to San Francisco for a week (including a quick weekend stop thru Louisiana) - if anybody wants to meet up shoot me an email - mknighten @ gmail.

Art of the skitchslap

Skitch has very quickly become an invaluable tool here at Atlassian, we use it daily to illustrate failures in visual design or really anytime we need a screen capture that others can view. For those not in the know, Skitch is a tool that allows you to quickly take a screenshot of anything, add the insults, arrows, or FAIL(s) which most aptly illustrate your point, and load it to a web url that anybody can access (if you give them the URL).

The developers here have taken Skitch to the next level, with the creation of the Skitchslap:

(v) skitchslap: the act of denigrating something by annotating a screenshot or image of it, using skitch. “Man, my CSS didn’t work in IE7 - got majorly skitchslapped for it”.

For a better understanding of what this means (including examples), you’ll have to read Nick’s hilarious post.

New Blog

For those who haven’t been watching my Twitter updates, my site was hacked last weekend. After a few days of trying everything to get it working, including a failed restore from back-up, I finally gave up and am starting with a fresh new install of Wordpress.

If you’re watching this on RSS, you’ll need to update your feed to the new address. However, since I’m unable to post on the old blog, I have no idea how to notify people of the new url, so hopefully after a few months/years of silence people will wander over to the site and realize its changed.

Since my primary audience is probably my family, whom I know don’t use RSS, I suppose its not a big deal.

The old blog is available here if you’re looking for old posts.

Update: by excellent suggestion I’ve burned my feed (which makes future URL changes moot): http://feeds.feedburner.com/Chatterwocky