pedrobelo

lol.

I'm not sure where to begin, but yes - it does take a special kind of idiot to believe that appointed judges can launch a coup to protect the elected president.

and why on earth is this on Hacker News? I guess even Jovem Pan is beginning to realize this whole movement is a clown show.

I wrote about a few of the different formats before: http://pedro.by4am.com/past/2014/5/23/get_more_out_of_your_s...

And been working on a tool to merge the schema with actual code for Sinatra apps: https://github.com/pedro/sinatra-schema

Not advertising that a queue (or any database for what matters) is shared between apps!

When using a non database-based queue you'll have to find another mechanism to make sure your operation is still atomic.

In other words you can end up in a situation where a record is inserted but the job to work on it is not enqueued, or worse - that an insert fails but the job to work on it is enqueued.

Point 2 is still necessary despite idempotency imo: lets say some value is updated to "a" and then to "b", enqueuing two jobs. If the request to update "b" runs before "a" then your receiver will end up with the wrong value. Same if the initial request to update "a" fails.

Kind of a long shot, but their "forgot password" flow allows for username enumeration attacks:

https://www.dropbox.com/forgot

For sure.

Most of the time migrations are developed in a feature branch, so the owner is responsible for splitting his branch into two or three before sending pull requests (as many as required to address issues with hot compatibility).

This means that we have two or more merges (and deploys) from master, each requiring a full run of the test suite.