Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! According to Mathijs Sonnemans, his job is to make people happy by building awesome products: What’s the value of innovation if no one can access or truly benefit from it? After studying computer science and philosophy, and spending years developing software, I’ve learned that "coding" is the easy part. The real magic happens when you turn that code into a product that genuinely helps people, excites them, and is supported by a sustainable business. Language technology is where I’ve found my home. It’s a field that brings together the subtlety of human communication with the precision of tech - something that’s far from easy. I’ve become an expert in this space, and my mission is clear: to make language technology more powerful, intuitive, and accessible, so it can keep making a positive impact.
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Hi, everybody. Here we are again. I would say today, this is a bit of a very special episode because I usually invite people I've met in other circumstances. But this time, I actually met Matthijs. Am I saying it right this time? Saying it really right. This is really hard. We're going to talk about this. But the truth is that I'm Under other circumstances, I was in a presentation of one of the projects involved with Blackbird, so we're going to talk about that a lot. But
the idea here, as we all know, is to get to know the man behind the projects, right? And talking about having something behind, the other time that we were together, our conversation started because I am someone who really appreciates musicians and music and instruments and studio environments and microphones. And therefore, of course, everybody started the conversation, even if it was about technical stuff in languages, we started by talking about his guitars. So I guess it's only fair.
that we do that. So let's hear the correct way to pronounce his name, where he's from, and why these guitars are here. So good morning, Matthijs. Thank you so much for being here. Such a pleasure to see you again. Yeah, thank you. Good morning. Yeah, I am. So the correct way to pronounce my name is Matthijs Solomon. I find that non -native English speakers always get my name right, but native English speakers have a lot of trouble with Matthijs. They tend to add a diphthong to
it. So if you get yourself saying Matthijs, that's okay, I accept it, but it's not right. So because I'm Dutch, I'm from the Netherlands, I always say that my accent and the Dutch language is as flat as the country is. So that's why we don't do diphthongs at all. So that's why it's Matthijs, not Matthijs. That's why you go. Okay. Yeah. And I inherited that name from my father and my grandfather and my great grandfather. They are all called Matthijs. So yeah. So you could have been Matthijs the fourth. Yeah, yeah, no,
we have a very like, I can go so deep into naming culture of the Netherlands, like probably every country has different naming culture, but because my fiance is actually American, there's always, you always see the contrast with other cultures, right? And even though American and Dutch culture don't differ that much, the places where it does differ makes it just more interesting and more makes you realize how fascinating that is. However, your last question, of course, was about the guitars. How did they end up here? I've been a guitarist for a very long time. I think my
first guitar lesson was like when I was like probably eight years old. So that's quite a hefty chunk of my life where I've been playing guitar, been in multiple different bands at the moment, still looking what my next project will be musically. But yeah, I'll get there. So what style is it? Is it more rock and roll like that one guitar will... make us think or is it that one yeah yeah so my flavor over there i would be lying if i wouldn't say that my specialty is metal uh guitar and so uh yeah that's a little bit
also what you see in the in the guitars themselves so this one's actually very special because it's an eight string um yeah probably from the traditional recording you can't see that well but yeah it has eight streaming is really quite big and heavy um why do you need eight strings Well, in certain genres, particular sub genres of metal that is more appreciated because you can go even lower. So, yeah, that's that's why I play an eight string mainly, actually. So you don't sing your guitarist and you don't sing? No, I don't. You do the chorus
every now and then. There have been some occasions where I have been doing some backing vocals or backing grunts on stage, but I definitely don't consider myself singing now. So you're a really young guy. But I'm just wondering, I mean, I know it was not long ago, but what kind of child, I always ask this because I love it. It's like, what kind of child were you? Were you, you know, musically inclined or all of this only came much later? Did you enjoy technology? Did you like
languages? Were you born in one of those multilingual families? Or no, it's probably like me, like my family is only Portuguese and everybody is. I also inherited my name from my grandmothers, both of them. So both together. compose my name. And so I mean, is it a more traditional approach? Or did you have one of those upbringings where you were traveling the world or diplomat father or? Well, I wouldn't I didn't expect to be reflecting on this this morning, but this is actually quite interesting. So that's the idea that you didn't
expect. Yeah. What came to my mind is that we recently saw some old videos of me when I was really little. I think like it must have been two, three years old. I cannot really estimate my age from just the recording, but I was walking already, so at least. And I just saw it was my birthday, and everyone was excited. Like, look, we got festivities and balloons and everything. And I was just very calm and just being like, oh, cake. But any other child would have been
totally crazy, probably. But in that, my fiance said, you can really see my character. I'm very... calm person in that sense. And from another video of that, I saw myself speaking a dialect of Dutch, which I didn't realize I actually spoke when I was that young. So my father was in Bergen, which is a particular region in the Netherlands where they have a regional dialect, which is
very distinct from Dutch. It is not officially formalized as a language because there was never consensus so that you know what's dialect what's the language you always have that discussion but regular Dutch people do not understand Limburgian that that's the thing I do understand it because I have heard my dad speaking for all my life but back apparently back then I actually spoke it which was a new revelation to me so that really asking about language that brought me back to that memory in that video that I saw So that
is actually quite fascinating. Fun fact, Limburgian is a tonal language. Yeah, there's actually tones in it. Any few examples that you could help us with? Oh, the most famous example that I heard is that I could talk about a graaf and a graaf, which is a different tone. And one of them means count, as in the count of a castle. And one of them means grave. And the Limburgian can hear the difference. Of course, context matters. But
apparently it's been proven that someone who speaks that dialect or speaks a tonal language has an easier time learning other tonal languages. Just a little fun fact out there. So your pass is a bit of a obscure one when it comes to water linguism, right? Yeah, it's a super obscure language. It definitely helped me. So I would say the rest of my upbringing, not any, it's very traditional, I would say, just, you know, I always get the
statements thrown at me that I've never lived more than half an hour from my parents. But in the Netherlands, that's not really difficult, because everything is really close. I don't, and I've lived very far away, but that's also common here. Yeah, yeah, exactly. So it's, I've never, I've not lived abroad yet. Maybe that will actually happen sometime soon. Who knows? In high school, I had trouble with language, I would say. Like my French and German was really
bad, really bad grades. I did take Latin and Greek as well. So in Dutch education, that's possible. I dropped Greek as fast as possible because aoristis, for anyone who knows, you know. But that didn't actually did for us for six years and I really enjoyed it. I love that. So somewhere I think that didn't really helps you get an understanding of language relatively fundamentally because you're not speaking. You're just dissecting. But still, I thought I was really bad at language.
So my focus was really on the technical subjects, right? Math and physics, et cetera, computer science. So it's also what I ended up studying. and I ended up studying computer science. Also still my love of philosophy never went away, so I also studied philosophy as well. But my language came around the corner again because I just for fun started to pick up Spanish, you know, with Duolingo as it goes. And I was like, hey, actually, this is really, really, really fun. So did some courses, also went to Spain
and slowly picked up my languages back again and just love speaking to people. I found out at university that actually, wait, I am a very big extroverted person. So I love speaking to people. And I'm one of those people who thinks that if you speak three words, you speak a language. So I try to use them all the time. Like immediately I will try to speak your language. So you do the most out of everything that you know, right? You make the most. Yeah, exactly. I would say that my Spanish is quite good. My German is also... good for a Dutch person. And French, I'm actually
back in class again, so I'm taking once a week French classes again. So I've really found language again in my life, even though in high school it really didn't work for me. I do feel like I'm a very linguistic person right now. And of course, certainly my field that I'm in, the industry that we are in, helps with that. Even though I'm never at the actual linguistic side of it, I'm completely at the technology side, but it's funny how it all coincided again. I know, but I heard you saying that you obviously had a lot of options when you graduated and then somehow
you ended up joining this crew because they were, I suppose, in your eyes, special. So what's the story with joining Blackbird and who are these people anyway? Who are these people? So I worked at an LSP first. That was my first job just as a software developer. So I got to know the language industry from a very direct side, working in the same room as project managers and understood
exactly what they were talking about and the pain points, et cetera, seeing where most time was spent. And my whole job was trying to teach them or not, sorry, not teach them, build things for them to make their life easier, right? To make the whole process easier. That was the whole point. I basically thought at some point, like, I can do this for one company, but what if I can do this for the entire industry? That was basically the starting point. And by then, I had met Bruno Bitter already, who was the co
-founder of Blackbird. So we got to talk and basically said, well, actually, it would be very interesting to help each other here. And that's how I joined Blackbird now two and a half years ago. Yeah, like I said, it's basically co -founded by Bruno Bidder and he used to be a serial entrepreneur. He had multiple companies, but he also at some point was the chief operating officer at MemoCube from which he started the whole North American
division. That's just what I know. I wasn't present at that. It's company history. It's company history. But that's where he realized that there's a really big connectivity and integration issue in this industry, which I really adhere to as well. Like, yeah, I think this is the biggest problem. I think language industry is 50 % language and 50 % technology because all the linguistic things are stored somewhere in the computer. I mean, very little pen and paper work happening anymore.
So when you joined, where were they? Because I've heard from a little birdie. Well, I have a friend, as you know, who's an evangelist for his project for Blackbird. And he said that what we heard from you because We were in a session when you did your demo. And he said, oh, what you heard two weeks ago is now almost old news. So there's lots of new developments. And I was like, whoa. So what could have been things like two and a half years ago when you joined? I mean,
at what stage was there a commercial product already? No, no, no. So I joined as basically, so at the moment I joined, it was just developers, practically. And I was initially joining with the idea that, okay, it's very soon, very soon we're gonna have customers and then the customers will need help on using Blackbird. Of course, the whole idea of Blackbird being for those who haven't heard of it, it's a no code orchestration
tool where you can integrate applications and heavily focused on language industry, heavily focused on content. not in a one -to -one way with each other. So we don't do connectors. We hate to work connectors. We allow you to build workflows that really truly go from end to end. So when the content is created through all the different phases, we do an interaction with machine interaction on how the content is processed and then back when the content needs to be. deployed somewhere, the content needs to be visible to users or sent somewhere. Then even then after,
you can then start gathering data about the content, how's the content performing, and then use that to make new decisions on it. That is what Blackbird does, no good orchestration tool. The idea when I joined was that I will definitely help the first clients to set up those orchestrations and finding the best ways. to implement the best processes basically because I came with actual industry knowledge. The most developers that we're working on back then did not have that industry knowledge. The starting point is always the same for software project that doesn't really matter, but at some point you need that expertise.
That's what I came in with. The idea back then was that we were very quick to have the first customer. But that was not the case, so it took quite a little bit more because I said, well, this is not really working yet. We need this and this and this and this. So that's also how I became basically the product manager of Blackbird. So I'm responsible for I often say 151 products, namely the 150 integrations that we have, and
the product backward itself, like how do people experience it, interact with it? That's the one, 151, right? So one is the one, and then 150 is everybody else that gravitates around your... Yeah, yeah, yeah, exactly. So right now we've grown, so the first real commercial... endeavors were a couple months later, really, we started going to visiting conferences. Like the actual first conference a month after I joined was at Ork World San Jose, where it was just literally
me and Bruno, me with a backpack, going to people at the conference, saying like, here, look at what we got. And people were like, oh, this is really cool. This is interesting. And it's fun to think back about that time and now seeing where we are now, where our name in the industry is quite recognized. And we have fantastic customers who are building really great orchestrations and that's really great to see a product and the company grow like that. So you guys somewhat launched the first version since apparently there's
new versions every day almost. Yeah. I suppose that comes also from the feedback that you get from your customers and their needs and all of that. And I suppose that each customer that you have will bring you new challenges and new needs, right? But you have to go from somewhere. So what was the first version like instead of the 151? The fun thing there is that we know exactly which are like the problematic tools in the industry because they're like the API ability of it is
like very difficult because they use honestly archaic architectures. So those two were basically Plunet and MemoQ. It's very hard to connect to those systems. So we basically said those need to be the first. And once we can do that, we know we can do everything else. or that was at least a thought. Of course, every system has its quirks. And I can tell you a lot about all the systems, but let's not get too technical here of what every system's quirks are. That would also not be fair. Everyone can always ask
me to send a message on LinkedIn. Let's say that. But back then, we really built the first version really around Pluton and MLQ, right? So that was also the first clients that we knew we were going to have, like they're using Pluton and MLQ. So let's just make sure that there we can create the orchestration idea. So the first version of Blackbird was really centered around that specifically, and couldn't really do that much else. So the customizability around the beyond. through the Memo queue was just things that were
standard REST APIs. The first version also had that, so we could really quickly build something with standard REST APIs that were just following, like I said, the standard. And then you really quickly find out that most of them don't follow the standard. So if you have any system that's just based on, yeah, just give the endpoint and the shape how it looks like, and we'll do the REST, that just doesn't work. You cannot really orchestrate with that. So that's why our biggest
most impactful feature was actually by our lead developer who came up with the idea, like, well, that's just the boy code. It's that. So every integration is just some code that we build and customize so that we can create. a seamless experience with what the user wants to do and how that technically translates into API endpoints. But only you have to worry about coding, right? We say that a lot. So we even yesterday had a call with a very large
LSP who is very used to doing all types of technical tricks and then having to realize again like, oh wait, Blackboard takes care of all of that, right? So that's our responsibility. So for example, when you translate a file, for you it's just translate the file. I mean that in the backend, there's like multiple API calls and polling happening. That's just hidden for you, but in a good way, I think. While we still try to make things as non -opinionated as possible. Like, you should be able to build anything with it that a programmer does, that I as a programmer could build, you
can build it backward as well. So we're still working on that mission. There's still things to be done. So where back then it was possible to, you know, send a message on Slack, translate a file with DeepL, and then create a project or an order in PluNet. Right now, we're in a place where, like I said, we have 150 apps and we have interoperability for most resources. So if you have, for example, a turn -based, then you can just export it from one system and import it into the next one, no problem, even though
the developer knows that would never work, we made it work. And right now, we're working on full Exif interoperability as well, so that even if you export your Exif for MemoQ, you can still import it into, let's say, phrase, even though those Exifs don't talk to each other, we make sure and take care of the conversion. So that's what you do. You make things talk to each other, right? Yeah. So how do you recruit your apps, if I can say that? Is it something that they will give you like a permission for? Are you considered partners or you just create the ability
to, you know, connect to them and therefore have them in your pool of possibilities? Yeah. Important thing here, you always bring your own connection, right? So it's not like you have Blackbird there for you have 150 subscriptions. No, you have those subscriptions separate and you choose which one to connect with Blackbird. Yeah, you don't get that. So basically, the clients themselves already have to have their licenses, whatever they need to make these things work. You guys come in and make it orchestrate. Like you say, I love that word, right? It's very musical. Yeah,
exactly. Well, we come in, but... We shouldn't have to come in. I mean, I think fundamentally, from a product manager perspective, if you have a product that you need to also provide training for, like fundamentally, and I know that some software companies do this, where you have to pay for the training to use their product, then you have a bad product. Right? It is a strange concept, I have to say. Yeah, so we have, of course, extensive documentation and we have, of course, a team of people who do want to support
you if you really want that. But in essence, it's not necessary fundamentally, of course. We can always do better. But that is the idea of we don't come in. You buy Blackbird and then you have the ability to connect your systems in a way and create very strong orchestration. What I see is interesting when I talk to clients is that They have a process already usually, but the process is often shaped by a lack of interoperability, a lack of automation orchestration.
So I had a client that was saying, well, I want to download my files from Google Drive and then put them into XTM, for example. That's what they said. And I said, OK, well, we can do that. And we were working on that. I was like, why are they in Google Drive in the first place? I said, yeah, because that's where people put them from JIRA, we put them in Google Drive and then we can download them. I'm like, why don't you just take them immediately from JIRA, right? Oh, right. So people are not enough thinking about the full workflow because that was not how we used to
do things in the industry with connectors because you connect to something and you just grab the thing that your TMS is able to connect to. So historically, the workflows were a certain way and then people, you know, instead of considering them just legacy and putting it there, It's just that they are trying to somehow keep parts of what it used to work. And sometimes it's just making things difficult. And of course you guys come with fresh eyes and immediately. I often think about the quote in the matrix, like truly
free your mind. Like you're constrained by the technology that you had, but now think of your ideal workflow and go build that. And that's hard for people to do. It's very hard. Yeah. Yeah. I mean, of course. also because you have an overview of what has been possible in the evolution of your services. Therefore, you have a much more open -minded, imagine someone, you know, business as usual. And now you could have done it in a more, you know, efficient way, but you just are so used to that mentality that it's
hard. That's the trickiest part. Like people are then like often saying, but I don't know what's possible. And I said, well, everything is possible. It's it's programming here, of course it's magic like that. And then there's only one asterisk. It's the limitations that the API puts on you. So if we cannot do something with the API, then we cannot orchestrate it, but no one else can either. Like it's just not possible. And okay, but what's then not possible with the API? And that's where really my expertise come in. So I can then tell, okay, you could do this and this. Like I want you to give your ultimate
process to begin with. Let's use that as the blank slate and then see, okay, you want to do this with this TMS, but actually this TMS does not allow you to do that. So therefore we'll have to come up with something else. Yeah, that sounds like a good way of looking at it. It's like, tell me what you want and then take from there what you know is possible. Tell me your ideal scenario. And sometimes we'll come with things that are fundamentally difficult. So something we get a lot is like, I want this term, this TM, I want to take the TM and put it into another
TMS. I will then say like, so the last thing there is most TMSs are very protective of their TMS so that you don't allow, yeah. They don't like to import and export them as easily as turnbases. Although some are just feeling free with it. And that's nice. So you can just, because the whole idea is that a TM is your property, right? That's what the whole industry has been telling you. Secret, it's not like. It doesn't work like that because - Sometimes it's not as necessary, especially these days, as you think it is. Well, I'm starting to get to that too, right? Exactly
that too. I am very skeptical about TMS, but then - Necessary as you think it is, and sometimes it actually is hurting your projects, I believe, in many circumstances. I think so. I mean, and then the real kicker is that even if you were able to export a TM from one TMS and then put it into another, your match is going to go way down. Why is that? Because both TMSs segment in a different way. So when you have a TM, you're actually in reality completely bound to that TMS. And that's super important for people to
know. It's not like, oh, I'm building this resource and I can then always use it. No, you cannot. That's not really how it works. It's just a TMS. I think we have to think about how desirable would it be any way to keep this information? Yes. That's why I'm also talking to clients and they basically still have a TMS and the only reason they have it is because of their TM. Then I just tell them, okay, because all the other things are just outsourced. They use vendors and the integration is done with Blackbird. So
the only reason they still use that and have that key aspect that TMS inside their system is because of the TM. So then I say, well, then it's just a sum for you. its calculation, how much do I pay for the TMS and how much value do I get from the TM? Then it's basically, if that is sufficiently large, of course, also considering the overhead, then keep it. Otherwise, draw your own conclusions. Exactly. I'm with you there. It's maybe not as necessary and beneficial. as
it might seem. Or it used to look that way under certain circumstances, like you say, when you know everything is very static, right? Then you work within this system and nothing had to connect and it was already, you know, huge when you had the possibility of having those. But right now with other possibilities and ways of thinking also. I think for enterprise customers, the TMS value has gone way down. To me, it's oversold. If I would be in charge of enterprise localization,
I would think three times before I would put a TMS in my system. Because if I'm using vendors, again, if you're doing it all yourself, different story. But if I'm just only using vendors, all they're going to do is just take out the thing. They're not actually going to translate inside your system. Maybe they do. There are cases where that actually happens. But they're going to just take it out and we help a lot of LSPs with that. I want to take it from this TMS and put it in my own TMS and then have my TM there. What is really this TMS into your workflow in your toolchain?
There's a conversation to be had about TMs and TMSs that I don't think it's being talked about right now. I mean, it's always funny to me that even Hummel who invented literally the TM and the TMS, he regrets it. He thinks it's an archaic system. He's doing all other things right now. So I think that's also telling. But it was, you know, I understand that it was a really important stepping stone, right? But there you go again, people are a bit attached to how things used
to be. Oh, but I know, I mean, I don't know, but you told me that there are... There are things boiling in your mind when it comes to the future of the industry and ties in the industry. So let's hear about that. I don't know if they have anything to do with Blackbird directly. Of course, they do have to do with Blackbird conceptually, because this is where your thinking bank, right? Obviously. But so what's the story? What plans are these? What can we expect from the guitarist from this location right here? Let's go back
to the fact that I used to work at an LSP. So I saw firsthand what was actually happening. And I started to figure out how the industry looked like zoomed out fundamentally. And I basically just started to notice and a little bit track as well, like what does a project manager do all day? And of course, this probably does not apply to every company. Let's hear what you have to say because I was a project manager in two completely different scenarios. Let's validate my theory here. So I think, first of all, what
is the fun part about being a project manager? Like, what's the awesome part? And I think that's just really talking to people about, you know, we've got this amazing project. we need this in this language because they're the expert on this and I know they're the expert on that and they will do a good job because I know them very well and at some point they'll call me and they have some questions about, hey, what does the client really want and let's just get the linguistic thing completely right. That's I think the awesome part of being a project manager. The not so awesome part is the actual overhead of all the systems
that you have to do data entry in, which I think computers can do better. But what I saw is that for most, of the time spent in the actual office. People are just, they got new projects that they needed to assign to people and they needed to figure out, okay, who to assign to. Most important thing is who has time. Who can do this in this short time or long amount of time or who's the best suited for this? And they started to email people and to call people like, hey, this is
a rush order. Do you have time? and we had the system where we would send emails to a whole batch of translators and whoever picked it, they would get it first. I mean, this is all very recognizable properly to everyone in the industry. Now I thought, okay, this is interesting because the system we used had the whole availability thing implemented. Why is that not used? But it's not used because most translators are freelancers and they have different clients. They have multiple clients. I work with multiple LSPs and some direct clients. That's how linguists work and how they
should work. If every LSB uses a system for availability, almost every LSB has a sort of portal for that. And I'm a translator and I have, let's say, 20 LSPs or maybe 10. I don't know the exact number. I have done some research, but then I certainly have to maintain my availability for all 10 different portals. The moment I get a job, in theory, I need to update all 10 different portals to say, I'm not available anymore. Nobody does that.
That's why people are still e -mailing each other and calling each other, do you actually have time? Fundamentally, it's because all software right now, translation project management software, all translation business management software, all general productivity tools, all general product management software. They all make one fatal flaw in their assumption, and the assumption is everybody works for the same company. And that's not true. But because that assumption is made, we're creating a very inefficient process,
right? So basically, now this is where I come in. And I say, well, what if we have a productivity tool, a project management tool, however, that does not make that assumption and says instead of just one team, one tool, we actually have the thing that made the internet what the internet really is good at, a network. So I have one place where I can check off my tasks, the things I need to do for all the clients that I have and
all the clients that I'm connected to. So it's a project management software for or network for freelancers? For freelancers, but also at SPs, of course. So it's because they actually get the real benefit. So it's basically a network of people giving each other tasks, working on projects, and at the same time, therefore also immediately seeing people's availability as so far that the freelancer wants to share any of that information. So I'm basically working on a system that makes that whole aspect, the human
aspect, the interaction, the project management aspect for the entire industry better, I think. And of course, this works really well in translation industry. I think there's more places in the world where companies work with each other on projects rather than only alone. So in short, that's where I came from. This is my inspiration. And I'm now turning this into an actual product as well. basically where people just have their own account. Something actually I figured out when talking to a lot of translators, I went
to translator conferences, I did a lot of research here, and something that was very interesting to me is they said, well, in this relationship of me and an LSP, and the LSP has this portal, and I am supposed to input data, we have invoices, and we have availability, I don't own it. I don't own the technology. they own it. If they make a change to it, they can just say, yeah, this is the truth now. And I cannot discuss any of that. And there's one reason for them to really
be hesitant to use these portals. So I literally also want to create more of an equal place where everybody is just as much of an owner of the technology as the other party. So we bring translators and LSPs more on the same level technology wise, but also therefore ownership wise and therefore have a just really better place to communicate with each other. Because I know about the issues that are there with translators and LSPs and that relationship has never been super good. So also something I try to hopefully make better
in some way. Wow. Sounds amazing, because I can only imagine. I mean, I'm an advocate. Of course, I was a project manager and a venture manager, which means that's what I did all my life was to somehow think about this relationship. I'm with you. So I guess we do worry about the same things, you and I, somehow. We do. So it's very interesting, this idea fundamentally that you're saying that both parties would be like. players in this one network as opposed to the super fragmented
idea that LSPs are on the one side of the realm of business and freelancers are on a totally different level when more and more, especially these days, These two players or these two types of players are actually businesses in themselves. So freelancers these days, especially the ones that are going to be able to keep going in this more, like I say, technology conscience world, right? Because I always say that it's not like. all of a sudden technology exploded. It's just
that the mainstream is more aware. For us in the industry, we were always very aware. We had to deal with it on a regular basis, on a daily basis, but the clients were not as informed, right? People who had direct clients didn't have to deal with certain things. LSPs didn't have to deal with clients knowing. the mainstream technologies and what they can do. And these days, this is exactly what it is. So it's only fair that the people who are able to keep building their careers within the industry actually somehow level up, right? So I like it. I guess it goes
into that sense. So I like it. It's great to hear about all the things that you have to do, but I'll just ask this before I go. How close are you to creating, let's say, commercial products? This is a really good question. I've been working on it for a while. There's definitely already a lot there. I'm starting Pilots this year. This summer, I have some interesting LSPs who have been... Oh, I've befriended over my time already
in industry. We're also interested in this and I want to try it out, see if it works. That's very, very important to me, of course. How do you approach the LSP and the freelancer like in separate entities or is it if the LSP adopt it, then the freelancer is working for them, we'll adopt it too. That's also the idea, but I basically talked to both equally because both have vetted. things to contribute and feedback to make this whole, because it's all about the relationship, right, between the two. So I work with freelancers and I work with LSPs and I will
pilot with it first. And my goal is to have a first beta release by the end of this year. Probably, yeah, not open to everyone immediately yet, but invite only. So anyone listening who's interested, let me know. We can work together on making this like a very awesome way to connect to each other. And to have basically really serious efficiency gains. That's really the modernist way of looking at capitalism. But I just look at it as in terms
of I see a lot of struggle in the relationship and I see a lot of struggle definitely in the overhead that it creates both for freelancers and for project managers. And we can just make each other's lives a little happier by just doing things more efficient. Mm hmm. The other day some, well, one of the, one of the, one of our friends was actually talking about, he's an expert in interpretation. And I was like, thinking about these major issues for text translation for, for obviously for translation, imagine for interpretation,
right? So I'm sure you've thought of that and there's probably a part of it because some people actually do both and other people only dedicate to one of them, but they have somehow. the same problems, but when you talk about interpretation, then you have extra, extra, extra problems that have to do with availability, right? So it's like the on the spot kind of situation. So if everybody is aware of what is really going on with everybody else as a team, even if they're not part of your company, then it would be the ideal situation. So I'm sure a lot of people
will be contacting you about this. And so we like to know. what's going on and to check what you're doing because it's always very nice. And I know that your brain must be always boiling. Like you don't have enough work doing your job and you already have all of these. My thoughts are always like three steps ahead of where I'm actually at physically with like the product. So I should not... go too fast in that sense, like, okay, just make the fundamentals right. And then looking for the band, right? At the
same time. And then looking for the band, that too. Yeah, I still also need to do that. It was also my New Year's resolution, like, okay, need to figure out musically what I'm going to continue with. Yeah. Yeah. Well, very nice to get to meet you a little bit better. And it's, I think it's very original to have someone who actually, original for me, right? The podcast, to have someone who really comes from this full -blown technology background and then gets interested in the industry and decides to, you know, service the industry
in such a positive way. I love it. Everybody loves the language industry. If you're inside, you're inside. Yes, I guess it's one of those things you don't want to leave unless you're really forced to, right? I guess we're holding on for dear life. Thank you so much, Matthijs. And I'm sure I'll hear and see new things from you very soon. And hope everything goes OK. And let me know when you find this band so I can
listen to what you guys do. Great. And thank you for having me. It was a really pleasure. OK. Thank you so much. And I'll see you around. Have a great day.
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Common terminology status values include preferred, admitted, deprecated, and forbidden. In the context of...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Terminology decisions are business decisions and leaving them unmanaged can come at a cost. In this episode, I...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! Terminology management doesn't happen in isolation. In this episode of The Language Worker, we look at the...
Got something to say to this podcast? Send a voicemail, and you might hear yourself on the next episode! In this episode of The Language Worker, I sit down with Sonia, a German and Italian native speaker and performance...