Interestings

Don't hardcode placehold/cat/charliesheen services into your code

Just your annual reminder that these services go down and will timeout your tests. Just download the kitten and serve it yourself, ya dummy.

Postgres sorting is not consistent when using offset and limit

It seems that postgres will sort consistently within a "page" of results. So the results on page 2 will always be the same.

But if there are duplicate values in your sort column and those duplicates cross a page boundary, it is entirely possible that one of those items will show up both pages.

So best to throw a secondary sort column in there if not sorting by a unique column.

Interestings

Checkman + Tracker

You can now monitor Tracker projects in Checkman.

Update to the latest master, install the Pivotal Tracker gem and checkout the readme.

https://github.com/cppforlife/checkman/blob/master/README.md#included-check-scripts

Interestings

Google's favicon service

A reliable way to get cached favicons (e.g. https://plus.google.com/_/favicon?domain=pivotallabs.com )

Helps

Making snapshots fail on AWS

We're trying to help our PM accept a story that requires a snapshot of a persistent disk to fail on AWS. Does anyone know a good way to make this happen or fake making this happen?

Events

Monday: Muse user group

This Tuesday is our second muse monthly user group at adobe sf.

Free: get badge: http://www.mugsf.com/

Blog:
http://mugsf.tumblr.com/

Helps

Capybara "within" blocks and CSS pseudoselectors

We're running into an issue where :nth-child doesn't work with capybara CSS marchers. Oddly, the Xpath equivalents work just fine.

Halp?

Events

05/20: Agile Experience Meetup: Designer / Developer pair-cooking show

Robbie will be speaking and live-coding!

When teams integrate Agile and UX practices, the borders between designing and making become increasingly blurry, with siloed work replaced by cross-disciplinary collaboration. For our next Meetup, we'll combine a live pairing session with two talks on collaborating across roles and disciplines. How is pairing better than traditional collaboration? What are some pitfalls to be mindful of? Is it the right choice for your team? After their talks, we'll open up the floor for a panel-style Q&A.

RSVP at http://www.meetup.com/Agile-Experience-Design/events/116322382/

Interestings

Negate a scope with ActiveRecord

Say you want to negate a scope.

scope :active, -> { where(active: true) }

You start by creating another scope:

scope :inactive, -> { where(active: false) }

Then the underlying column name changes, and you're forced to go back to two different scopes to update it. Ugh.

Wait!

You could have negated the first scope in the second scope!

scope :negate, ->(scope) { where(scope.where_values.reduce(:and).not) }

Now, use it:

scope :inactive, -> { negate(active) }

Boom.

Interestings

FireSASS in Chrome (source maps)

If you're using SASS and ever wanted to see the original line numbers in your SASS files for debugging purposes, you've probably used FireSASS. Unfortunately, FireSASS is not available in Chrome.

However, you don't need FireSASS in Chrome, as SASS Source Maps totally work.

The following blog post will show you how to enable it.

http://fonicmonkey.net/2013/03/25/native-sass-scss-source-map-support-in-chrome-and-rails/

Events

05/20: Agile Experience Meetup: Designer / Developer pair-cooking show

Robbie will be speaking and live-coding!

When teams integrate Agile and UX practices, the borders between designing and making become increasingly blurry, with siloed work replaced by cross-disciplinary collaboration. For our next Meetup, we'll combine a live pairing session with two talks on collaborating across roles and disciplines. How is pairing better than traditional collaboration? What are some pitfalls to be mindful of? Is it the right choice for your team? After their talks, we'll open up the floor for a panel-style Q&A.

RSVP at http://www.meetup.com/Agile-Experience-Design/events/116322382/

Interestings

Remote code execution vulnerability in nginx

A remote code execution vulnerability was discovered in nginx 1.3.9 & 1.4.0. It has been fixed in 1.4.1 and 1.5.0. Update to these versions if you're running nginx.

http://nginx.org/en/security_advisories.html