mcos

The biggest problem with the spaces vs tabs debate is that editor presentation is still tightly coupled to file persistence. Imagine an abstraction layer created so that developers might choose to see what they wished, yet have files saved in a standard format it might negate some of the issues people have.

This is great. I wonder if there's a way to package it up for an e-reader, or as a PDF?

This is a great move. Unfortunately it's still in Microsoft Word format and there's no license associated with it. Would love to see this somewhere like GitHub, where it could be forked and changed by others.

I'd like to give this a go, but I don't have a twitter account. How do you see this working for those developers without a social media presence?

Techcrunched: http://techcrunch.com/2013/04/01/steam-gauge-gauges-the-size...

You could read all the responses into a Queue-type structure and then populate the database in the background.

.

Unfortunately, if you're using an Intel-based Mac, the Mac versions of applications are limited to Power-PC machines.

Thanks, I've already tried that. My main issue is EBS performance when writing the dump file to disk. The backups themselves don't impact on database performace much, but writing up to 20 Gigs of a dump file to an EBS disk on a nightly basis is extremely slow. Maybe this Data Pipeline service will help bypass that.

Just this week I was looking for a better solution that would back up my RDS database to S3. I'm currently using mysqldump, but the RDS instance size has grown extremely large and so, it has become unwieldly. Hopefully this will help with that.

If you've seen the movie, I'd highly recommend "Moneyball" the book too. It goes into a lot of great detail that the movie doesn't deal with.

A large version is available here: http://xkcd.com/1127/large/

No, just straight up EC2 and RDS. It seems not all the RDS instances are affected, but it's just frustrating that they all haven't failed over.

"11:03 AM PDT We are currently experiencing connectivity issues and degraded performance for a small number of RDS DB Instances in a single Availability Zone in the US-EAST-1 Region."

Given that my sites are deployed using Multi-AZ RDS instances and yet they're still down, this takes the cake a little.

"It's built with simplicity and power in mind -- The simplicity for a non-technical user to be given the reigns to deploy from a master branch to a "staging" server… or to a production server after any tests have passed."

I'm sure there's good reasoning behind wanting to give a non-technical user the rights to deploy code to servers, but I'm afraid I can't seem to conceive of them right now. Can you elaborate why you would want someone without the requisite technical skills deploying code?

They are hiring! http://www.jobscore.com/jobs/twilio/list