About me: Nice to meet you! My name is Cristian. Let me tell you why I think I’d be a great addition to your team. I have over 15 years of experience with Ruby. The highlight of my career is probably the decade I have spent at Zendesk, where I am one of the technical leaders of Support, their flagship product, as a Group Tech Lead and Senior Staff Software Engineer. My main focus is scaling the ticketing system and making sure it can handle massive workloads efficiently. That experience turned me into a bit of a Rails performance nerd—so much so that I wrote a book about it, Rails Scales!, published by Pragmatic Bookshelf (https://pragprog.com/titles/cprpo/rails-scales/). I’ve also had the chance to share my insights at conferences like RailsConf, EuRuKo, and RubyKaigi. You can check my talks in my profile in RubyVideo (https://www.rubyevents.org/speakers/cristian-planas).
About me: Nice to meet you! My name is Cristian. Let me tell you why I think I’d be a great addition to your team. I have over 15 years of experience with Ruby. The highlight of my career is probably the decade I have spent at Zendesk, where I am one of the technical leaders of Support, their flagship product, as a Group Tech Lead and Senior Staff Software Engineer. My main focus is scaling the ticketing system and making sure it can handle massive workloads efficiently. That experience turned me into a bit of a Rails performance nerd—so much so that I wrote a book about it, Rails Scales!, published by Pragmatic Bookshelf (https://pragprog.com/titles/cprpo/rails-scales/). I’ve also had the chance to share my insights at conferences like RailsConf, EuRuKo, and RubyKaigi. You can check my talks in my profile in RubyVideo (https://www.rubyevents.org/speakers/cristian-planas).
> I’ve noticed lots of rails developers optimize so heavily for making things DRY, they make the most hard to debug monstrosities full of meta programming all so they could write a thing one one line of code instead of 3.
I think that was definitely the case some years ago, but the Ruby community has matured since then. Meta programming is a bit looked down upon, these days.
Oh yeah totally. Our linter definitely discourages it.
I still see a false equivalency in the ruby community that verbosity == complexity, that tends to make super complex abstractions and DSLs in order to make the consumption less verbose, that then say “see how simple this is to use”
Because rails does such a good job in their DSL, I think I understand why that tendency exists. But rails under the hood is quite complex, and most DSLs are no where near as well thought out.
Maybe I have Stockholm syndrome, because I hated ruby coming from a nearly all c style language background at first, but I honestly think it is pretty cool now. I think a lot of issues come from people wanting to do things in ruby like they would in C# or Java.
Your experience is very different from mine. I rarely interviewed white candidates, but they were still more common than Hispanic and Black ones. The majority of the candidates were Asian.
I don't think that most of proponents of DEI share my opinion, but for me, the endgame of DEI (and antiracism in general) is the destruction of race as a social concept. IMO, race is basically a casta system, particularly given how it operates in America.
Don't get me wrong, I do believe in genetics. I do believe that certain groups of people form genetic clusters. Nevertheless, I don't think that "race" the genetic cluster and "race" the social concept are that much intertwined. Of the 4 major racial groups in America, there are two that very obviously don't cluster (Asians and Hispanics): this somehow is ignored by both pro and anti DEI sides.
In a world in which DEI efforts are successful, the current races would just become non-sensical, in the same way in which considering Irish and Italians non-white has become non-sensical today.
Author of the presentation here. While you are right that sharding is an incredible tool that makes our lives much easier, not everything in our system is/can be sharded.
Also, we do handle more than a billion requests/day, that was just for giving the title a nice ring.
Author of the talk here. Thank you, you made my day by sharing my presentation. :)
One thing I would like to add after reading some of the comments here. The "1 billion requests/day" is actually an understatement so the title has a nicer ring. Last time I checked we were around 2B -and that's according the most conservative approximation-. Those are requests that hit the application, excluding the CDN caching layer.
For Zendesk, what are the business consequences of using a monolith? Is this a mono- or multi-repos? Are tests simpler? Does the system require lots of special-purpose tooling?
Willing to relocate: no. More than happy to make periodic visits to any office, though.
Technologies: Ruby, Rails, Javascript
Résumé/CV: https://drive.google.com/file/d/16LgKHqECH5NDHnN_QCQtk-cXsEv...
Email: me[at]cristianplanas[dot]com
About me: Nice to meet you! My name is Cristian. Let me tell you why I think I’d be a great addition to your team. I have over 15 years of experience with Ruby. The highlight of my career is probably the decade I have spent at Zendesk, where I am one of the technical leaders of Support, their flagship product, as a Group Tech Lead and Senior Staff Software Engineer. My main focus is scaling the ticketing system and making sure it can handle massive workloads efficiently. That experience turned me into a bit of a Rails performance nerd—so much so that I wrote a book about it, Rails Scales!, published by Pragmatic Bookshelf (https://pragprog.com/titles/cprpo/rails-scales/). I’ve also had the chance to share my insights at conferences like RailsConf, EuRuKo, and RubyKaigi. You can check my talks in my profile in RubyVideo (https://www.rubyevents.org/speakers/cristian-planas).