Making sure that the 3 guys working together are actually working ltogether is tough. Then you deal with schedules, deployments, personality conflicts, and the whole thing.
Managing things is a profession unto itself. My guess is Arrington doesn't like doing it.
It took me a while to parse this as "Finding ones who'll be available after finishing that one feature you need is harder." :)
No offense but his sounds so incredibly naive it's not even funny.
From the post I take it that is is exactly what Arrington didn't want to do any more. The article you linked to basically says 'to make your idea a success, you treat the programmer in detail, and let him focus solely on the technical aspects of the software.'.
Same is true for other industries btw. I'm living through this in the real estate sector right now and sometimes I want to punch people in the face for not just thinking for one freaking second before blindly doing what some other non-invested person wrote on a spec sheet or plan, but then I remind myself that they're all mercenaries who just do what I (directly or indirectly) tell them, and that I need to be on top of every little detail and double- and triple check everything. That's what driving (not just running) a business is about.
Perhaps what Arrington means is that it's really hard to find programmers willing to work on these two products for the long term. It is a blog and a database, after all, and the nature of the software doesn't make for terribly exciting work.