 Hello, as well. Oh, sorry about the delay. And thanks for coming to ThoughtWorks. So tonight is about the latest edition of the ThoughtWorks technology radar. So just want to have a show of hand, how many of you have heard of the tech radar? OK, it's quite a number of people. So I'm going to give you a brief introduction of what this is really about. The technology radar started as an experiment by ThoughtWorks. It is really our collective opinions on some of the technologies we have used in our projects and things that we like, things that we don't like. And after a while, it has become a project on its own. And people now started paying attention to these things. And about every six months or so, we do a community event like this to talk about what we have learned in the last couple of months in the last half a year. So it's put together by the technology advisory board of ThoughtWorks. It's about 20 or so senior technologies coming together in a face-to-face meeting. How many of you are using agile methodology in your workplace? Quite a lot of you. So you'd be very familiar with sticky stickies on the wall. So they consume a lot of stickies, and there's a lot of very heated debate about is something really a platform or is it a tool or is it a framework? Do we like it? Do we have enough experience? There's only enough space for a small handful of blips on the radar. So there's a heated discussion about what blips we keep and what blips we call and what is the message we're sending to the developer community. So that is the tap face-to-face meeting. You may or may not see people like familiar faces. So on the tap, you have famous people like Martin Fowler, Jim Highsmith, Rebecca Parsons, but there's also a lot of representatives from different countries. So this is really about our opinion and project experience. It's called a radar because we stole the metaphor of a real radar. And the structure is a series of rings and also the four cauldrons. So the cauldrons are techniques, tools, platforms, programming languages and frameworks. As I said, it's not always clear where certain things are. Sometimes it's really about opinions. And because these are our opinions, these are our actual experience on the project. There's no such thing as, how can I get my library onto your tech radar? It doesn't work that way. So if you want to get your product or you want to get your libraries onto the radar, well, then put it on GitHub, share, and we'll use it and we'll find out and maybe we'll put on the radar someday. So within the radar, you have the different rings. Typically, a blip starts from the access ring. That is when some of us may look at a library and we have some good experience. We play a little bit around with the library and we use it in an early stage of a project. And we say, yeah, that seems quite interesting. Let's put it here. As we gain more experience, we start to use it in a few more places in a different context and we start to move the blip into the trial ring. That is when we start telling teams, telling companies that this is an interesting technology. You may or may not like it. It may not be applicable in your environment, but this is something that we think you should pay attention and have a trial. The innermost ring is the adopt ring and that is when we have used these things so many times in so many different contexts that we think you really should use it. This is your default choice of doing things. So we have an internal rule, an in-joke that says if you don't use this technology in your project, we're going to laugh at you in the pub in your face because these are technologies that we think are really applicable. Firstly, on the outermost ring, we have the hold ring. These are some of the anti-patterns that we see in some of the environments that we work with and we just want to let people know that if you do these things, it comes with certain cost. It doesn't mean it is always wrong. It just means that from our experience, we have suffered and we know that if you do certain things differently, you get better outcomes. Just like a real raider, blips fade after a while when there's no activity. So if you have a library that you like, you may be wondering why isn't closure on the raider? It's because it's been there for several years already and it faded to make room for new blips. Along with each addition of the raider, there are several themes as well. So in this current raider, one of the themes is conversational UI and natural language processing, which is an area that we have quite a bit of experience in the Thoreau Singapore office here and that is what we're going to focus tonight. So with that, I'm going to hand it over to my colleague to talk about conversational UI and NLP.