Are you still typing because I can literally hate you? Maybe. I'm done, don't worry. You're useless.
But also, I love you. This is the weirdest introduction to a DBL ever. Hello there everyone and welcome, of course, to DBL the Rekate Podcast that is all about data and beer. I, as always, am the effusive, the effervescent, the somewhat, the little bit slightly majorly too over enthusiastic Chris.
What is effusive, me? If effusive is like, give off, right? It's like, phew. Right, okay.
And I am the effervescent, Chris. I did say effervescent. You could be the effervescent, Chris. Ever-nessence, Chris.
Can you see into my beer? Sorry. No, that was terrible. You need to tell at least a second why.
I didn't want to screw it up. To be fair, I grew up with effervescent, and I loved that song, so they don't want me butchering it on the podcast. Oh dear. Hello there everyone and welcome to Rekate DBL, of course.
Once again, Chris and Chris, back again. It's your renegade. I don't know, wherever we are. But we are, of course, here we can.
Can you really describe us as renegade? Back again with your renegade masters. Yeah, even so, I don't think we could be described as renegades in any sense. Was that a burp or a hiccup?
I don't think that was a mic problem. Oh. That's just striking my beard. Maybe it's my beard, I think.
Fair enough. Well, thank you everyone for joining us for what is this? DBL 20 goodness knows whatever. Yeah, 26 probably.
It's today you've joined us on nothing's day, the 613th of March 2020. And we are proud to be talking to you all about feedback. Oh, I can feel the warmth. The fuzziness.
Oh, give me a hug. Oh wait, you can't. You're in your house. Anyway, today we're going to be talking all about feedback, both the importance of feedback in a personal sense, but also in a technological sense.
Oh, why have you got your wires crossed? Yeah, I thought you might like music. You want to talk about how to reduce feedback in all the audio in audio. Yeah, you've done too much research.
Yeah, this is all bad now. Okay. You're going to be banging your desk. You're going to death and all of the listeners, all both of them.
But of course today we're going to be talking about feedback and my feedback is important. Now, before we do, of course, with feedback being our favorite, we thought we'd bring you an extra special beer this week. So Chris and I have both been tasked with going off and finding one of our favorite beers to have for DBL because the brief, the brief when we came up with it was our favorite beer. And now you change it to one of our favorite beers.
Could someone could someone not decide? So I struggled to decide. I have several favorite beers. And yeah, I struggled.
So I've gone with one of my top 20 favorite beers. Probably at least top 50. Well, the problem is I like my top 20 so much. There's so little in it that plus my favorite beer is actually brewed by the Ivo brewery in submission in Cambridge in the UK.
And unfortunately, they aren't reopening their online shop because they're a small batch brewery. They aren't opening their online shop again until probably a week and a bit of time. So I've got myself something else. Never mind.
What have you got, Chris? What are you doing? Hey, what have I got to start? What have you got?
Oh, right. Fine. If you want me to go first. I've got toast.
Yeah. Hey, for all of you listening, it genuinely is a beer called toast. It doesn't taste like really, really good pale ale. It's so it's they do a couple of different brews.
And this is a 5% pale ale. So it's a golden zesty and planet saving. So effectively, the premise of toast is that they brew it with surplus fresh bread. So where there's fresh bread going surplus, otherwise be just food waste, they actually use that to brew the beer.
So instead of instead of adding additional kind of supply chain to to climate change and having a negative impact on the world, they just brew the in their words we brew our planet saving beer with surplus fresh bread, all our profits profits go to charities fixing the food system. Wow. That's cool. Very clever.
Something that is essentially just grilled bread. Basically, and something that is 5% volume, which is pretty cool. But yeah, so I'm a big fan of some of the big fan of their mission. I think that they've got a fantastic ethos about them.
And if you're in the UK, definitely drink more of toast. Or of course, if you're abroad, I say abroad, I mean, you know, in your country, then you might also have similar beers available. So definitely check it out because I can highly recommend it and it is delicious. I learned something new today.
Hmm. So what have you got? I've got something that I'm pretty sure I've read before on this. I've definitely tried it before today.
That would be very weird. Sure. What you got. So this is the West mother.
Oh, the best mother trappas double. Yes, I am a big fan of Belgian beers on a big fan of trappas beers. So yeah, this one. This was pretty good.
So the interesting thing, I think the double the one that you're about to drink. Also, when we first broke 5000 listeners for DBA, I think was in the box. Oh, really? So I think you're just subconsciously somewhere you're identifying that and going to a good strong DBA or beer.
Yeah, I always have like at least one of these in my fridge. This and Guinness and statues was the what I was deciding between those. Very west century. Fantastic.
Oh, well. So for everyone out there who doesn't know about the best mother trappas, how would you describe it? It's Belgian trappas beer. So it's like, yeah, I like trappas beers.
I like Belgian beers. The two of them combined. Very good. One fun fact that people don't often know is that not all trappas beers are Belgian.
Most people assume that trappas means Belgium. No, Belgium doesn't mean trappas, doesn't mean Belgium. There is an English trappas brewery. There is a couple of Dutch ones.
The thing has a French one. I don't know where the others are. But yeah, it's very sweet. It's very strong.
It's just very nice in general. Oh, very nice. Well, I think we're both good to go. So let's get these.
Let's get these open. I'll let you go first as you've got a you've got an actual bottle open. There he goes. Wait for the quick.
Very nice. Yeah, I heard that and I'm going to go for the can open. Nice. Paul, the lever.
Crunk. I do. I've also got a chalice to drink some as you should always do when you have a Belgian beer. That may sound very, very, very, very, very, very.
My beer snob. Yes. I only have one chalice and it's for my Belgian beers. Gosh, I love this beer.
Love me a bit of toast. What's your favourite toast topping? Everyone out there. Tweet me at one basically.
Tell me about your toast. I'm going to just plain old spread. Really? You're not doing fancy.
Yeah. I'm going to one up here and I'm going to say that there is a there's actually a spread that I really like from Romania called Zekulska. They also have it in a few Eastern European countries under different names. I think in in Bulgaria, it's a new tinitsa and it's this beautiful spread of like roasted aubergines and all peppers and all mushrooms and various different vegetables and it's beautiful on toast.
When you're when you're finding out to come around my house again, great. I'll get you on the Zekulska. Just nothing but slice of bread after slice of bread. Nice.
Right. So, this hummus count. Oh, gosh, I love hummus. Oh my goodness.
Yes. That's the most middle-class thing on earth. I love hummus. You know, I'm afraid I like one hummus.
Right. We've got a beer, Chris. That's the important bit. Now we're on to the less important bit and that of course is feedback.
No, no, I'm joking. It is quite important. So obviously, let's let's start with one of the two aspects here. So we're going to talk about personal feedback and we've got to talk about like technological feedback.
So let's talk about personal feedback first because we won't spend too much time on it. But what would you why would you say feedback is so important from a personal perspective. So feedback is really essential for growth. Right.
How do you know if you're growing or developing or progressing in a way that's positive if you don't have feedback. I like to consider myself as someone who is pretty self-aware, but even even even me who is the king of self awareness, the most modestness, this is a way that other people's perceptions may be a little bit different from my own. And it's not their fault. Although I may think it is all their fault.
A lot of the time it's because I've maybe not thought things through. It's very typical or I presented things in a way that not all people agree with. And, you know, we all cover different walks of life. So something you might think is very reasonable.
Others might disagree with. For example, Chris has given up showering for the last six months. It's really noticeable because of lockdown. I've not had to tolerate it anymore, but I don't have to give him that feedback because we have no longer in the same way.
This is true. Of course feedback I would probably still receive within my household. Were it true, of course, were it true. But there's a few distinct forms of feedback here that are important.
I would say it breaks up into three main categories. And if we're talking about professional feedback and I'm not just talking, there will be times where friends do things, or where you do things and friends perceive it where you have to give like really personal feedback because of friends family, etc. But from a more professional context, there are three main situations where you're likely to be, you know, thinking about feedback. The first of those is receiving feedback.
The second of those is giving feedback. And of course, the third is actually feeding back to yourself, which is often overlooked. So, I'll clarify the third one there because I don't just mean going good job me. Thank you me.
I mean, you do quite enough of that. I do a lot of valuable feedback by the way. Super valuable. I will take that on board.
I will take that on board. I do too much. I will improve. But no, the giving feedback is important, like you say, because it's important to grow and to understand, you know, the giving and receiving a feedback is a path to to growing as an individual and as key, really making sure that you always think about the feedback you're giving or getting if you're giving feedback, making sure that it's if it's critical, then it's constructive because there's no point me just saying to Chris, hey, I think your beard looks greasy.
If, you know, I'm not going to actually suggest a way to improve on that situation. It doesn't, by the way, it looks magical. Hello. And if I'm getting feedback as well.
And this is one of the guiding lights of my life. This is one of the things that's helped me kind of improve over time. You should say, me years ago, my gosh, no one could have helped in. But the receiving of feedback is a blessing.
And, you know, we've even been in the position. I think I can say, Chris, I won't mention names or situations, but there's been a situation where you've had, I wouldn't say negative but constructive feedback for me, and you've then had to give that to me. And actually, I would say that that was some people might feel defensive about receiving that kind of critical feedback. Actually, that's a perfect opportunity for you to, to revisit and enter into that third stage, which is self feedback.
And being like you say, the king of self awareness, if you are self aware, self awareness doesn't mean just knowing where you are and what you're doing in any given context. Self awareness is about metrics and about monitoring and about checking in with yourself. And, you know, actually being completely honest and vulnerable with yourself and saying, could I have done better there. How can I improve?
How can I take this feedback I've been given and actually incorporate that into my own being. But the problem is, like you said, you have to come with a growth mindset, but if you're closed off to feedback, you can't improve. You are fixed at a point in time and. Well, that's about it.
I think to me it's personally something I find very important is always, always be learning, always be looking to find things you can learn. The reasons that I've left previous roles were because I felt like there wasn't an avenue for me to learn. I got to the point where I basically hit my ceiling. And I could either stay there and sit on my laurels or I could move on and look to learn something new.
It doesn't have to be like further expanding yourself outwards as a person. But I think constant progression is a big part of part of who I am and constantly thinking about what I can take away and what I can learn from this. And so yeah, I definitely get on board with the growth mindset piece, but it's not easy. Like, it's something that you do have to check in with yourself and you do have to, I think, make a conscious effort to kind of keep in that medical zone.
And then there's lots of tells I think you can find very, very easily like the way you are in terms of whether you're open and accepting and in that growth mindset area or whether you are not quite there. And things like if someone if someone does really well in the office in the office, in the office, of course, if someone say lands a big deal or if someone produces a great good content or if someone finishes a big project and they get a lot of praise and recognizing how that makes you feel. Does it make you feel happy on their behalf. Does it make you instead a little bit jealous.
Just obviously feedback. How does that make you feel does that make you feel defensive, or does it make you feel like you want to try and understand what that is. And these things are not black and white like I'm painting in quite black and white picture but there's always mixed emotions when these things happen like I'm always I'm always looking at like my metrics and I'm always trying to beat everyone and I think competitiveness is a good. And we do think to have in.
Yeah, we're not putting other people down right as long as you're not trying to actively sabotage others or healthy competition is a good way to to draw out high performance and it's a really good way of building comradery with one another. But at the point that competition becomes almost putting each other down for the sake of your own merit. And that's where it crosses from feedback into bullying more so than anything. We could probably talk about this for hours and hours and we both I know with both huge huge fans of self awareness mental resilience checking in with ourselves key metrics.
That's what you're not very mentally resilient though. It's true I fall over with a slight gust of wind but I overheard a video that I'm not sure I'd believe him relentlessly all the way back. Exactly. But I was I was I was I overheard a video that Andrea was listening to the other day and it made a really nice point that I've incorporated into my own sense of being.
And I think it's a really good point to which to end the personal feedback section so let me know if you think that's true. But, whenever someone uses the phrase the phrase fail obviously we know to you know if you've never failed you've never tried anything new blah blah blah. But what I overheard was fail to fail stands for first attempt in learning. Nice.
And I was like, ah, that's really cool. And failure in some senses is feedback of its own it's the opportunity to learn the opportunity to grow the opportunity to be a better you and I think that's a really important thing to bear in mind. You just completed the first iteration. Exactly.
It just happens that the first iteration didn't deploy properly but anyway. So I was on to talk about I guess delivering on feedback I think that's really important to be receptive to feedback and looking for feedback as well like how can you find ways to look with feedback it's something that we continue to do. And that we continuously try and put systems in place in our kind of workplace to incorporate and mix success for sure. But you know, sometimes you get right, sometimes you get it wrong, take the feedback and improve the feedback process.
Wait, this is going very matter. But yeah, delivering feedback very important. Yes, absolutely. And knowing how to deliver constructive feedback as well.
And working with people to actually improve the way you give feedback as well to get feedback on your feedback wait no that's that's too bad. Never mind. Let's let's move on so I think the next part of this and I think we can probably do a whole, a whole episode of DBL on kind of mental resilience self awareness methods for checking in with oneself that sort of thing. If you're listening and you would actually find that interesting.
Let us know tweet me at plant basically tag tag in at Kurzweil Chris. Let us know if you'd be interested in hearing a bit more content like that and we'd be more happy to put it together. Yeah, for sure. So, on to the next thing then let's talk about the importance of feedback as part of DevOps obviously this is.
Oh, I can't wait to move on. I guess one more thing that I really want to say but delivering a feedback so the delivery of feedback has always, you know, if someone's receptive then it shouldn't matter as much but delivery feedback still really matters I think and the top tip for anyone who hasn't gone through training on this or hasn't learned about this before is always even better if so there's something you did well and genuinely did well this would be even better if is like the number one hack for delivering feedback well. Yeah, it just softens the, softens the blow I guess is making the wrong way of phrasing but it is incredibly powerful and I find this in the professional world. I find this in the in your personal life as well but you know it just makes the other person know that you're not there to just rip into them.
Yeah, yeah a compliment sandwich. Well, that's that's actually an interesting one you raised but there's actually a theory that a compliment sandwich is bad because I disagree. Yeah, compliment sandwich will have the opposite effect of what you intend, it will make them the other person think that the negative or destructive piece is something that can be forgotten or dismissed a lot more easily. Whereas if you end on the constructive piece is something that will they'll take away.
Yeah, exactly it's it's like they say you know people always remember the first thing and the last thing I'm exactly the same with Eurovision is you know, as you go through as you go through. You're a vision to every conversation. You could put your vision in anything. I mean you get the you get the odd kind of act here and there that really stands out like like daddy flair who did think about things or you've got 2020 Eurovision specifically here or you've got little big who did one of my absolute favorite songs.
So this is a great example I guess sorry to interrupt but if you think about britains entry to Eurovision that have Katie Price. I don't remember. For example, I think that the song she chose was a really good song I think it would have been even better if she wasn't watching it. That's good feedback.
Obviously thing that you can do to improve Britain's Eurovision entries is definitely needed at this point like how many years in a row have become bottom of voting. Yeah, that's fair. I mean, I don't think we've been bottom for the last few years if I'm honest like there's been a couple of blips where we have but I don't know I nominate Chris Kurzwell for next year vision 2021. The world isn't ready yet for my interpretive heavy metal Mongolian throat singing but that's okay well we'll send everyone can send a message to Alex Yates and ask him to whip his guitar out again.
Some fantastic songs on that guitar. I do. Indeed. So let's move on then and talk about feedback as part of DevOps and we could talk about this all day long there's so many important aspects when it comes to feedback as part of DevOps process.
Zoom the next actually zoom the scope right in here so we're going to be talking specifically about the database change management process in more general terms shocker shocker shocker. So obviously there's a few key points and the purpose of putting in place good change management practices for the database is so that you can do effectively what Microsoft would coin as shift left. Am I right. I mean the amount of times I've heard you say the phrase shift left shift left shift left shift left I'm always pressing on my keyboard it does nothing but it does nothing.
Well, that's because it should be shift alt left but that's the story for another day. Effectively, the purpose of shifting left is so that you do more testing great validation better quality development on the left hand side, so that by the time you're promoting to production. It should be simple is clicking a button it really should be very straightforward. Unfortunately in practice it doesn't always work like that but there are a number of ways that you can introduce additional feedback loops into a development cycle.
So I think Chris, why don't we take it in turns and go through what we think are the feedback loops on the left on our way up to prompt what do you think. Right, can I start with like the big one then. Yes. And just do the whole cycle being shrunk down in iterative steps.
Right, good, good point absolutely. So like the whole kind of agile methodology being extended to it's kind of logical progression. If you're deploying like as soon as you can whenever you can that means that you can take on feedback and pivot around that feedback instantly right so excellent point. You see that you have a request from a customer or from a market or from whatever it might be incorporate that into the next delivery and deploy that and the quicker that you can do that because you can respond to the feedback and the quicker you can kind of progress.
There's no better way to build software than by listening to the actual customer requirements and building around that right yeah and you know customers I'm using in the very loose of senses so. Yeah, customers may be well I think of them as customers still if you are an operations team through your customers if you are developing software for internal use your customers, we have customers who will talk to. But that doesn't mean that you shouldn't think of them as customers it's just they might not be customers that will give you spend money directly with you. Interesting.
No that's a really good point and actually what I didn't even think of so like the whole cycle in itself as a feedback cycle there's no point doing a big bang release after six months and then getting a huge amount of customer feedback over the following six months and then spending another six months trying to fix it when you could work to a two week cycle deploy a minimum viable product and immediately start getting feedback oh good change that by the time you get to that same kind of 18 month point on an iterative development cycle. You just are so much better off with so many fewer bugs and so many kind of enhanced features and capabilities that you've been able to pivot and naturally just fit into that market where you should exist and with the big bang deployment cycles every six months. You just end up you know you end up not listening to user feedback but you end up delivering what you believe users want and those can be too very mismatch things. And we're lucky with software that this is something that you can most of the time very easily do appreciate if you're building houses this is a lot of like a minimum viable houses.
Yes, basically the house. Yeah. Yeah. Okay, what's your what's your option is number two.
Number two. So number two, I was thinking a good feedback cycle is a database first methodology. Okay, that's not expected. Excellent.
A lot of people make changes to to the code directly a lot of people make changes to SQL files and things. Okay, yeah, that makes a lot of sense. And then they try to apply it to the database and it goes boom. Yeah.
So actually making sure that you have, and this is kind of a double point number one is making sure you have an environment that's indicative of production first. So actually make sure you refresh development testing QA pre prod environments often make sure they're up to date make sure they're representative of production both in terms of schema and data where possible obviously sanitize. And then work on that copy because if you're making your change to what is effectively a very recent copy of production, and it works well, then you can better believe it will probably work if you deploy that same change to production so kind of a double point there. Make your change against a realistic copy and of course make it database first instead of code first, because then you get that immediate feedback of, Hey, it can run it syntactically valid everything's fine.
Don't worry. This is good. Yeah, that makes a lot of sense. A lot of sense.
All right. I'm going to go to number three. Go for it. How many numbers are we getting to?
When until we run out of time and we've got probably about eight more minutes worth of this segment. We find another 88 more minutes. I mean, Chris at the end will be like, I can't think of anything. So I'm going to go for the next, I guess obvious one but there's so many different ones.
But I'm going to go for running a database build. So running builds is a great initial point of feedback for software as a whole, not a typical process when it comes to databases. But literally, it makes so much sense, especially if you're running a change script or migration script method of versioning and deploying database changes. So let's say that we have like five migration scripts that I've written and I check on the source control.
I next should have some system in place that's going to give me feedback as to whether the scripts I've written are hot loaded garbage, hot tip if I write them they are, or not. And the build does that in a very nice and neat and fundamental way. So spin up a copy of a database. Ideally, you could do a blank database and rebuild from scratch or the whole clone is baseline thing that we came out with a few months ago is really cool.
So you're basically testing those scripts at the fundamental level. Do the scripts actually execute. And if they don't execute, then you got a problem, because then you know what's the point of running deployment on scripts that don't execute right so you've got instantaneous feedback. Take that, pick the scripts, correct them up.
Oh look now the build runs. And then when you take those scripts you run as somewhere else you know they're going to run. That's true. That's true.
You might have coded something absolutely diabolically awful but you know they're going to run. I'm going to jump back a second because I think you're already at continuous integration and I think that you've missed three key steps for feedback. That's how much feedback I think is in this present I think you've missed three points of feedback there three. Yes, so there's a brief coverage of those three.
The first one. Static code analysis. Yeah, yeah. It's a small point, but it's a point nonetheless applying best practices to the code you are writing against the database as much as anything is a really good way of catching out.
Oh, someone put an asterisk in their select or someone's declared several parameters and only used most of them or xyz and you know, press press or procedure that was just select star. That's all it was. No problem. That's it.
Select what deferred name resolution isn't going to help me here it's just rubbish. Select everything. Could you imagine select star from star and just leave it there. I'm pretty sure you can probably do that that's probably valid.
Some sequel server I just don't even know I've never even tried it. But yeah, so that one and then the second one is source control so actually sharing work with your colleagues working in a dedicated model where everyone has their own sandbox environments means that people working on the same branch start to diverge quite quickly. Making sure that you are consistently committing pushing pulling applying to your database and making sure that you and the rest of your team are constantly saying up to date with one another is an excellent way for you to review, give feedback and validate not only the work that you are doing but the others within your team. And that allows you to rapidly pivot and improve on any functionality your team is working on.
Makes a lot of sense. And the third point that I think was missing poll requests. Yeah, I knew all of those three were coming. See, my feedback for you is that I think you did really well in highlighting those three but I wasn't thinking that this linearly.
That's fair. I just don't process something of importance process shouldn't restrain you Chris we shouldn't be restrained by the process. It should be naturally flexible enough to work around whatever you need from your pipeline. But that being said, I am working quite linearly here.
That's what helps me think so. For sure feedback. Thank you. The interesting part about pull requests, so pull requests probably my favorite part of this whole process.
I'm not sure what the reason is because I've seen recently a number of our customers, red gate customers get up and running with pull request workflows in as your devops leveraging SQL change automation and SQL clone and they're able to spin up copies of the database on demand to then deploy build and deploy changes to from that branch to a live environment so that they no longer have to review just code in as your devops or pull it down apply it to their own database and then have to kind of reverse engineer that. I think that's a really good concept of a really good concept that allows developers to get instant almost instantaneous feedback. So I think that's a really good way of doing it once you know once all of those steps have passed and we could we could also make this red gate specific and say the validate in in SSMS or visual studio for change automation builds the database before you're even in source control. But we're not going to do that.
But the pull request is an excellent way of validating those changes and then ensuring that they are properly merged back into our main our trunk are whatever it is however we're working. And then we're going to see I and as part of the time we've got the build and an optional thing that we quite often talk about is unit testing. Again, another great source of feedback so you run a selection of tightly defined tests that validate the store procedures the functions. Mainly store procedures if I'm honest that you read and by simply executing them in a dummy environment.
And these are things that you don't have to do a build you can do. But it works really nicely built it's kind of just a neat way to give you extra validation on code you've written. It's interesting it's like when we talked about testing far earlier on in DBL like four or five or something crazy. I think we also paid homage to a test driven development.
But the point is you don't just build you don't. I'll call it you porridge you don't just you don't just pay porridge you don't run a test once in your development environment and then leave it. It's actually included in source control and actually then can be automated as part of the pipeline and filtered out where necessary so it's a really good point. And what's the additional feedback loops as well I think then that brings us on to the natural.
The natural kind of final step from a continuous integration build as well which is continuous delivery like continuous deployment is definitely a thing but I wouldn't necessarily say that that in particular is the feedback loop. I would say that the feedback loop is the continuous delivery where you don't get in the middle the build is published you end up with the artifact and then you release it to an integration or a test environment where you prove that not only can your database be built from scratch. But you can also deploy those changes to later stage environments so not only does not only can we do 100% but we can do the delta. And that leads us on to like the things that I guess we weren't going to but the actual testing you do in testing violence right so.
Functional testing and performance testing and load testing and all of this weird and wonderful stuff that we don't know anyway near as much about as a lot of you guys probably do. Yeah exactly and if anyone out there is a massive tester let us know we'd love to have you on asking questions have a beer talk about testing and get your insight. Yeah cool. So fabulous so yet we continuously deliver and we know that our quality of our deployments are good and we've already signed it off in dev we've signed it off against the pull request we've signed it off by building it by testing it by packaging it by deploying it we've done everything we need we then just go ahead and go deploy deploy deploy deploy or in some people's cases deploy all the way up to production and we are good to go we can deliver fast and get fast feedback.
Bish bash bash bash and that pretty much takes us to the end of the feedback section and we've kind of we've talked a lot about feedback there and I feel like we could continue talking about feedback but I think we're probably going to have to call it for the sake of time. And a lot of feedback we probably get is not talking about feedback it's really really really that would be useful feedback and I'd love to talk about that feedback should anyone wish to offer said feedback. So I think that it was really good that you asked for feedback there but personally I think that you are having the point a bit too much. And so your request for feedback on the dbl episode about feedback I think it'd be improved.
I agree and that's something I will work on as part of my growth mindset. Ding. Any feedback about how I deliver that. No I think that'd be too much.
Speaking of feedback I think there's something that is worth while bringing up as part of our section we haven't sung the intro for a while so I'm just going to go ahead and introduce it hang on. We got very different times that we got very different times that yeah we did I was I was not expecting a little beatbox in the background background beatbox. It wasn't that loud. The yeah so one thing that we should bring up as part of the news and something that's very important that red gate runs every year is of course Chris.
And the state of database DevOps report. The state of DevOps report. Yeah so a couple years ago we actually got what was it 1000 respondents something like that. And then last year we got 2000 respondents.
Or just over now if for anyone who doesn't know every year. You've got people like Dora and puppet who run the state of DevOps report and that tells us all about the DevOps things people are doing. Oh hey I really like containers I've got Kubernetes out the wazoo you know these sorts of fancy DevOps things. Now a crucial aspect of that is how people are treating the database as part of their pipelines now.
Interestingly every year red gate runs the state of database DevOps survey as kind of a report a tandem to what Dora and puppy runs so giving it that that crucial insight into practices in the the wider kind of database development ecosystem. So guess what we run it again. Yes well aren't we all. But no the state of database DevOps report 2021 is available and Chris why should these lovely people who are listening to us go and fill it out if they work with databases any databases.
Well because it gives us good feedback. Yeah. How how how serendipitous. How are you working with Oracle 9i are you still working with SQL Server 2012 or are you currently using as your sign up so you're using snowflake and what are you using for your data warehousing for your database development.
Do you fundamentally have your databases under source control all these sorts of crazy weird and wacky things we care about what you have to offer and the world's biggest database DevOps survey needs you will need your feedback. Absolutely it's always got great information that comes out of it and it's really really interesting. So it's kind of who knows. It's definitely the most exciting.
It is the most exciting absolutely. And Chris where where can people go to to fill out the survey where can they go to get their voice heard. I don't know. I got to do everything around here.
If you want to get your voice heard and be part of that feedback and you want the opportunity to I believe when I think there's there's a winning incentive as well you can win a massive super fantastic gift card or something even better than that. You can go to red hyphen gate.com forward slash dev ops survey red gate.com forward slash dev ops server that's dev ops server that's dev ops survey as you are the why get your voice heard find out about everything that the community is doing and also being with a chance to win. I was just Google it. Yeah, red gate state of database dev ops survey or red gate.com forward slash dev ops survey or tweet question asking or tweet me and ask me and I will share you a link that's absolutely fine as well at plant based sequel.
Oh, we don't get to do data breaches. Well, okay, we can do a data breach. So there's a little data breach that comes from a vendor that sells a lot to a lot of hotel booking sites. So it's prestige booking.
So they have an unsecured S3 bucket that apparently in a month's worth of data was found to have around about 18,000 records. And by looking at back of the logs, this data has been open for access for a significant amount of time to the point where people reckon that this data has been on secured for around about 10 million rows worth of data. Wow. Oh, so actually it was just 18,000 recently because I heard it was, I heard it was millions and millions in that unsecured S3 bucket.
But what, what kind of information did that, did that include Chris. So that is a lot of payment information specifically. So not only are we hitting kind of personally, but the information where relevant, but a little bit more. I guess established is probably the right way, but PCI compliance is going to be all over this, a lot of credit card numbers, et cetera, including this.
So if you've booked on basically any hotel booking site within the last like few years, then, whoa, let's get to them passwords and your national ID numbers and credit card numbers. Oh, anyway, if you want to check that out it's prestige software, right? Yes. Yeah, so definitely worth a check out.
Cool. So we've only got one final thing to talk about besides the data breach there. So we've got two, two kind of fun bits of news there. So we've got, well, I say fun, but one fun thing is the state of database DevOps survey and also the classic data breach monthly.
Chris, really just how exciting he gets about data breaches right there. It's not about getting excited. It's just, it's nice for her to have something to talk about. Also, also, also, we have a competition.
Oh, so, so Chris, did you want to introduce it? Yeah, so we'd like to, I guess, get feedback from the guys. So if you have the time, the inclination, if there's anything you'd like us to cover, if there's something you'd like to hear us talk about, then please let us know. We also love to hear, I guess, what your favorite holiday drink is as well.
Exactly. So basically, this is a competition that we're running here at DBL and effectively, you could win a, you could win a crate of a beer of your choosing up to a certain value will have to double check terms and conditions apply. So, effectively, if you want to be in with a chance to win a crate of beer, then let us know, send us an email, dbl at red-gate.com. Tell us your name, obviously.
Tell us what your favorite beer is what is well, not even what your favorite beer is what is your favorite holiday table. Maybe you don't even drink beer. I don't know if you prefer wine. Maybe you prefer non alcoholic, maybe for non alcoholic beverages.
Doesn't matter if you like cherry aid, let us know. If you'd like to see us talk about in 2021, give us any feedback, things you like, things you don't like, we'll be more than happy to take that on board and it's just dbl at red-gate.com. With the subject line, we haven't decided on this, what should be the subject line, Chris. Cats.
Everything myself, everything. With the subject, dbl, dbl December competition. I mean, do you say this like we get inundated with emails and it'll be hard picking through. Well, just send it with a subject line so that we know that you're sending us an email with your feedback for dbl 2021.
If you want to go with dbl December DEC competition, that's fine as well. It'll be easy to pick out. Sorry, I'm BH. Compefficient.
No, in DBL. Oh, dear. And yeah, let us know your feedback. Let us know what you would like to see us drink, what you would like to see us talk about, what your favorite table is, we'll put your names all in a hat.
And then at the in dbl, I guess, dbl January. Yeah. Yeah. Yeah.
We will announce the winner and. Right until the end of the year. Right until the end of the year and then you will win a prize. Please.
Congratulations in advance Robert French. Oh, dear. And anyway, that's brought us pretty much to the end of today's dbl then. So I think it's about time to say thank you to all the listeners and of course, but anyone who's listened up to this point.
Thank you so much for supporting dbl. We're very close to 10,000 listens now. So goodness knows how you're all getting by listening to us. But here's a bit of feedback from us to you.
We really appreciate you listening and we love doing dbl and we've got topics like I say, for days. So if you want to keep listening to us, please do please let us know if you like the show. It's always really great to hear any feedback. Thank you.
So for now, Chris. I guess that's it. It is. Cheers.
Cheers.