Pinned
I have changed my last name to Alayce. If you’re curious about the story I wrote about it on my blog eileencodes.com/posts/where-id…
eileencodes
2,953 posts
eileencodes
@eileencodes
OSS: @Rails, Ruby, and Rubygems Core Teams | Work: Engineer @PlanetScale | Prev: Shopify, GitHub, 37signals
Joined October 2011
- I have some exciting news! This week I was promoted to Principal Engineer @github. I'm really proud of the work I've done here since joining in 2017, and excited for that work to grow from here.
- As of Tuesday @github is running Ruby 2.7 in production. 🎉 It took 30+ gem upgrades, 15+ gem patches, and fixing 11k+ warnings. The upgrade shaved an impressive 20 seconds off production boot time! I'll be writing a post about our experience soon.
- So a big thing happened yesterday. @github is now running 100% on Rails 4.2 in production!!!!!!!!!!!! #railsupgrade #github
- Replying to @sgrif @rubemazenha and @nateberkopecI will not be quitting Rails. The community is too important to me.
- I'm honored and excited to be the newest member of the Ruby core committers. I love having the opportunity to make Rails and Ruby better for y'all. ❤️Congrats to @eileencodes on becoming a Ruby committer! You deserve it!! bugs.ruby-lang.org/issues/20728#c…
- I rebase with master so I can hide how good I am at engineering...
- Today was my 4 year @github-aversary! Looking forward to more work on making Rails and Ruby even better!Excited for my first day @github! I'm joining the Platform Systems team as a Senior Systems Engineer #githubber #newjob
- #Protip: Get through a git bisect and realize you labeled a bad ref good or a good ref bad? Run `git bisect log`, save the output to a file, change the part of the log that's wrong and run `git bisect replay`. Now you don't need to start your bisect over.
- I'm super proud of the work we've done on Rails 6, and especially happy with the multi-db work I did. But some days all I get are bug reports and help requests on this feature and it's really exhausting. #opensource
