mtodd

s/nothing/bash/ ^_^

Tangentially related is the Yale Haskell Group's (well, mostly Paul Hudak's) project Euterpia: http://haskell.cs.yale.edu/euterpea/

You could achieve something like that using https://github.com/defunkt/dotjs

Can't wait to see it!

Lists in general are great for organizing thoughts. Being able to check items off the list helps focus thoughts and offload the overhead of keeping track of progress to something better suited to the task.

If you want to do multiple renames in one commit then the command line is likely the best way.

Pain points rule everything around me.

We design and build with Enterprise in mind. This particular feature has its own Enterprise-specific design considerations and challenges.

The best answer is: when it's ready, but not before.

There is no space allotment for users. Abuse, however, isn't tolerated.

Meme freely!

Apple won't be fixing this. Their approach is to recommend transit apps depending on your location instead.

Collaborating with colleagues is a very social endeavor.

A Rails consultancy (I used to work for) in Atlanta called Highgroove also implements ROWE, going so far as to incorporate it into the way they deliver to the customer. It was a great way to work and operate as a business.

http://highgroove.com/

Like the idea.

I often take a couple of shots of the same thing just to experiment; probably a symptom of growing up shooting digital. I guess you're just banking on randomness preventing dupes from showing too often or manually removing them.

That's not what she said last night.

Sounds like you should be using Chef or Puppet to manage these kinds of dependencies.

I love how easy it is to use conflicting versions of packages. Haven't needed it in practice, yet, but I'm sure it'll only be time.

I do plan to automate looking up the DOM ID. Just wanted to share it early.

Bastard beat me to it!

Friend of mine was graphing out all of the connections (using Graphviz) and found some interesting patterns. Ultimately you can say the same thing for "Science", "Knowledge", and even "Mathematics".

Can't... ;)

I know of at least one change that isn't a new product for consumers but isn't a new change to the store displays either. Nor a giveaway. Might be what this is.

Oh, and thanks again for patching the JSONP middleware.

Thanks for sharing this tricky bit of knowledge, Magnus. Glad you're helping raise awareness on this further :)

Where the hell is the legend?

Quote from the AWS support rep: "I can confirm that ELB has been affected by the EBS issue despite the lack of messaging on the AWS Dashboard".

We have an identical load balancer to one that is causing problems so we're lucky enough to reroute traffic through that one instead to get to the same boxes. (The boxes serve two different APIs through two different DNS CNAMEs so we split the ELBs for future and sanity). In this case, it's helped us out. Alternatively, we would've just routed all traffic to our west coast ELBs.

Why is ELB not mentioned at all on the Service Health Dashboard?

We're experiencing problems with two of our ELBs, one indicating instance health as out of service, reporting "a transient error occurred". Another, new LB (what we hoped would replace the first problematic LB), reports: "instance registration is still in progress".

A support issue with Amazon indicated that it was related to the ongoing issues and to monitor the Service Health Dashboard. But, as I mentioned before, ELB isn't mentioned at all.

[Commented on his blog but not sure if he'll approve, so I'm reposting it here]:

It just seems like you're associating passion with unpleasantness. Does it make you uncomfortable to be around people that enjoy what they are doing passionately?

In my experience, I encounter very little douchebaggery in my community interactions. I don't want to be a dick, but it may have to do with your own view of your work (just a job, as opposed to a passion) that gets you around more douchebags.

There are lots of alphas out there that do condescend and patronize, but that's a characteristic (or character flaw) of that person, and not everyone. It's just far more obvious and annoying when you're not that type of person.

Why don't you find something that you're actually interested in doing for work?

Sorry, didn't see this reply.

We've been using EC2 for a while now, before most of these plugins were available for Heroku. We're extremely comfortable with the platform and our tools for managing it.

We have most of our customer-facing nodes on m1.large instances since we have a lot of caching (mostly loading all of the data in memory) up front and then the rest is CPU bound.

Scaling Heroku is nice since it's just some knobs you turn, but Chef isn't that much more difficult and it's just a different type of knob.

It's interesting to see this line of questioning because the post to me was more about Rubber than about EC2 vs Heroku.

For me, Chef is a no brainer for bootstrapping and managing my instances.

Heroku is also a no brainer, but as rapind pointed, it's for simpler setups or for getting an app up quickly without a lot of ceremony.

We've deployed to Heroku and eventually moved to EC2, but have kept several apps on Heroku.

Moe has some good points about maintaining these instances, keeping things up-to-date, and launching more sophisticated infrastructure beyond your vanilla Rails/MySQL stack apps.

In my experience, Chef is really not that difficult to get setup, especially for the benefits it gives you: idempotent recipes with a great deal of control over the configuration, setup, and control of your infrastructure.

In the blog post, it mentions having to comment out migrations that will fail. That's bad: when bootstrapping machines, a db:schema:load is far more appropriate and less brittle.

Rubber seems like a half-solution for maintaining infrastructure. The blog post mentions that it was picked to prevent having to manually configure boxes, but it sounds like they chose a tool that only half solves their problem and then leaves them to do manual maintenance.

Now, with some experience, I can get a Rails machine booted and running an app in 20 minutes total with Chef. It's really pretty easy, and having tons of resources, lots of recipes, excellent support, and a sane system makes it super flexible.