I just spent a good deal of time trying to get the optional FTP task working with the default ant install on OS X 6.4. The most useful information on this topic that I found online was right here: http://mactip.blogspot.com/2009/02/ant-ftp-task-libraries-jakarta-oro.html. If you scroll down to the comments section:
"Whoever built the Ant distro from Apple didn’t have all the optional JAR files to hand, so things like the ssh task wont work even if you add jsch.jar to ~/.ant/lib"
— SteveL (on the Ant dev team)
So that pretty much nailed it. Time to upgrade. For this you’re going to need:
HTML5 Boilerplate has been generating a decent amount of buzz lately. OK, it’s nice. Really, really nice. So nice, in fact, that I abandoned my own project to create a project baseline. Instead I rolled my own custom boilerplate, and there was a lot to customize.
If you aren’t in a position to deploy working code on a regular schedule, then your project can’t really be called “agile.” Getting the team together regularly and taking a test-first approach to development are fantastic practices, and employing them is crucial to a successful agile team. Agile by definition, however, means being able to deploy recent updates to production frequently and regularly.
“Agile” is a bit of a buzzword these days, and one of the chief complaints I hear from developers working towards an agile methodology is the push to be immediately more productive while the infrastructure lags behind. Maybe the development and pre-prod environments are unstable, the process for deploying to production is slow or costly, or there isn’t an accepted standard for driving automated unit and acceptance tests. Whatever it is that’s slowing you down, fix it! The longer it waits, the worse it gets. Here’s my own checklist for deciding whether or not a project is ready to be called “agile.”
On the surface, Jawr is a resource bundling library for Java web-apps with an incredibly confusing name (try saying “Put the Jawr JAR in the lib dir” a few times out loud…). The project website has this to say about it:
But why should I bundle my resources anyway?
A few days ago Hubspot published a simple choropleth map visualization of Twitter usage per capita across the United States. The map assigns a percentage value above or below the national average tweet-rate to each state.
Edward Tufte would be quick to point out that neither the visualization nor its corresponding blog post contain two bits of concrete information: The actual national average tweet-rate, and how it compares to previous years. Without these vital metrics, the conclusion (“…Twitter will be an especially important tool if you are trying to grow your business…”) is a bit suspect, though the $150M (projected) they made in 2010 tells me they’re doing OK.
That minor quibble notwithstanding, the map does call out a few surprising conclusions (Massachusetts is one of the top three? Really?). I’d really love a time-series of these maps over the last four years, just to see how much things have grown and changed.
Speaking of Twitter, it dawned on me today that my own decline in Twitter usage links directly back to the acquisition of my iPad. Lets look at the crucial facts:
* App-switching was non-existent for a good while post-launch.
* The iPad features a terrible, awful, horrible (sorry…) keyboard.
Don’t get me wrong, I’m sure there are thousands of happy iPad tweeters in the world, but I’m not one of them. Sadly though, because the Flipboard app integrates with Twitter I *do* still post retweets and article links pretty regularly. Unwittingly I am a cog in the information proliferation machine.