https://meta.discourse.org/t/running-sidekiq-more-efficiently-and-reliably/15001
Not sure what all is going on here
but the discource guys have tuned their sidekiq setup
http://david.heinemeierhansson.com/2014/tdd-is-dead-long-live-testing.html
DHH says testing is dead. some choice quotes
Test-first units leads to an overly complex web of intermediary objects and indirection in order to avoid doing anything that's "slow". Like hitting the database. Or file IO. Or going through the browser to test the whole system. It's given birth to some truly horrendous monstrosities of architecture. A dense jungle of service objects, command patterns, and worse.
Rails can help with this transition. Today we do nothing to encourage full system tests. There's no default answer in the stack. That's a mistake we're going to fix. But you don't have to wait until that's happening. Give Capybara a spin today, and you'll have a good idea of where we're heading tomorrow.
I guess we can look forward to more Omakase :-)
His point i think is that, for webapps - UI are the specs
and UI spec (via capybara) is the right tool
and unit-testing in the classical sense is wasteful
http://codeofrob.com/entries/you-have-ruined-javascript.html
A rant againt frameworks in general and Angular in particular
https://github.com/trotzig/diffux
a gem to diff images
Looks like C++ has changed quite a lot (atleast since the last time I touched it). Many interesting changes have been made in C++14. Check out this video and see what's up with C++14.