Matthew McCullough

Generally so, yes.

I have really enjoyed using and learning Git these past four years. GitHub has made my outbound contributions and request for contributions from others on my OSS and commercial projects significantly smoother than any past solutions.

I understand and respect the "Git is hard" argument from devs coming from a centralized version control system like I did. However, I think many things that are hard are worth it. Only exploration confirms or rejects this. Refactoring a thought from Rich Hickey at Strange Loop, "just because brain surgery is hard doesn't mean everyone should avoid learning it."

I'm doing my part to help others absorb these new ideas. I'm producing and pointing to many free resources to help folks learn Git whenever I can.

Matthew's Git Links
ProGit Free eBook
GitHub's Git Help Pages

In sum, no matter your feeling for Git, please help others have a deeply informed opinion of these new DVCS systems. Even if they don't adopt the tool, they will have a greater knowledge of some unique ways to solve computer science, historical data, and object versioning challenges, perhaps repurposing these tactics for their own programs.

Sadly, this error was made by DZone in the conversion of my source document to their styled PDF. My original document has the correct phase name. I have asked for it to be corrected by DZone as of today. Thank you for the sharp eye for detail.

Sadly, this error was made by DZone in the conversion of my source document to their styled PDF. My original document has the correct phase name. I have asked for it to be corrected by DZone as of today. Thank you for the sharp eye for detail.

Sadly, this error was made by DZone in the conversion of my source document to their styled PDF. My original document has the correct phase name. I have asked for it to be corrected by DZone as of today. Thank you for the sharp eye for detail.

Sadly, this error was made by DZone in the conversion of my source document to their styled PDF. My original document has the correct phase name. I have asked for it to be corrected by DZone as of today. Thank you for the sharp eye for detail.

Sadly, this error was made by DZone in the conversion of my source document to their styled PDF. My original document has the correct phase name. I have asked for it to be corrected by DZone as of today. Thank you for the sharp eye for detail.

Sadly, this error was made by DZone in the conversion of my source document to their styled PDF. My original document has the correct phase name. I have asked for it to be corrected by DZone as of today. Thank you for the sharp eye for detail.

Both DZone and I are complicit in some of these errors that were not caught by our reviewers. We've worked hard to address them and the latest version should clear all of them up.

Both DZone and I are complicit in some of these errors that were not caught by our reviewers. We've worked hard to address them and the latest version should clear all of them up.

Both DZone and I are complicit in some of these errors that were not caught by our reviewers. We've worked hard to address them and the latest version should clear all of them up.

Both DZone and I are complicit in some of these errors that were not caught by our reviewers. We've worked hard to address them and the latest version should clear all of them up.

Both DZone and I are complicit in some of these errors that were not caught by our reviewers. We've worked hard to address them and the latest version should clear all of them up.

Both DZone and I are complicit in some of these errors that were not caught by our reviewers. We've worked hard to address them and the latest version should clear all of them up.

Both DZone and I are complicit in some of these errors that were not caught by our reviewers. We've worked hard to address them and the latest version should clear all of them up.

Both DZone and I are complicit in some of these errors that were not caught by our reviewers. We've worked hard to address them and the latest version should clear all of them up.

It is and has always been entirely free. The only step in the process is getting the download link by email.

The RefCard authors definitely try to put out the best possible card, but the review process could use some help. We have to find our own volunteer reviewers, and you know that can be a real challenge. We have however, addressed the community findings of errata in the card though and republished it. If you find any in the latest version of the card, please point them out. We'll be happy to correct them and give you credit.

Excellent feedback.

java.lang.Thread is only PARTIALLY whitelisted. You can access the static methods on Thread, such as getAllStackTraces(), but cannot call its constructor. We will alter the RefCard to clarify its partial blacklisting. Details are given here: http://stackoverflow.com/questions/1389043/why-is-java-lang-thread-in-the-google-app-engine-whitelist and here http://code.google.com/appengine/docs/java/runtime.html#The_Sandbox

As for java.io.FileWriter, if you go to http://code.google.com/appengine/docs/java/jrewhitelist.html and search the page, you will find that java.io.FileWriter is NOT whitelisted. You might be looking at the whitelisted FilterWriter mistakenly, an entirely different topic. Please verify and confirm. I want to make sure we've addressed your concerns.

Excellent feedback.

java.lang.Thread is only PARTIALLY whitelisted. You can access the static methods on Thread, such as getAllStackTraces(), but cannot call its constructor. We will alter the RefCard to clarify its partial blacklisting. Details are given here: http://stackoverflow.com/questions/1389043/why-is-java-lang-thread-in-the-google-app-engine-whitelist and here http://code.google.com/appengine/docs/java/runtime.html#The_Sandbox

As for java.io.FileWriter, if you go to http://code.google.com/appengine/docs/java/jrewhitelist.html and search the page, you will find that java.io.FileWriter is NOT whitelisted. You might be looking at the whitelisted FilterWriter mistakenly, an entirely different topic. Please verify and confirm. I want to make sure we've addressed your concerns.

Excellent feedback.

java.lang.Thread is only PARTIALLY whitelisted. You can access the static methods on Thread, such as getAllStackTraces(), but cannot call its constructor. We will alter the RefCard to clarify its partial blacklisting. Details are given here: http://stackoverflow.com/questions/1389043/why-is-java-lang-thread-in-the-google-app-engine-whitelist and here http://code.google.com/appengine/docs/java/runtime.html#The_Sandbox

As for java.io.FileWriter, if you go to http://code.google.com/appengine/docs/java/jrewhitelist.html and search the page, you will find that java.io.FileWriter is NOT whitelisted. You might be looking at the whitelisted FilterWriter mistakenly, an entirely different topic. Please verify and confirm. I want to make sure we've addressed your concerns.

Excellent feedback.

java.lang.Thread is only PARTIALLY whitelisted. You can access the static methods on Thread, such as getAllStackTraces(), but cannot call its constructor. We will alter the RefCard to clarify its partial blacklisting. Details are given here: http://stackoverflow.com/questions/1389043/why-is-java-lang-thread-in-the-google-app-engine-whitelist and here http://code.google.com/appengine/docs/java/runtime.html#The_Sandbox

As for java.io.FileWriter, if you go to http://code.google.com/appengine/docs/java/jrewhitelist.html and search the page, you will find that java.io.FileWriter is NOT whitelisted. You might be looking at the whitelisted FilterWriter mistakenly, an entirely different topic. Please verify and confirm. I want to make sure we've addressed your concerns.

Excellent feedback.

java.lang.Thread is only PARTIALLY whitelisted. You can access the static methods on Thread, such as getAllStackTraces(), but cannot call its constructor. We will alter the RefCard to clarify its partial blacklisting. Details are given here: http://stackoverflow.com/questions/1389043/why-is-java-lang-thread-in-the-google-app-engine-whitelist and here http://code.google.com/appengine/docs/java/runtime.html#The_Sandbox

As for java.io.FileWriter, if you go to http://code.google.com/appengine/docs/java/jrewhitelist.html and search the page, you will find that java.io.FileWriter is NOT whitelisted. You might be looking at the whitelisted FilterWriter mistakenly, an entirely different topic. Please verify and confirm. I want to make sure we've addressed your concerns.

Excellent feedback.

java.lang.Thread is only PARTIALLY whitelisted. You can access the static methods on Thread, such as getAllStackTraces(), but cannot call its constructor. We will alter the RefCard to clarify its partial blacklisting. Details are given here: http://stackoverflow.com/questions/1389043/why-is-java-lang-thread-in-the-google-app-engine-whitelist and here http://code.google.com/appengine/docs/java/runtime.html#The_Sandbox

As for java.io.FileWriter, if you go to http://code.google.com/appengine/docs/java/jrewhitelist.html and search the page, you will find that java.io.FileWriter is NOT whitelisted. You might be looking at the whitelisted FilterWriter mistakenly, an entirely different topic. Please verify and confirm. I want to make sure we've addressed your concerns.

I've been amazed by the number of folks using Maven that have this RefCard on their cubicle walls the first time I make it to their company offices. It's fun to see the reach of DZone stretch across the globe.

Speaking of Groovy as a gateway to Gaelyk's awesomeness, there are some cool new solutions that use Gaelyk purely to serve up web service requests/replies. I think you've even touched on some of those facets in your talks/research for iPhone apps... Groovy and GAE FTW.

Speaking of Groovy as a gateway to Gaelyk's awesomeness, there are some cool new solutions that use Gaelyk purely to serve up web service requests/replies. I think you've even touched on some of those facets in your talks/research for iPhone apps... Groovy and GAE FTW.

Speaking of Groovy as a gateway to Gaelyk's awesomeness, there are some cool new solutions that use Gaelyk purely to serve up web service requests/replies. I think you've even touched on some of those facets in your talks/research for iPhone apps... Groovy and GAE FTW.

Speaking of Groovy as a gateway to Gaelyk's awesomeness, there are some cool new solutions that use Gaelyk purely to serve up web service requests/replies. I think you've even touched on some of those facets in your talks/research for iPhone apps... Groovy and GAE FTW.

Ken, thanks for the review and thoughts. It's going to be fun to see the uptake in GAE this week from folks exploring it for the first time based on this refcard. I'm really excited about this platform.

Ken, thanks for the review and thoughts. It's going to be fun to see the uptake in GAE this week from folks exploring it for the first time based on this refcard. I'm really excited about this platform.

Ken, thanks for the review and thoughts. It's going to be fun to see the uptake in GAE this week from folks exploring it for the first time based on this refcard. I'm really excited about this platform.

Ken, thanks for the review and thoughts. It's going to be fun to see the uptake in GAE this week from folks exploring it for the first time based on this refcard. I'm really excited about this platform.

There's a soft limit of 10MB for files stored in the Datastore. Folks have creatively worked around it, but you'll have to evaluate if that makes it more fragile for your situation.

There's a soft limit of 10MB for files stored in the Datastore. Folks have creatively worked around it, but you'll have to evaluate if that makes it more fragile for your situation.

There's a soft limit of 10MB for files stored in the Datastore. Folks have creatively worked around it, but you'll have to evaluate if that makes it more fragile for your situation.

I just presented on this to an audience at TheServerSide Java Symposium in Prague and many audience members came up to me and shook my hand about how excited they were about VisualVM and BTrace. I pointed them at the real heroes - Sun developers Jaroslav, Tomas, Petr and others. What an amazing free debugging tool. I couldn't live without it.

I just presented on this to an audience at TheServerSide Java Symposium in Prague and many audience members came up to me and shook my hand about how excited they were about VisualVM and BTrace. I pointed them at the real heroes - Sun developers Jaroslav, Tomas, Petr and others. What an amazing free debugging tool. I couldn't live without it.

Howard! You mentioned m2eclipse! I'm so surprised.

I'm really glad you wrote this article as I'm doing the same decision-dance. I love some things about IntelliJ, but using Eclipse makes my students and pair-team-members so much happier. And though I could gain some individual productivity from IntelliJ, with "Agile", "Pairing", and "Coaching" dominating my life these days, it's more about the benefit to the collective than for myself, and that equals Eclipse.

Looking forward to meeting you in person when we both are presenting in Seattle...

-Matthew McCullough

Signing JARs can be a tricky thing in JNLP, as certain JARs, such as Java Encryption/JCE providers, have to have a certain company (Sun) Certificate Signature to even function. I've been using and working on the Maven Webstart Plugin to make this easier though in our build environment. It really does make it a breeze.