'Tis the season to hack on fun side projects instead of the thing I "should" be doing.
I finally open-sourced the app I've been using to read Hacker News in a feed reader. It makes it really quick and easy for me to stay up on latest tech news.
https://t.co/KhAFfpfsQ7
It's Friday, so we deployed 3 new features. JK, we deployed these days ago behind a feature flag. All we did today was push a couple buttons to flip on Project Overview, Feature Creators & Owners, and Read-only API for everyone.
https://t.co/SfXy4UAmDD
We just released Flipper 1.0! But this release is more than just a version number. Introducing free plans, sponsorships, and a new teammate.
https://t.co/WHFBSzWdZI
According to rubygems, I have released 67 different gems. Those gems have been downloaded an astounding (to me) 624 million times.
But I've never released a 1.0. Until today! ๐๐ฅณ๐
Head over to https://t.co/2MwC46bz6k for the rest of the story (new teammate, sponsorships, generous free tier, etc.). Feels big!
If you use flipper or anything I've made in the past 20 years, I'd really appreciate you sharing this!
Feature flags are amazing. I've said it before. I'll say it again (on repeat). They give you control so you can increase confidence and reduce accidents.
One way is by using objects other than "users" for flipping features. Flipper actors can be anything, even jobs!
We recently migrated to https://t.co/OhPDfCbtYy (and Rails ActiveJob) from delayed job with the snippet in the screenshot of this tweet and few Flipper.enable calls.
Zero outages and sweat.
Full story here: https://t.co/vwKlmDEpuP
Have a crazier flipper actor story? I'd love to hear it.
How we helped a customer migrate their Rails application
to a new ActiveJob backend -one job at a time-without
user-visible interruptions.
https://t.co/UzsfHElzpj
Anyone out there with mad thread skills would be welcome to rip apart the background thread polling @bkeepers and I wrote a few weeks ago.
https://t.co/PPratP0Mj8
It's been working fine locally and in production, but I love learning so don't hold back.
@will_j I was on the team that shipped the first version of GitHub Actions, and this was the primary use case we used in all our examples. Ironically, I have yet to see anyone (myself included) using this workflow. Iโd like to, but Heroku has just been too easyโฆuntil last week.
Today was a big deal for us.
We officially welcomed @bkeepers as an owner. This is his beautiful face after signing the paperwork.
He's already been working on things like automatic setup, docs and feature flag organization.
Pumped about the year ahead!