Jeff Kao

So I played around with that quite a bit.

We actually, it's funny, we migrated when I worked at PagerDuty.

We moved some workloads from JavaScript to actually CoffeeScript.

But I think it's pretty much defunct now.

Nobody really uses it.

So those are probably my main languages, you know, dabbled in Python and some C and C++, but never in like a really full-time sort of manner.

And so these days at Radar, mostly working with TypeScript, some Scala for some Spark pipelines, of course, a lot of Rust.

And yeah, what else?

Maybe some Python as well.

That's the matter in the face.

I think this is sort of like an interesting question because technology comes in cycles, I would say.

And that's definitely something I learned with some of the more senior principal engineers at companies I've worked at before, where really having an understanding and appreciation of things that are old really gives you insight onto what's coming next because technology really is cyclical.

So I think there's a lot to learn and like about Ruby.

And usually, I would say the entry point for most people with Ruby is really Rails.

So it's really that concept of making programming languages work for you, in some sense.

And so what does that entail?

It's almost like, especially in modern languages, a lot of us have come to really...

be spoiled with these concepts of very powerful list collections that you see from functional languages.

So mapping and filtering,

and reducing.