DiscoverModernize or Die ® Podcast - Conference Edition
Modernize or Die ® Podcast - Conference Edition
Claim Ownership

Modernize or Die ® Podcast - Conference Edition

Author: Ortus Solutions

Subscribed: 1Played: 17


CFML has some great Conferences - so we want to get the vital information out to you, so you can make the most of them.
Your Host will interview Conference Organizers, Workshop Trainers, and Speakers, to get you all the information you need to decide which conferences to attend, what workshops to dive into, and what sessions to attend when you're enjoying the CFML Community at our great conferences.
9 Episodes
For more episodes - view the website -★ Support this podcast on Patreon ★
Gavin talks with Luis Majano, CEO of Ortus Solutions and Founder of Into the Box Conference. They discuss the history of Into the Box ( ITB ) and this years ITB in Houston Texas, May 2020. Find out what makes Into the Box special, why you should attend, and some details on the workshops and the speakers presenting at the conference.For the show notes - visit the website from this podcast used under Royalty Free license from SoundDotCom and BlueTreeAudio★ Support this podcast on Patreon ★
Watch the video version you YouTube: talks with Eric Peterson, Software Consultant for Ortus Solutions Trainer leading the Intro to Quick ORM Workshop at Into the Box 2020 in Houston Texas, May 2020. Find out what the workshop is about, why you should attend, what you need to know before you attend and what you'll learn while you're there. You can support us on Patreon here the show notes - visit the website from this podcast used under Royalty Free license from SoundDotCom and BlueTreeAudio★ Support this podcast on Patreon ★
Watch the video version you YouTube: talks with Gavin Pickin, Software Consultant for Ortus Solutions and Trainer leading the ColdBox Zero to Hero Workshop at Into the Box 2020 in Houston Texas, May 2020. Find out what the workshop is about, why you should attend, what you need to know before you attend and what you'll learn while you're there. You can support us on Patreon here the show notes - visit the website from this podcast used under Royalty Free license from SoundDotCom and BlueTreeAudio https://bluetreeaudio.comTranscript:Coming soon★ Support this podcast on Patreon ★
Watch the video version you YouTube: Pickin interviews Brad Wood, Software Consultant for Ortus Solutions and Trainer leading the Intro to BDD Workshop at Into the Box 2020 in Houston Texas, May 2020. Find out what the workshop is about, why you should attend, what you need to know before you attend and what you'll learn while you're there. You can support us on Patreon here the show notes - visit the website from this podcast used under Royalty Free license from SoundDotCom and BlueTreeAudio https://bluetreeaudio.comTranscript: Intro (00:02):Gavin (00:31):Welcome to the Modernize or Die® podcast conference edition. And today we're meeting with Brad Wood, an Ortus Solutions Consultant and trainer for his workshop at Into the Box 2020, Intro to BDD. Welcome. Brad.Brad (00:44):Are you meeting with me or am I meeting with you?Gavin (00:46):I'm the little guy today, so it means you're the important person.Brad (00:50):Okay. Careful. I might get a big head.Gavin (00:52):Yup. Yeah. Well me, I'm not usually the little person, so that's kind of cool for change. Anyway. So, we're going to be talking to you about your workshop, Intro to BDD. So what's the workshop about Brad?Brad (01:06):It's about intro to BDD. Gavin, can't you read? So what is BDD? That's a good question. BDD stands for behavior driven development. It's sort of an evolution of TDD test driven development. It doesn't quite replace it. It kind of builds on top of it. Honestly we'll kind of start out with the workshop just talking about, testing and why it's important because, before you get off too much in the weeds about all the different styles of testing or types of testing, for a lot of people, the biggest hurdle for them is just actually begin testing their applications.Luis and I were at a DevNexus conference recently and I sat in a part of a workshop that he had on, on TDD for Java developers. the speaker Vencat had like, you know, three rules of testing and I forget what the third one was, but the first, the second rule was just do it and just do it.Brad (02:01):Cause that's kind of the problem. Um, you know, with people's getting over that hump. And one of the quotes that came out on Twitter that, that Vencat had said in that workshop was something along the lines of, um, I don't test because I have a bunch of free time. I write tests because I don't have a bunch of free time. You know, in the time savings that you have. Ultimately when you have a nice test suite that goes along with an application and it's always hard for people to kind of see that future version of themselves where they have a, you know, a nice, suite of tests that, you know, cover a lot of the functionality of the app and all they see is kind of the immediate, you know, version which is, well I would have to take longer to write tests.Brad (02:45):Um, and so, you know, with, with TDD, with test driven development, the idea is you don't write your application and when you go back and just write some tests to verify what you did, you are kind of doing it backwards. You use the test as part of your planning phase, design phase. When you think about, you know, what's the function on building? And it might be a quote unquote, you know, functionality of the site. Maybe not a specific code function. You know, what am I building, how should it behave? What are the externalities, what kind of inputs does it need? What kind of outputs do I get back? Whether that's at a very low level or at a high level, like a page. You think about those things when you're building the test and you come across a lot of, redesigned cause changing of your design costs a lot more the farther, uh, the later in the process that that occurs.Brad (03:31):So you want to find out those kinds of design flaws and those bugs in the design earlier on and writing your test up front. It really helps with that. So, you know, built on top of test TDD, test driven development. Uh, by the way, I, I heard a joke once, which was bug driven development, right? You just wait till you have a bug and you find it and you fix it. That's not an actual type of testing. Please don't do that. BDD behavior driven development kind of builds on top of that, writing your test first. It ties it in with a kind of agile workflows with user stories. You know, as a end user, I would like to have feature A because of this business value it provides. And when you have your scenarios that you tie in with that, you know, given these inputs, then when this action occurs, you know, when this action occurs, then this should be the output.Brad (04:23):And it's kind of a ubiquitous language. Luis loves to use the word ubiquitous when he does the training, that you use that, developers can understand that language from kind of a developing standpoint, but your business owners, the product owners, the business analysts, they also understand that given this, when this happens, then this is the result. So BDD is kind of a natural evolution of coming up with your, your user stories first, your business scenarios first, and then out of those inherently grow your, your unit testing suite or your integration testing suite. Um, so reorganizing your, you know, your development shop to first kind of appreciate the value in the utility of testing and the actual, you know, cost savings that you get in the long run and implement meaning that is oftentimes kind of the first step for people.Brad (05:16):So it's a really long answer to your question of what's BDD is, you know, we're going to talk about a lot, why we test and what it does for us. Um, and so that's where BDD kind of fits into that conversation. Um, because if it's just here's some code that we already have out there, let's throw some test at it. Um, it's sort of like, you know, you're, only getting a fraction of the benefit you've, you've missed out on so much of the process. Um, had you had testing as a kind of a first class citizen of your design phase now and unfortunately for, you know, a lot of people, most people you have existing code bases you're maintaining and you may not have any tests for that code base or maybe you have a couple tests. That's all you ever did. And in those cases, you know, this code is already in production.Brad (06:00):The, you know, the, the ship has sailed on, you know, starting from scratch with, you know, testing and scenarios. So, you know, in those cases you don't have a choice. You have to be able to fashion and tests, um, you know, against an existing code base. Um, but you know, going forward it's nice to have a, a bit better perspective. So that's what I hope that the workshop kind of gives people is, um, just understanding how to fit it into the workflow, why it's important. A lot of times, you know, you had developers that are okay with the idea of testing, but the management, um, doesn't understand the reason. You know, why you want to spend more time, you know, why this is just gonna push your deadline back. We didn't have time for this testing. It's seen as a, as an optional step. Um, and it really can't be seen as an optional step where people will just skip it every time. Um, so, okay.Gavin (06:46):Anyway, I think that answers the why you think this workshop is important too. So, obviously you're talking about the buy in effect you have to do in everything. So, so what do you think you're the right person to lead this workshop thing? Trick question.Brad (07:00):Yeah. It sounds like a dangerous question. Um, well, uh, I I like, uh, testing is really fun. I've, I've given this this workshop and this training quite a few times. Um, and it's always fun to kind of see, you know, the lights, the lights turn on when you cover this kind of stuff with people. Uh, if you've a, this is a lot of what we're going to cover is a pretty standard to our onsite trainings and our virtual trainings that we've provided Ortus when we come in and we talked people through, you know, building applications with cold box, we always have a whole unit on testing the kind of covers. Um, all this right here. Now I mentioned ColdBox. I should add that this, uh, this session is not about cold box. In fact, uh, we may use ColdBox and some examples, but if you're not using ColdBox, don't think the session isn't for you.Brad (07:47):This is really just about, um, you know, test box and the theory behind testing. Um, so some of what we talk about may use some examples and ColdBox, but it's really nothing specific to ColdBox in the training. Um, but anyway, yeah, I guess as far as as why I should be giving it. Um, I suppose there's a handful of people that could give it just as good as I can, but it's something I've, I've taught quite a few times. I've done a lot of work with testing and, uh, I think it's a really fun topic. So, um,Gavin (08:16):Im sure you have written plenty of tests in your lifetime?Brad (08:18):I have probably not as many as I should have. You know, I'll be honest. Yeah. Everyone who says their tests and everything they write is probably lying. But we, uh, we definitely try to place a very high priority on testing at Ortus, at least with the pro, the projects that we work on and the products that we do.Brad (08:35):So, um, you know, that's one of the reasons I think it would be really fun to open source stuff like ForgeBox is because we actually have really good test coverage in our ForgeBox site is kind of a shame that, uh, that, that that's a closed source, you know, application just because it would be a really great example of, you know, what does it look like to have integration testing that kits your entire API. But yeah, we, we definitely pushed pretty hard. Luis like the task master. He's got his whip out and he's like, write more tests. That's basically, you know, an average day at Ortus. SoGavin (09:06):yeah, pretty much. Okay. Well you mentioned the one expectation for people, but um, like the whole ColdBox, no ColdBox thing, but whatever information or expectations should you have for employees before they come what do they need, what do they need to know? What, you know, what do you expect from them coming into it?Brad (09:25):We don't have a great deal of prerequisites for.Brad (09:27):This, um, oftentimes I give this sort of course in the context of a ColdBox training. Uh, but we really kind of start from scratch as far as what does TestBox, how does it work, what are the main, you know, major pieces. Uh, if you have a familiarity with TestBox ahead of time, that would obviously be, um, good. It gives you a leg up. Um, you should be familiar with, uh, just the typical closure syntax and CFML, um, which has been around for a while, but I realize not everybody deals with it, especially if they write a lot of tags. Um, but the BDD style of testing uses a syntax that uses, uh, closures, sort of the anonymous functions, uh, to help define each of the specs that we test. So if that's a syntax that isn't quite something that looks familiar to you, um, you know, maybe you can brush up on what that looks like, but, uh, you know, we'll, uh, we'll use CommandBox, um, just to install TestBox and run some tests, maybe do some basic scaffolding.Brad (10:24):Um, so if you don't have CommandBox installed and you're planning on taking this training, you know, something you want to brush up on a little bit. Um, but we really kind of start at the beginning as far as, um, you know, how TestBox works and how the pieces fit together. Um, so like I said, there's, there's not a great deal of requirements. You certainly don't have to be using ColdBox. Um, like I always say, uh, you know, you can get a lot of value out of TestBox, uh, just in, you know, legacy code framework, one CFWheels, any kind of application. I think you'd get the best experience when you use test box alongside a ColdBox because we have some really sweet, you know, integrations that are low level. But if ColdBox isn't in your current stack or maybe it's not in a bunch of your legacy stack only and some of your newer things, um, don't let that be, uh, you know, turn you away from this topic. Cause it's definitely more of just a, this is how TestBox works. And once you know that you can kind of test anything. SoGavin (11:15):For sure. So you've mentioned a little bit, but let's go into a little more detail. So what do you think people are gonna learn from this workshop?Brad (11:25):Right. So I think first and foremost, um, understanding of, of why they should test and what they should test. Maybe some information to help them convince, you know, managers or other developers that don't see the value in it. Um, some of the information we cover talks about, you know, studies that have shown hard costs and you know, how much more money you spend on a project that you don't test up front. Um, basic, you know, understanding of how TestBox works, how to write tests. Um, we'll cover a little bit of mocking and stubbing. Not a great deal that's, that's a bit more advanced and it's only a one day workshop. Um, but kind of just all the pieces and how they fit together. So, you know, it is a workshop, so people will be following along, building stuff. So you'll be standing up, you know, a test suite with, you know, some examples and you'll get to be able to, you know, run it from this DLI or on it from the browser.Brad (12:16):Two different outputs and we'll talk about all the different things, uh, your expectations, which are kind of like a assertions. Um, you know, you can check variables to exist, you know, check arrays to have length check things to be true or false. All those kinds of basic inner workings of, building a test suite will be covered, um, in this. And hopefully it'll, you know, wet people's appetite such that once they, you know, get away and they start plugging into the real apps, they'll be able to dig in and learn some of the more advanced stuff, uh, on their own.Gavin (12:46):Cool. Okay. So what do you think is your favorite part about this workshop? is there some part, you mentioned that you liked seeing the light, the light go on when they finally get it about why they should test or whatnot, but, you know, is there a favorite part of the workshop?Brad (13:02):Um, probably, uh, I usually will, will show people the code coverage stuff, which the code coverage is a feature that requires a future reactor license. So if you don't have a Fusion Reactor license, uh, you can't use it. But I'll usually at least demo that to people and show that it's a builtin functionality in the TestBox. Uh, you run your test suite on a server that has Fusion Reactor and Badda bing budda boom you get like code coverage. And I just absolutely love that feature. Because, uh, well first of all, like every other language in existence has it, and ColdFusion. It took us a long time to get this, but we'll actually show you, um, how much of your application is being hit by your unit tests. So if you have a, a CFC with three methods and you only have test written for one of those methods, you might not realize it, but the code coverage will raise a little red flag and go, Whoa, Hey, Hey, look over here.Brad (13:49):You see the CFC? Yeah, your test ran this guy. But what about these two guys? They never even got tested. Right. And then you're like, Oh wow, we should probably add some tests for those. Um, so that's probably one of my favorite parts even though it was kind of a, a little side note that I like to show people. Um, but we really love the code coverage, you know, uh, we've been adding that. Some of our clients, you know, get lab pipelines, know, calculate in how much of their, their application is covered by the test every time we run it. And it's a really fun feature. So it's probably one of my favorite things.Gavin (14:20):Cool. Okay. Well I think that's a good little summary of what to expect at the intro to BDD workshop. ITB 2020 in may. And this is a one day workshop but it's available on both days. So if you pick it on the first day, you can pick something else on the second day or vice versa. So if you want to take, like Eric's Intro to Quick one on the first day, you could still take Brad's Intro to BDD on the second day. So, and if you're really brave, you can take it twice. That's right. So, yep. So workshops are available on, you can go register now and we really looking forward to a good workshop. That's always a good time to meet people and interact and make some friends. And then obviously the conference following the workshops is always a good experience. So yeah, I think that's, that's it for you, Brad. You're free. I know the workshop is not free, but, but anyway, so. Yep. So thanks for Brad for your time and then, uh, yeah, I'll be interviewing you later about your sessions you'll be doing at Into the Box as well.Brad (15:21):So thanks for having me on Gavin.Gavin (15:23):Okay, have a good one, everybody. Bye. Bye.★ Support this podcast on Patreon ★
Watch the video version you YouTube: Pickin interviews Charlie Arehart, Server Troubleshooter and Trainer leading the Troubleshooting Common CF/Lucee Server Challenges Workshop at Into the Box 2020 in Houston Texas, May 2020. Find out what the workshop is about, why you should attend, what you need to know before you attend and what you'll learn while you're there. More information: can support us on Patreon here the show notes - visit the website from this podcast used under Royalty Free license from SoundDotCom and BlueTreeAudio https://bluetreeaudio.comTranscript: Coming soon★ Support this podcast on Patreon ★
Watch the video version you YouTube: Pickin interviews Luis Majano, creator of ColdBox, CEO of Ortus Solutions and Trainer leading the ColdBox Hero to Superhero API Edition  Workshop at Into the Box 2020 in Houston Texas, May 2020. Find out what the workshop is about, why you should attend, what you need to know before you attend and what you'll learn while you're there. You can support us on Patreon here the show notes - visit the website from this podcast used under Royalty Free license from SoundDotCom and BlueTreeAudio https://bluetreeaudio.comTranscript: coming soon★ Support this podcast on Patreon ★
Watch the video version you YouTube: Pickin interviews Jon Clausen, one of the creators of the CommandBox Docker Images, Senior Software Developer for  Ortus Solutions, about his Containerizing CFML Applications Workshop at Into the Box 2020 in Houston Texas, May 2020. Find out what the workshop is about, why you should attend, what you need to know before you attend and what you'll learn while you're there. You can support us on Patreon here the show notes - visit the website from this podcast used under Royalty Free license from SoundDotCom and BlueTreeAudio https://bluetreeaudio.comTranscript: Gavin Pickin (00:31):Welcome to the Modernize or Die Podcast, Conference Edition. And today I'm talking with Jon Clausen about his workshop at, Into the Box in May. And so, uh, Jon, thank you for joining me.Jon Clausen (00:41):Absolutely. My pleasure.Gavin Pickin (00:42):Your workshop is Containerizing CFML application. So do you want to tell us a little more about it?Jon Clausen (00:49):Well, it's, I mean, as we all know and are aware at this point, if you're, if you're not aware, you're kind of living in a kind of a tunnel or something, but the container space just continues to expand and blow up. And there are a lot of options available to you now. And even since last year, we've got, you know, more expanded usage of a lot of different containerization strategies. What we want to do is provide one day of giving, users, CFML developers, an opportunity to understand how to containerize their applications, what are the logistics of it, you know, software, you know, hardware, requirements, things like that. How to, actually, deploy your code in those containers. And then how to handle, consistency between multiple tiers of your applications deployment. So from development to staging production. So we'll start off the day by giving you an overview of containers... and then as we go through the day, we'll actually do more and more things with it, to the point where by the end of the session, you will have started the process or possibly even have finished the process of containerizing one of your own applications. With its dependencies in a stacked environment. So it's a very hands on workshop. There's certainly a lot of information, so you know, come prepared to learn. But it's also something that, I think a lot of developers who have taken the workshops in the past have found very useful and has helped to jump start them in their own containerization strategies.Gavin Pickin (02:18):So obviously you mentioned earlier on containerization is big these days. Is there anything else that you think people should know? Like why is this workshop really important for CFML developers or developers in general?Jon Clausen (02:30):I think for CFML developers in general, I think that there's many of us who've been developing a language for a long time who started on bare metal hardware, big old monolithic servers, where all of our dependencies were packaged as one. And I think, I don't know that, five years from now you're going to have the tools you need to do your job, if, especially if you're a full stack CFML developer without at least understanding containers. So I think that's part of it. I think that it's an important technology to learn. It's an important technology to master. Although there's a, you know, we're not going to build a master of one day, but you should be at least on a path to help you do that. I think that's a big part of it. I think for, developers in general, I think that when you containerize your application stack, it contributes to a lot more worry-free code.Jon Clausen (03:23):It contributes to agile development in the sense that small iterations are tested and ready to go and pass all their health checks and they perform the same way and every tier before they, before they're deployed. So I actually think that, I find it to be essential. I mean, I think there's folks that have stinking thinking about it and one way or another, but I find containerization to be essential to keep the, you know, the consistency between deployment tiers, you know, solid, and then also be able to, introduce new features in a way that's much less worry free because I don't have to worry about the environmental aspects.Gavin Pickin (04:02):Yeah. I mean, another thing that I mentioned to, you know, just all throw my 2 cents in here, but, with Docker, you know, it really takes away some of the bad baggage that ColdFusion has. Cause a lot of companies these days, they know, they don't know how to maintain it. They don't know how to deploy it. And a lot of feedback we hear anyways that, you know, they've got these apps and they're DevOps people don't want to support them, but once you dockerize it and make it, here it's a container, go deploy it, they know how to do that. They know how to maintain it, they know how to deploy them and Orchestrate them. And so I think you can actually help, you know, companies keep working with ColdFusion when they're getting to this DevOps age where everyone seems to think it's a dinosaur. So, I've noticed a lot of people...Jon Clausen (04:48):No, go ahead. I was just saying, I think a lot of people, you know, they're, they're used to these old monolithic installations and I think the days of the, you know, monolithic server are dead if not dying quickly. And I think that, you know, containerization makes that very easy. It makes CFML apps viable again. And with, you know, open source technology like Lucy and some of the containerization licensing like that Adobe has, it's a real option for people to use.Gavin Pickin (05:21):Yeah. Especially with the 2020 updates coming out, where they're working on modularity and smaller install sizes and everything, they're definitely moving that way cause they know it's important. And so...Jon Clausen (05:32):Not to mention the fact that now in CommandBox and this'll be, by the time we do Into the Box, there'll be a release on this, in CommandBox, you can actually generate a bash script that bypasses the need to actually even use CommandBox in your containers. It's a straight script. So previously, you know, if you wanted to start a server with CommandBox, it was Java in Java. Right? That's no longer necessary because we're actually able to, to generate a script, wipe CommandBox completely from the container and then actually use that one script to run that job a process. And it's slickGavin Pickin (06:04):Very cool. Yeah. So I guess that leads right into the next question. So why are you the right person to lead this workshop?Jon Clausen (06:11):Ah, well I guess it's probably just cause I got on the containerization bandwagon At Ortus earlier than everybody. I guess I think that, you know, I'm not going to honk my own horn here toot my own horn. But I think that, you know, I've spent quite a bit of time in this space, from the earliest development of the Docker CommandBox images. I've done extensive use of Docker, you know, personally and also professionally and day in and day out. I work with it. I mean, I don't use any other development environments when I code the CFML anymore. All of my database servers, caching servers, elastic search, everything is all containerized. So, I think I've got a fair amount of knowledge to bring to the subject and, I also have some tremendous, you know, team members who will be helping out during the day to help with some of the more environmental specific things. So I think it's a team effort, but I'm uh, I'm happy to lead it.Gavin Pickin (07:10):Yeah. I mean you've done some great work on the Docker images and we've compared to Lucee images and Adobe's images and everything. And I mean obviously we use them all the time. So as we come up against some hurdle, you guys update these Docker images for CommandBox to handle everything we want and need. I mean it's like secrets are built in and it just, it's a such a smooth workflow and yeah, you guys are a lot of great work on that and keeping up on date. as new stuff rolls out too.Jon Clausen (07:37):Well, and I think there's a couple of tools now that we've had of it. We have now that we didn't even have when we started with the Docker images and we've got CFConfig, which basically allows you to pre-configure an entire server. There's no need to like move files into the file system and deal with XML files and stuff like that where like with the Lucee containers, you can just, BOOM you know, have your production config and then use environment variables in that. So you can use a combination of hard coded settings and environment variables. and it just, you know, it just works. And then there's also, you know, between that and dotEnv, which allows you to source in environment variables. You know, we've just got a ton of tools that are available with the CommandBox image and, you know, we use it right now, we're using it in so many different places in production with both Adobe engines and Lucee engines. Then some people are even using it for like old, like Blue dragon images. So I mean, cause you're gonna run any, basically any war file, any, you know, any jar file from the CommandBox. So, it works pretty well.Gavin Pickin (08:45):Very cool. So if someone's wanting to take your workshop, what type of expectations or prerequisite knowledge does someone have or need to have before they come to really get most value out of this?Jon Clausen (08:59):There are prerequisites there? And one of the things that we need, to come with so, that you can come prepared to actually do your work on your own computer with your own stack, is you're going to have a machine that's got at least 16 gb of Ram. Just so you can start a stack. 8gb, will probably do it for you. but if you, you know, you want to be able to work and be speedy, probably 16 gigs of Ram. You need to make sure that you have Docker installed, the latest version of the Docker engine installed along with the Docker compose binary as well. So you'll need to come, come prepared with some tools. Also some code and maybe, if you, if you're going to have a database dependency or, or any kind of dependency that requires data, bring at least a sample of that data that you can load into a containerized database.Gavin Pickin (09:42):Okay. So we'll obviously send out some requirement emails to remind people of those things.Jon Clausen (09:47):Yeah.Gavin Pickin (09:47):But what about knowledge? So do they need to know a Docker is or you know, like do they need to have any history or...Jon Clausen (09:53):Nope, not at all. You can come to, you can come there and we go through that. Uh, you know, obviously as the years have gone by, more and more people are at least familiar with the basics of it. So, we would customize that a little bit. But yeah, we're gonna, we're gonna talk to you about containers and what they are and how they work and where you can use them and all sorts of information from the get go. So it's not really necessary other than what's necessary to run the installer to install Docker on your machine.Gavin Pickin (10:17):Okay. Sounds good. Now, I know that you just did a webinar last week, on containerizing CFML applications. Would that be a good thing to them to watch beforehand to get an idea?Jon Clausen (10:28):Yeah, absolutely. There's about probably 15 minutes of stuff that we cover in that. and, and there's a bunch of stuff that we kind of go through fast to show people how to do it. So we'll actually have, the nice thing about the workshop is we'll have our time to dig into some of those things and what's going on and what's happening with ports and allocation and crosstalk and all that. So there's, there's benefits of the workshop in that, but definitely, you know, please take a look at that. There may be a little bit of review during the day of the workshop, but it's probably 15, 20 minutes review at the most.Gavin Pickin (10:59):Okay. Well that sounds good. I just thought I'd give them a good taste of what they might get out of the workshop.Jon Clausen (11:04):Absolutely. Without a question.Gavin Pickin (11:05):Okay. So you mentioned a lot of things. Do you want to sort of give us a rundown of what will people learn in the workshop? What should they get? You know, when they leave, what should they be able to do?Jon Clausen (11:16):Well, by the time you're done, you're going to be able to understand how to take one of your applications, your own personal applications and containerize it. And you know, you may get all the way there during the course of the workshop or you may get part of the way there, but you'll at least understand the basics and the fundamentals of how to do it. You''ll understand how to, uh, you know, how to start and stop a container, how to poke around on the file system of the container, how to configure that container. How to, you know, Mount your, your code into a like a running Docker container, but also how to package your code in building a custom image that's got everything ready to go. So there's a lot of different, a lot of different information we'll cover. We'll also can cover, cover some, some of the basics of deploying stacks and creating stacks with Docker Compose so that you can see how to, how to package your dependencies for a particular tier like development or environment. We'll talk about stack deployments. We'll talk about Docker swarm. We'll, we'll touch on Kubernetes, although this really isn't the Kubernetes presentation, but we'll spend some time talking about that. And spend some time talking about the different ways in which you can deploy your application and different vehicles to allow you to do that out there.Gavin Pickin (12:32):Okay. Sounds good. So what do you think your favorite part about teaching this workshop is?Jon Clausen (12:38):You know, I think my favorite part is actually usually, it comes to maybe three days later and sometimes a year later, which is when people have adopted the technology. We've got some of the, some of our biggest contributors to that project. Now, some of the people who are most active in the containerization community are people that were in that containerization workshop two years ago. And they've now, they've now gone from, from learning it to becoming experts. And they're invaluable members of our community. And so it's really, the workshop is, was wonderful seeing the light bulbs come on and people and yes, there's some frustration and it's nice to be able to help people, you know, kind of overcome some of the things that frustrate them. But that the biggest benefit that I've seen is being able to see people, you know, take the technology and just run with it in their own projects and become adopters and raving fans. And you know, we've got a lot of, a lot of community leaders in this container space, in the CFML community that are, you know, that that started out learning about Docker and that workshop.Gavin Pickin (13:40):Very cool. Yeah. And that's the other thing too I really like about the workshops is you have like a cohort, you know, you've got a group of people and so they can help each other. And a lot of the times we set up a Slack group for the workshop as well, so people can ask questions later and you know, touch base. And I always find the best thing when I'm teaching a workshop is that later on when someone asks a question, other people in the group help answer and they help guide and you know, you get that teamwork and some comradery. So even if you're, you know, this is your job and you're on your own to figure it out. You're not on your own when you've made some friends that Into the Box in a workshop or, or whatnot. So it's a very cool, so this is a a one day workshop like you mentioned, but we're offering on two different days. So the beauty of this is, is if there's something like the elastic search one that you want to take on one day, you can still take Jon's on the other day and vice versa. So some of the two day workshops, you don't get a choice. There are two days full of content, but the one day workshops like this, you can basically pick and choose two. And, Jon is repeating the workshop. So that way, no matter what you choose on one day, you can always pick Jon's on the other. SoJon Clausen (14:48):Let's pick somebody from the first day and let them teach the second day.Gavin Pickin (14:52):Maybe. Yeah, if you're dumb enough to sign up for two days, you might be teaching it the second day. How about that? It sounds like a great workshop. I know this is the most popular workshop over the last couple of years. We're always in sell out. So I know that you're getting a couple extra helpers to make sure we don't, you know, we have a little more room cause it's definitely an in demand workshop. SoJon Clausen (15:13):Yeah, it'll be good to have two days. with small, little smaller groups and then we'll be able to spend a little more time, a little more one on one time with people. So I think breaking into two days is a good strategy.Gavin Pickin (15:23):Yeah. Okay. Well, I really appreciate your time, Jon and talking to us about your workshop. I know it's going to be great and hopefully this podcast will give someone, you know, a little more information so they can go sign up Go get your tickets. And, yeah, we look forward to seeing everybody in Houston in May.Jon Clausen (15:42):Absolutely. My Pleasure.Gavin Pickin (15:43):Okay. Thanks very much JonJon Clausen (15:52):Ok, goodbye★ Support this podcast on Patreon ★
Watch the video version you YouTube: Pickin interviews Michael Born,a Software Developer for Ortus Solutions, about his CBElasticSearch Workshop at Into the Box 2020 in Houston Texas, May 2020. Find out what the workshop is about, why you should attend, what you need to know before you attend and what you'll learn while you're there. You can support us on Patreon here the show notes - visit the website from this podcast used under Royalty Free license from SoundDotCom and BlueTreeAudio https://bluetreeaudio.comTranscript: Coming Soon★ Support this podcast on Patreon ★
Download from Google Play
Download from App Store