Usually twice a year for about a week each — once in the US, and once in Europe.

I work remotely full-time as a Product Designer for Elastic. Of our ~1100 employees, it seems that 90% of us are remote, which is pretty amazing. Moving to full-time remote work was a bit of an adjustment for me, but I think my team handles it well. Since we're all over the world, we mostly communicate over Slack and Zoom, and we record and make notes of every meeting and conversation for people who can't be present. Also, we're hiring.

I thought the detail on their pricing slider was pretty fun: https://getballpark.com/pricing

Full disclosure: I work at Swiftype, the company that powers DN's search.

I am certainly biased, but I'd like to think that the quality of the search experience on DN has little to do with the underlying technology and a lot to do with the implementation. I think some relatively simple changes would make a huge difference:

• Adding some basic facets, like badges and date range so that users can narrow their searches quickly.
• Consider tuning the relevance algorithm to weight Stories over Comments and Users, or possibly filtering to Stories by default.
• Consider sorting Stories by overall comment activity or other popularity metrics, like clicks.
• Adding more metadata to the results themselves, like the user who posted, the number of comments, and an excerpt if available.

If anyone from DN reads this, I'd be happy to help if you've got any questions.

I really wish you'd stick to Twitter for all your trolling bullshit.

This is really nice. Great job, guys!

We've recently started using Inky.rb to build emails at Swiftype. It's a truly great, painless experience. The thought of going back to the days of infinite nested tables makes me queasy.

Golden.

"Born again product designer" you say? #blessed

+1