11–20 of 74 posts
(I work at Stripe.) We're also accepting applications for our second Open-Source Retreat: https://stripe.com/blog/open-source-retreat-2016
Nice program! There seems to be a typo relating to start/end dates, though: It says the grant lasts for "three months", but the quoted period is "from January 15th until March 15th, 2016".
Love Conway's Game of Life in the background.
Would be interested to hear from the devs about the actual reasons they chose to write unilog ( https://github.com/stripe/unilog ) instead of using multilog (which ships with Daemontools). Agreed that multilog is arcane and weird but what are the actual problems with it that unilog solves?
(I'm an infrastructure engineer at Stripe) This actually took a fair amount of digging! We've been using some version of unilog for over 4 years now (longer than I've been at Stripe), and we'd mostly forgotten why we switched. What follows is more the result of historical exploration and guesswork than authoritative statement of original truth. I'm fairly confident that the impetus for unilog was timestamp prefixes f…
The original headline feature of unilog was that it wouldn't block writes if the disk filled up. multilog does - if it can't write a line to disk, it stops ingesting data off of stdin, which eventually causes the application to hang writing to stdout.
unilog sends you an email and starts dropping log lines, which we decided better matched the tradeoffs we wanted to make - losing logs sucks, but not as much as blocking your application until you figure out how to free up disk.
Kool aid is so good!
Unless you just wanted to throw out the catchy but ultimately insightless line and then walk away while donning sunglasses. Remember, cool guys don't look at explosions.
Some of the projects (e.g., jepsen) are quite impressive. I bet that displays like this one beat any office perk when it comes to hiring.