 or how do you identify yourself, OK? So you're interested so that you have a team that, OK. All right. Which of you are working with Java, OK? My examples are Java, but you have similar tools for other technologies, usually at least. And the tools that I'm going to show they're not really the point. The point is having a tool, not the specific tool. So I think we're fine. Just out of curiosity, what other technologies do you work with other than Java? Ruby. Ruby, OK. Ruby. Groovy, yeah. I'm working. OK. Yeah, well, in certain communities, apparently the way of living is that you always build your own tools. I've understand that C and C++ generally go in that direction after some fundamental tools like the compilers in place. And some other communities like Java, they perhaps the usual way of working is you take the latest popular build tool, but you never touch it. You just take what comes out of the box, but you don't really extend the tools much. Yeah, the point is the purpose, not the way you're getting there. I guess it's 30 pass, so we should get started. I'll first tell you a bit about myself, mostly about my background. So I've been earning a living doing software stuff for more than a decade. I've been writing code for longer than that. And even though for the past maybe seven years, eight years, I've been mostly sort of working around methodology things, training methods. I'm also a certified scrum trainer, but don't call that against me. I've been doing a lot of non-programming work recently, but I also do still frequently work with teams, usually not full.