1,406 karma · joined October 3, 2009
I've really liked it for https://blog.statusok.com and https://statusok.com
GitHub webhook deploy flow, one-click SSL, 301 redirects and other rewrite support, CDN seems pretty good.
Also, what's up, homie? Hope you're well.
http://jamesgolick.com/2007/12/1/noisy-backtraces-got-you-do...
DHH later ported the work to Rails:
https://github.com/rails/rails/commit/f42c77f927eb49b00e84d3...
I knew James mostly online and a little in person from various programming conferences. He was smart, funny, and kind. He made a difference. He will be missed.
We're using this code-level approach in basically every one of our Rails apps these days: http://robots.thoughtbot.com/segment-io-and-ruby
Most common integrations: Intercom, Mixpanel, HubSpot, AdWords, Twitter Ads, Google Analytics.
Good interview with Peter (Segment founder) from February this year: http://podcasts.thoughtbot.com/giantrobots/86
https://github.com/thoughtbot/dotfiles sets up a bunch of slick aliases and plugins for Vim and ZSH to make development productive.
We've tried putting style violations in the build and found there are enough edge cases that it isn't exactly the interaction we've wanted. Sometimes, we want the human to say "no, my pair and I broke the guideline on purpose and we're okay with it in this case." We don't want a broken build in those cases.
Totally agree with you about getting feedback earlier than opening a PR, though. Linters integrated into text editors are a great way to go.
https://houndci.com/configuration
> the change is a false positive
I've been using Hound on about a dozen projects the last few months and haven't seen false positives. We built it atop Rubocop, which has been pretty well-vetted.
> Software development has too many unwritten rules and social interactions for a bot
We've limited our guidelines to a subset that should almost always be "no argument, my bad, fixed in [SHA hash]." However, it comments instead of failing the build or mechanically changing the code because that the human should make the final decision about whether to make the change.
Some other good ones:
Everyone's busy so we'll see how much time is needed and able to be spent by the new maintainers but we're happy to have found almost a dozen developers to lead maintenance across the two companies (Crowdtap and Iora Health) and we took the time to express a process and way of doing things to help make the project more efficient:
Prem Sichanugrist was a former apprentice of ours. He's from Thailand and is now a full-time thoughtbot employee.
Please apply if it interests you!
http://robots.thoughtbot.com/post/14216183124/internship-or-...
I'd say Hungry Academy is definitely an apprenticeship.
I heard about Heroku Bartender from http://devopsweekly.com
It pushed me to finally use a Linode slice for which I had a $60 credit from http://appsumo.com and play with Ubuntu, which is outside my typical skill set.
I had fun installing Ruby, git, Postgres, and https://github.com/defunkt/cijoe on that slice. While stuff was installing, I added the favicon to Heroku Bartender.
There's a lot of cool software and tools out there. Open source, DevOps Weekly, etc are awesome for learning and playing.
Startups love Facebook authentication more than users do.