Hello and welcome to the ThoughtWorks podcast. My name is Mike Mason and I'm one of the hosts

of the podcast and I'm here today with Rebecca Parsons, who's the CTO of ThoughtWorks. Hello, Rebecca.

Hello, Mike. And I'm also here with Evan Botcher, who's the CTO of ThoughtWorks. Hello, Rebecca. Hello, Mike.

And I'm also here with Evan Botcher, one of our technical principles from Australia, although, I mean, we change job titles all the time. Are you still technical principle, or is some other...

That'll do. I take care of engineering across Australia at the moment. Excellent.

So we're here in Shenjin, China.

We've been locked in a room together.

We're part of the Doppler group that creates the Filtworks technology radar.

When we do the radar, people suggest technologies that are moving and interesting now,

or they suggest techniques, things in a positive light

or possibly in a negative light. And one of the things that was put up this week started off

as Node for All the Things, which was, I guess you could call it a technique or a set of

architectural decisions where organizations are

choosing to use Node and JavaScript throughout their technology stack because they feel that

coalescing on that one specifically the language choice around JavaScript will provide them

with a productivity benefit. And I think we talked

about that whole node for all the things for a little while and ended up, ended up with a different

name, a monoglot monopoly, which I believe came from Johnny Leroy because he's our Department

of Naming Department. And so we talked about monoglot monopoly.

And unfortunately, while that's awesome alliteration, it's actually a very bad name because it's

repetitive.

Monaglot means there's only one.

...