1 00:00:00,000 --> 00:00:04,520 Hey everyone, this week we have one of our interviews with a SpringOne Platform speaker 2 00:00:04,520 --> 00:00:09,040 where you get to not only hear a little bit of what they'll be talking about, or preview if you 3 00:00:09,040 --> 00:00:14,240 will, but some about themselves as well. Now we have SpringOne Platform coming up in my hometown, 4 00:00:14,540 --> 00:00:19,860 Austin, Texas, October 7th to 10th. Now if you're listening in the future, this is in 2019. 5 00:00:20,500 --> 00:00:25,580 Sorry if you missed it. You have to write a letter to me, tell me how 2025 is doing. 6 00:00:25,580 --> 00:00:30,940 Always curious. Anyhow, you should take a look and register for it. If you register before 7 00:00:30,940 --> 00:00:37,020 August 20th, you'll get a nice discount from it. Otherwise, if you just go to springoneplatform.io, 8 00:00:37,320 --> 00:00:42,920 you can sign up for it and come see us in Austin. So with that, enjoy the interview. 9 00:00:43,520 --> 00:00:47,560 Today I'm joined by Madhura Bhave, one of our Spring team members who will be presenting at 10 00:00:47,560 --> 00:00:53,020 SpringOne Platform. And we're just going to talk a little bit about Madhura, her background, 11 00:00:53,020 --> 00:00:57,900 and what she's going to be talking about. So Madhura, if you would start us off by sharing a 12 00:00:57,900 --> 00:01:01,020 little bit about yourself. I know that our audience would love to know more. 13 00:01:02,520 --> 00:01:09,680 Yeah, sure. Thanks, Mark. Thank you for having me. And I guess I'll just introduce myself for 14 00:01:09,680 --> 00:01:16,800 starters. So as Mark said, my name is Madhura Bhave, and I am a member of the Spring Boot team. 15 00:01:16,800 --> 00:01:24,280 And now I'm also working on Spring Initializer, which is the library that powers start.spring.io, 16 00:01:24,480 --> 00:01:31,800 which is probably the second favorite place on the internet for a lot of you. I think I started 17 00:01:31,800 --> 00:01:41,620 working on the Spring team about three years ago at Pivotal. But I've been at Pivotal for six years 18 00:01:41,620 --> 00:01:52,680 now. So I joined in 2013. I know it's been a long time. I just finished six years this July. And before 19 00:01:52,680 --> 00:02:00,620 Spring, I used to work on Cloud Foundry. So I used to work on UAA, which is the user authentication and 20 00:02:00,620 --> 00:02:09,760 authorization component of Cloud Foundry. And which is one of the few Spring projects on Cloud Foundry, 21 00:02:09,840 --> 00:02:15,100 actually. So after working on Cloud Foundry, I really enjoyed working on Spring. And I was like, 22 00:02:15,180 --> 00:02:19,600 hey, I would love to work on the Spring team, which is why I am now here. 23 00:02:21,420 --> 00:02:26,700 Wow. Well, I had no idea personally that you had such a background in security. That's really cool, 24 00:02:26,800 --> 00:02:31,980 actually. So I mean, that's a great introduction and kind of a background. And by the way, 25 00:02:32,140 --> 00:02:35,960 congratulations on your sixth year anniversary. That's also quite a milestone. 26 00:02:36,600 --> 00:02:43,880 Thank you. Yeah, I've really enjoyed working with you my almost four years. So I'm trying to catch up, 27 00:02:43,940 --> 00:02:49,640 but obviously that will never happen. But if you would kind of maybe expand a bit on how you got into 28 00:02:49,640 --> 00:02:55,080 tech in the first place, kind of maybe how you got into development, or if you had other roles before 29 00:02:55,080 --> 00:03:00,060 you moved into a development role, I know a lot of us have worn a lot of hats over the years. So 30 00:03:00,060 --> 00:03:04,660 if you wouldn't mind giving a bit more of your pre-pivotal, pre-spring background. 31 00:03:05,580 --> 00:03:13,900 Yeah, sure. So I've always been a developer. I think I actually got into tech a long time ago. So 32 00:03:13,900 --> 00:03:20,800 as a 17-year-old kid back in India, when I finished high school, I kind of had to make the decision of 33 00:03:20,800 --> 00:03:28,320 where I want to go next and what career path I want to pursue. So a lot of my family actually, 34 00:03:28,720 --> 00:03:36,780 they're doctors. And I was that kid who wanted to do something different. So I was like, hey, I don't 35 00:03:36,780 --> 00:03:42,680 I know I don't want to be a doctor for sure, because my family is all doctors. That's not really a valid 36 00:03:42,680 --> 00:03:47,200 reason. But I guess that was me at that time. That works for most of us, right? 37 00:03:48,560 --> 00:03:58,280 Yeah, I suppose so. But being a kid, and then I was obviously interested in science. Otherwise, 38 00:03:58,280 --> 00:04:05,200 I guess I wouldn't be here. The second option, which is pretty popular in India, if you get decent enough 39 00:04:05,200 --> 00:04:12,380 grades, and you're interested in science is engineering or computer science. So I know I wanted 40 00:04:12,380 --> 00:04:19,320 to do something different. But I guess I ended up not going too far, not diverging too far away from 41 00:04:19,320 --> 00:04:28,040 what a lot of people might consider a common path for someone who pursues a career in something 42 00:04:28,040 --> 00:04:34,660 related to science. So which is why I chose computer science. And now here I am. I'm actually very glad 43 00:04:34,660 --> 00:04:42,280 I chose it because I love being here. Just the idea of getting a job straight out of college and being 44 00:04:42,280 --> 00:04:48,800 independent and up on my feet was very appealing to me at the time. And that's actually exactly what 45 00:04:48,800 --> 00:04:57,480 happened. And I think I've been very lucky in my career to find what I really love to do. And I'm 46 00:04:57,480 --> 00:05:03,180 really happy to be on the spring team now. I'm pretty confident I can speak for everyone in saying that 47 00:05:03,180 --> 00:05:10,740 we're really happy you're a part of the family. So I'm happy to be here. Well, I mean, something you 48 00:05:10,740 --> 00:05:14,820 said actually kind of leads very naturally into the next thing I was going to ask, which is what do you 49 00:05:14,820 --> 00:05:20,120 love about this career field about your position about I mean, whatever you want to talk about, but 50 00:05:20,120 --> 00:05:27,300 what what are the things that you like best? So yeah, like I said, just a few minutes before 51 00:05:27,300 --> 00:05:35,940 I think I've been very lucky in the teams that have been on and in the projects that I've worked on. 52 00:05:36,400 --> 00:05:44,680 The thing that I like most about tech in general, though, is that it's constantly evolving, you know, 53 00:05:44,720 --> 00:05:50,740 so there's always something new that's happening. And I like being pushed out of my comfort zone. I like 54 00:05:50,740 --> 00:05:55,880 learning new things all the time. And whenever I feel like, Oh, hey, I think I'm getting good at this. 55 00:05:55,880 --> 00:06:02,280 There's always something new out there, which I need to now learn. And then I think I think that's 56 00:06:02,520 --> 00:06:10,820 what I enjoy quite a bit, being in tech, kind of keeps you on your toes, keeps you on your toes. And 57 00:06:10,820 --> 00:06:16,840 yeah, I find it, I guess, good to be challenged. But I know there are a lot of folks who don't 58 00:06:16,840 --> 00:06:23,080 necessarily appreciate that on a day to day basis. But our industry is such that with with frequent 59 00:06:23,080 --> 00:06:28,040 changes, and the never ending stream of changes, you really have to, you have to enjoy that kind of 60 00:06:28,040 --> 00:06:33,760 thing. So if I could maybe ask, how do you stay on top of it all? I mean, that's a lot of volume of 61 00:06:33,760 --> 00:06:38,200 change kind of coming nonstop, always. What are what are your suggestions, advice? 62 00:06:39,100 --> 00:06:46,460 Yeah, I think, especially now, in the past few years, or maybe it's always been like that. But I think, 63 00:06:46,460 --> 00:06:53,580 since I've been around in the industry, there's been a lot of change in the way applications are being 64 00:06:53,580 --> 00:07:00,620 built. So you started with monolithic applications, which I guess ran in server container somewhere, 65 00:07:00,620 --> 00:07:06,780 which you deployed as a war file. And then with the move to cloud and self contained applications, 66 00:07:06,780 --> 00:07:14,540 is that move to you create thing, I'm talking all about Java. So you're creating runable jar files, 67 00:07:14,540 --> 00:07:19,260 and then pushing those directly to the cloud. And then it moves from that to something more where 68 00:07:19,260 --> 00:07:24,380 you package your application as an image as a Docker image, and then push that. And then there's 69 00:07:24,380 --> 00:07:30,380 functions and serverless. So there's all sorts of things as you're aware, Mark. So for me, 70 00:07:30,380 --> 00:07:39,180 I think it's, there's always the aspect of trying to figure out what is just a hype versus what's 71 00:07:39,180 --> 00:07:45,820 really going to stick around and what really makes sense for the particular use case that you were 72 00:07:45,820 --> 00:07:51,740 trying to solve. There can be a lot of this hype created around new trends where people just jump 73 00:07:51,740 --> 00:07:58,940 on the bandwagon and, you know, the thing that say that this is the next big thing, whereas that might not 74 00:07:58,940 --> 00:08:05,580 not necessarily be true. So I think for me, it's trying to filter out the noise and trying to figure out, 75 00:08:05,580 --> 00:08:12,620 okay, hey, this is what makes sense. So this is what we should focus on. And I think it's in the open 76 00:08:12,620 --> 00:08:17,740 source world, it's more about like, reading what there's so much content available out there on 77 00:08:17,740 --> 00:08:22,620 the internet that it's more just about reading and researching, I guess. 78 00:08:22,620 --> 00:08:28,300 Yeah, which I guess if you don't mind me taking a completely self indulgent question out here and 79 00:08:28,300 --> 00:08:33,660 asking you is, how do you, how do you cut the noise? Because there, there really are so many 80 00:08:33,660 --> 00:08:39,980 things, even that are really interesting, and that may turn into evolving trends. How do you filter out 81 00:08:39,980 --> 00:08:45,740 the things that you feel like, I mean, maybe it's just a matter of, you know, you, you kind of feel 82 00:08:45,740 --> 00:08:50,140 like you see kind of where the industry's going, or maybe it's more directly relevant. But I find it 83 00:08:50,140 --> 00:08:57,020 sometimes kind of difficult with the cacophony of voices that you hear coming out and people espousing 84 00:08:57,020 --> 00:09:01,100 the latest thing. And sometimes things that look like they're going to be pretty big trends kind of 85 00:09:01,100 --> 00:09:06,860 fizzle very quickly. How, is there anything that you use kind of as a rule of thumb, or is it just 86 00:09:06,860 --> 00:09:11,500 a matter of kind of following things far enough to, to kind of see how they, you know, whether they 87 00:09:11,500 --> 00:09:18,300 start to go up or down and then? I think for me, one of the first things that the one rule of thumb 88 00:09:18,300 --> 00:09:24,300 that I follow is that if I see something on Twitter, I don't always immediately believe it. 89 00:09:25,100 --> 00:09:33,020 Right. You know, I'm, I'm not like, oh, okay, the so, so, and so, no matter like how, how many 90 00:09:33,020 --> 00:09:38,460 followers they have or whatever, I, I don't always believe it. If it's just the one person or a few 91 00:09:38,460 --> 00:09:45,900 people saying that I need to go and read about it a little bit more myself, or, you know, watch YouTube, 92 00:09:45,900 --> 00:09:53,180 I think YouTube videos, there's so many out there now, they play a pretty big role in how I learn new 93 00:09:53,180 --> 00:09:59,820 things because I just find consuming video content easier for me. Maybe I have like a low attention 94 00:10:00,460 --> 00:10:07,900 span or something, but I find it, I find YouTube videos a faster way for me to learn about something 95 00:10:07,900 --> 00:10:13,900 than maybe reading articles or something like that. So I try to, I try to see what everybody's talking 96 00:10:13,900 --> 00:10:21,340 about out there. And then I go and look up YouTube videos. And I guess at some point I just have to 97 00:10:21,900 --> 00:10:29,260 decide for myself. Well, that's actually a kind of validating for me as well, because I kind of fall 98 00:10:29,260 --> 00:10:34,780 into the same category you're talking about. Whereas I think the YouTube videos, and obviously they're not 99 00:10:34,780 --> 00:10:40,380 all conference videos, but I think there is something to be said for this constraint that we have like 100 00:10:40,380 --> 00:10:46,860 with conference videos or with just generally accepted formats, maybe where we have a 30 to 60 minute 101 00:10:46,860 --> 00:10:53,020 tops exposition to a topic. Of course, you can't exhaustively cover anything that way, but it certainly 102 00:10:53,660 --> 00:10:59,500 forces you to kind of focus to where you can learn an awful lot by, you know, maybe sitting down for 103 00:10:59,500 --> 00:11:06,860 20, 30 minutes with a video, 50 or 60 minutes with a video, and maybe kind of capturing a, you know, 104 00:11:06,860 --> 00:11:12,380 at least a pretty good coverage of a particular topic. So I find myself learning the same way. I just, 105 00:11:12,380 --> 00:11:18,860 I'm always looking for hacks and obviously you do excellent work and I, any chance I get to pick your 106 00:11:18,860 --> 00:11:26,140 brain on that, I'm going to take. So yeah. Well, I mean, kind of along that same vein, you know, 107 00:11:26,140 --> 00:11:32,140 with in terms of conference videos and whatnot. Last year at SpringOne Platform, you presented about 108 00:11:32,140 --> 00:11:37,420 mastering Spring Boots Actuator, which is a very important topic. You know, we're talking in terms of 109 00:11:37,420 --> 00:11:43,660 monitoring metrics and what have you. So how, if I could ask you a little bit of a different take on 110 00:11:43,660 --> 00:11:49,820 that, how is your thinking on that particular topic or related topics changed over the past year? 111 00:11:50,540 --> 00:11:57,580 Well, I think it's a topic that it doesn't really change that often. So the reason why we did that 112 00:11:57,580 --> 00:12:06,940 talk last year was because Spring Boot 2.0 released in, I think, March of 2018. So SpringOne Platform was 113 00:12:06,940 --> 00:12:12,860 one of the big Spring conferences after Spring Boot 2.0 was released. And a lot of the actuator 114 00:12:12,860 --> 00:12:20,460 infrastructure and the way you would write your own actuator endpoints was overhauled as part of the 115 00:12:20,460 --> 00:12:27,980 Spring Boot 2.0 release that went out. So everything that people knew about Spring Boot Actuator, well, 116 00:12:27,980 --> 00:12:34,940 I wouldn't say everything, but a lot of things that were hard to do in Spring Boot 1.5 with actuators 117 00:12:34,940 --> 00:12:41,660 and actuator endpoints, which we thought could be improved. We did that. We took that opportunity in 118 00:12:41,660 --> 00:12:49,020 2.0 and we redid a lot of the actuator infrastructure, which is why a dedicated talk for 119 00:12:49,020 --> 00:12:54,380 just the Spring Boot actuators made sense because there was actually so much to talk about. It took 120 00:12:54,380 --> 00:13:03,820 up a whole hour. The other thing that I really am and even was excited about at that time was the 121 00:13:04,620 --> 00:13:10,780 actuator integration with Pivotal Cloud Foundry. So this has been around since Spring Boot 1.5, 122 00:13:10,780 --> 00:13:17,420 but with Spring Boot 2.0 it also supports WebFlux applications and Jersey applications along with 123 00:13:17,420 --> 00:13:25,180 Spring MVC applications. And I think I spent quite a bit of time integrating Pivotal Cloud Foundry's 124 00:13:25,180 --> 00:13:33,100 UAA authentication to work with Spring Boot's actuator endpoints. So once you were logged into 125 00:13:33,100 --> 00:13:39,900 Apps Manager, which is the UI for your apps on Pivotal Cloud Foundry, you wouldn't need to 126 00:13:39,900 --> 00:13:47,100 have any separate authentication or authorization for accessing your actuator endpoints. So that's 127 00:13:47,100 --> 00:13:54,300 something that was and still is very special to me, that integration, which is why I think we decided to 128 00:13:54,300 --> 00:14:02,540 include that in our talk last year. So I wouldn't say anything's changed. We have seen what's 129 00:14:02,540 --> 00:14:08,860 interesting is once we rewrote the actuator infrastructure, writing custom endpoints became 130 00:14:08,860 --> 00:14:15,180 much easier than it was in Spring Boot 1.5. So a lot of the new actuator endpoints that you see out of 131 00:14:15,180 --> 00:14:21,500 the box with Spring Boot, they're actually contributions from the community, which has been, which is kind of 132 00:14:21,500 --> 00:14:28,540 great because a lot of folks out there who use Spring Boot applications in production, they actually know what 133 00:14:28,540 --> 00:14:33,740 information they need in production from their applications probably more than we do. So they 134 00:14:33,740 --> 00:14:39,020 have some really good suggestions about what endpoints we can add out of the box. 135 00:14:39,020 --> 00:14:46,620 Yeah, that is, that's great, actually, because I love the whole community involvement story. I'm, I'm, I'm constantly 136 00:14:47,180 --> 00:14:53,180 seeing and saying how much the Spring ecosystem is driven by the community. So that's, that's really 137 00:14:53,180 --> 00:15:00,780 amazing to, to hear how much more is being contributed into Spring by the consumers of Spring, if you will, 138 00:15:00,780 --> 00:15:06,140 by developers who are using various Spring components on a daily basis. I find personally 139 00:15:06,140 --> 00:15:11,900 actuator is such a broad topic that I, I feel like the more I learn, the less ground I cover, 140 00:15:12,940 --> 00:15:17,340 which, which is a good thing, right? I mean, the, the capabilities are continually expanding and unfolding. 141 00:15:17,340 --> 00:15:23,100 So yeah, that makes a lot of sense. Along the same lines, you know, that was last year, but this 142 00:15:23,100 --> 00:15:28,540 year I see that you're down to speak about how to get productive with Spring Boot, which is also another 143 00:15:28,540 --> 00:15:34,460 topic that I don't think anyone could get enough of, quite frankly. Uh, but I guess just if I could peek inside your 144 00:15:34,460 --> 00:15:40,380 head, just, uh, again, one more time, how did you arrive at that topic? How did you, um, how did you decide that 145 00:15:40,380 --> 00:15:44,780 that that was something that you wanted to talk about? And obviously we all need it, but how, uh, how did you, 146 00:15:44,780 --> 00:15:47,820 how did you get from idea to, uh, to submission? 147 00:15:48,620 --> 00:15:55,740 I think, uh, just talking, uh, with a lot of folks from the community and seeing how they use Spring Boot 148 00:15:56,540 --> 00:16:02,860 probably over the years led to this idea. Uh, maybe some, it had something to do with the fact that 149 00:16:03,580 --> 00:16:10,140 I did the actuator talk last year with Andy. The actuators have some useful endpoints for debugging 150 00:16:10,140 --> 00:16:16,780 your application and getting useful diagnostic information about your application, which can lead 151 00:16:16,780 --> 00:16:23,020 to productivity in one way, right? Because it gives you like ease of access to the information that you 152 00:16:23,020 --> 00:16:31,180 would otherwise need to maybe hunt for and spend more time and I guess be less productive. So I thought 153 00:16:31,180 --> 00:16:38,860 of expanding that idea into, okay, so Spring Boot already gives you a lot of things out of the box and 154 00:16:38,860 --> 00:16:46,940 it makes you productive right from the get-go, I guess, because it takes an opinionated view and it cuts 155 00:16:46,940 --> 00:16:53,820 off most of the boilerplate that you would need with a Spring application. But how do you use Spring Boot 156 00:16:53,820 --> 00:17:01,500 in sort of an idiomatic way so that it makes you even more productive? How do you, once you've written 157 00:17:01,500 --> 00:17:08,220 your application, how do you debug it and how do you grow it and maintain it? Uh, there's things such 158 00:17:08,220 --> 00:17:15,660 as IDE support for configuration properties, there's slice tests for writing faster tests and helpful 159 00:17:15,660 --> 00:17:22,140 debugging tools. I think that all of these together, um, there's like little bits here and there 160 00:17:22,140 --> 00:17:27,900 that Spring Boot provides out of the box and all of them together contribute towards this increased 161 00:17:27,900 --> 00:17:35,260 and enhanced productivity experience for developers, which I think like being a developer, I think that's 162 00:17:36,220 --> 00:17:43,260 something that most developers like to be productive. So yeah, I think that's, I think it would be 163 00:17:43,260 --> 00:17:49,260 interesting. Oh, I'm sure of that. Actually, one of the things that I always feel like we don't really 164 00:17:49,260 --> 00:17:54,700 talk enough about, and this is me personally, so, you know, 100% on target, 100% out of line, but I, 165 00:17:54,700 --> 00:18:01,180 I've always felt that, that productivity is the biggest thing. Developer productivity, developer velocity 166 00:18:01,180 --> 00:18:05,980 is the biggest thing that Spring Boot brings to the table, uh, among several other benefits. 167 00:18:06,220 --> 00:18:11,100 I really think that, uh, you know, out of all the different things you could employ to get the job 168 00:18:11,100 --> 00:18:15,820 done, that Spring Boot really kind of gives developers superpowers. And then to take that 169 00:18:15,820 --> 00:18:20,700 a step further or several steps further with a talk like this on how to get productive with Spring Boot, 170 00:18:20,700 --> 00:18:26,940 how to really be productive by the folks who are creating and extending Spring Boot's capabilities 171 00:18:26,940 --> 00:18:33,020 on a daily basis is something that I personally am super, super pumped about. So, and, and darn it, 172 00:18:33,020 --> 00:18:39,980 I had another question in my mind and you, you kind of already covered it. Uh, so yeah, darn it. Uh, 173 00:18:39,980 --> 00:18:44,860 you know, I, I, I should have hidden that better, I guess, but, uh, but yeah, I, I guess, you know, 174 00:18:44,860 --> 00:18:49,660 that, that covers the, the essential parts, uh, of who you are, what you're going to be talking about, 175 00:18:49,660 --> 00:18:55,500 what you have talked about, where you're excited about the topics in general, which I think, uh, 176 00:18:55,500 --> 00:18:59,340 is, is something that again, I, I speak for the community and this, I think we're all really 177 00:18:59,340 --> 00:19:05,180 excited to come hear your talk, but if I could kind of go out a little bit at this point and just ask, 178 00:19:05,180 --> 00:19:11,820 what's your favorite thing about SpringOne Platform in general? Um, no pressure. 179 00:19:13,900 --> 00:19:19,580 No, I know. I, I really like going to SpringOne Platform. I think I've been going there since 180 00:19:19,580 --> 00:19:23,980 I've been on the Spring Team. I think I even went the year before I actually joined the Spring Team 181 00:19:24,460 --> 00:19:29,660 because, uh, I was working on Cloud Foundry and since it's SpringOne Platform now with 182 00:19:29,660 --> 00:19:33,820 a lot of the Cloud Foundry talks and things like that, it made sense. 183 00:19:34,860 --> 00:19:42,380 So I think what I really like is the fact that it's the one time in the year that the entire 184 00:19:42,380 --> 00:19:51,660 Spring Team is in one place at the same time. And it's really nice meeting everybody from the team 185 00:19:51,660 --> 00:19:58,060 and everybody from the community who's out there to learn about Spring. Um, I think it's a really 186 00:19:58,060 --> 00:20:03,580 great place where everybody can meet and just talk about all things Spring, learn about Spring. And it's 187 00:20:03,580 --> 00:20:09,660 not just a one way street, right? Where, uh, people from the community can ask us questions. It's also 188 00:20:09,660 --> 00:20:15,420 that we get to hear so much from folks from the community that there's actually a lot of issues 189 00:20:15,420 --> 00:20:21,660 that we worked on that stemmed from some, somebody's suggestion or idea that we heard at SpringOne 190 00:20:21,660 --> 00:20:26,620 Platform. So just those interactions and meetings make it quite special. 191 00:20:26,620 --> 00:20:32,460 Along those lines, wasn't Spring Boot something that actually came out of discussions at a particular 192 00:20:32,460 --> 00:20:35,660 SpringOne 2GX back in the day? Or am I remembering that wrong? 193 00:20:35,660 --> 00:20:41,580 No, I think you're right. I think the issue, um, I don't know the issue number, but it has 194 00:20:41,580 --> 00:20:49,500 the reference from SpringOne Platform and how it led to Spring Boot. And so it's actually an issue in 195 00:20:49,500 --> 00:20:53,580 Spring Framework, I guess, but it did lead to Spring Boot, yeah. 196 00:20:53,580 --> 00:20:57,740 Nice. It, I mean, it's, it's a very dynamic, um, cooperative, right? 197 00:20:57,740 --> 00:20:58,380 Absolutely. 198 00:20:58,380 --> 00:21:03,980 Well, and, and again, I think you, you kind of covered my last question or the one of the 199 00:21:03,980 --> 00:21:08,460 questions I wanted to kind of wrap up with, uh, but I'll, I'll just to see if you have anything more 200 00:21:08,460 --> 00:21:13,260 to add. Uh, why would someone consider coming to SpringOne Platform? Why should they attend? And 201 00:21:13,260 --> 00:21:17,740 you've already talked about the chance to, uh, get access with, uh, to the Spring Team and maybe, 202 00:21:17,740 --> 00:21:22,140 uh, run into some folks that might be kind of difficult to cross paths with on a daily basis 203 00:21:22,140 --> 00:21:28,700 if you're located in, uh, Miami or Boston or, or Detroit or wherever. But, uh, anything more you 204 00:21:28,700 --> 00:21:30,540 want to add before we kind of wrap up here? 205 00:21:31,500 --> 00:21:37,820 No, you said it, it's spot on. I mean, just getting to meet people that work on the Spring Team. Um, 206 00:21:37,820 --> 00:21:43,180 if you have anything you'd like to share with the Spring Team, it's a great, um, 207 00:21:43,180 --> 00:21:52,220 medium to do that. And the, the talks are pretty relevant to what, what's the latest and greatest 208 00:21:52,220 --> 00:21:59,740 going on in Spring and in the Cloud Foundry world. So I think overall, it's a, it's a great conference 209 00:21:59,740 --> 00:22:05,500 to attend. Wonderful. Well, I'm in closing then, if I could just ask, what would be the best way to 210 00:22:05,500 --> 00:22:10,060 reach out to you? You have a Twitter account, right? I know you do because I follow you, but, uh, uh, 211 00:22:10,060 --> 00:22:14,860 where can people follow you and keep up with, uh, what your latest, uh, thoughts are and announcements 212 00:22:14,860 --> 00:22:22,300 are? Um, so yeah, I think Twitter is the best place. I am, um, on Twitter. It's my, it's Madhura 213 00:22:22,300 --> 00:22:31,580 Bhave 23 is my GitHub is my Twitter handle and I am on GitHub as well. So if anybody has any bug reports 214 00:22:31,580 --> 00:22:37,740 or enhancements requests for Spring Boot, GitHub is the place to, I guess, raise an issue. The one thing 215 00:22:37,740 --> 00:22:44,620 I did want to mention, since we are talking about SpringOne platform is I would really like to meet 216 00:22:44,620 --> 00:22:51,900 the women who use Spring and who are attending SpringOne platform. And so if someone's out there 217 00:22:51,900 --> 00:22:57,900 who wants to meet me, I would really love to. So feel free to reach out to me on Twitter and we can 218 00:22:57,900 --> 00:23:02,700 definitely catch up at the conference. Absolutely. That sounds great. Well, 219 00:23:02,700 --> 00:23:06,940 thank you very much for your time. Uh, don't want to keep you away from the code too long, 220 00:23:06,940 --> 00:23:11,820 but, uh, really appreciate you pausing and just chatting with us today and see you and everyone 221 00:23:11,820 --> 00:23:16,780 else at SpringOne platform in Austin, Texas. Thanks Mark. Thank you very much, Madhura. 222 00:23:17,660 --> 00:23:22,700 Well, I hope you enjoyed that interview. I sure did. Hey, and as a bonus for listening this far, 223 00:23:22,700 --> 00:23:28,220 if you want to register for SpringOne platform, the wonderful conference we have coming up October 224 00:23:28,220 --> 00:23:33,420 7th to 10th in my hometown, Austin, Texas, when you go to springoneplatform.io to register, 225 00:23:33,420 --> 00:23:44,060 you can use the code S1P200_mheckler. That's M-H-E-C-K-L-E-R. That's Mark's last name. 226 00:23:44,060 --> 00:23:49,500 You can find the discount code if you go to pivotal.io/podcast as well, and that'll get 227 00:23:49,500 --> 00:23:57,100 you $200 off the registration fee, price, winning admission, however you want to think about it. 228 00:23:57,100 --> 00:24:01,100 Well, uh, we've got several of these coming out. So if you enjoyed this one, you should check out 229 00:24:01,100 --> 00:24:05,980 the other ones and, uh, otherwise tune into the regular Pivotal Conversations each week or so, 230 00:24:05,980 --> 00:24:07,820 and we'll see you next time. Bye-bye.