That reason isn't a technical one. As an administrator of your small company you have to hire people that are good enough and keep them happy.
All small companies have this problem. Programmers don't want to work for small wages, feel unappreciated, work on uninteresting problems forever, or be second-class citizens. Those that do and are half-decent, would rather prefer the job security of a big company.
Another reason would be the stress of any small business to be profitable. Not only that, but you've started the business partly to get rich.
If what he's saying is true, and AOL can't interfere with their writing, and it's in the contract, and he also earn a handsome sum of money, then I can see why they agreed.
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.
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.
You're right about the technical. As for what he's offloading I guess that's running TC as a business. Ad sales, budgets and so forth.
On a side note it's very strain to me to run something so intertwined with the valley from... Seattle.
Does the editor and founder of Mashable maintain the server and fixes software issues?
I hope not!
But it should also be a payday for him, a more reliable one at that.
The technical reason seems like a very bogus reason. Its true that the TC design could use some help and the general site layout and speed could use some improvement. But any half-decent developer and a designer who is worth his balls could solve this problem. After all they are running on wordpress using PHP. In regards to the speed of the site, its no so much of a technical problem as it is a "widget problem" they have more external JavaScript widgets pulling in than the site itself. The only solution to that problem is a reduce the number of external calls.
The other reason he used was that he is tired. I can understand that, it is very much possible to get tired of something that you have been very involved with for several years, even if the project is the love of your life. It can be both mentally and physically taxing. But he is not going anywhere... he is staying with TC even after the sale. What responsibility is he offloading other than the technical aspect of the site? And it isn't much offloading because its not like he is sitting behind the computer and developing the site, he would be hiring someone to that job.
The only thing that he doesn't mention and doesn't talk about (anyone else in his position would have done the same), is money. It is possible that AOL offered something that was too good _for him_ to refuse or he really needed the money. Everything else he mentioned sounds like a bunch of hogwash to me.