Or at least I could blame all the problems I ran into on my complete novice status when it comes to JavaScript and TypeScript at the time. When I learned just enough JavaScript, and by extension TypeScript, to be dangerous, it worked a lot better. In my experience, when I tried it for the first time in Python, it was not a great experience for me. The problem I run into, and this is true of most things in my experience, when a company says that we have deployed an SDK for all of the following languages, there is very clearly a first-class citizen language and then the rest that more or less drift along behind with varying degrees of fidelity. It’s the block printing to the script that is basically Java cursive. I think those are the currently supported languages.Ĭorey: Java.
Matt: Yeah, it’s: TypeScript, JavaScript, Python Java.Net, and Go. NET, Python, there’s obviously TypeScript, there’s Go support for it-I believe that went generally available-and I’m sure I’m missing one or two, I think? Aren’t I? The first and most obvious one is that AWS claims publicly that it has support in a bunch of languages. And as I went through the CDK, a couple of times in service to a project that I’ll explain shortly, I made a bunch of missteps with it. That sometimes works out, sometimes doesn’t. Whenever I wind up having a problem that StackOverflow doesn’t immediately shine a light on, my default solution is to resort to my weapon of choice, which is brute force. So, the whole piece of it is that it’s a developer experience, developer speed play, that if you’re from a background that you’re more used to writing a programming language than a YAML, you might actually enjoy using the CDK over writing straight CloudFormation or SAM.Ĭorey: When I first kicked the tires on the CDK, my first initial obstacle-which I’ve struggled with in this industry for a bit-is that I’m just good enough of a programmer to get myself in trouble. So, it doesn’t really matter what you write in your script the point is, at the end of the day, you still have the CloudFormation template that comes out of it. Either way, it lets you write code that produces CloudFormation. Matt: Yeah, so we like to say it’s imperative code written in a declarative way, or declarative code written in an imperative way. And if you’re listening to this, and you haven’t heard that show, it’s not that necessary to go into mostly it was me spouting uninformed opinions about the CDK-the Cloud Development Kit, for those who are unfamiliar-I think of it more or less as what if you could just structure your cloud resources using a programming language you claim to already know, but in practice, copy and paste from Stack Overflow like the rest of us? Matt, you probably have a better description of what the CDK is in practice. Matt: Yeah, thanks for inviting me back, especially to talk about this topic.Ĭorey: Well, we spoke about it a fair bit at the beginning of the year. Matt Coulter is a senior architect since he has been promoted at Liberty Mutual.
My guest today returns from earlier this year. Well, do I hold on to that original opinion with two hands at a death grip or do I admit that I was wrong in my initial opinion about something? Let’s find out. But what happens when things change? What happens when I learn new things? One of the best parts about, well I guess being me, is that I can hold opinions that are… well, I’m going to be polite and call them incendiary, and that’s great because I usually like to back them in data. This is Screaming in the Cloud.Ĭorey: Welcome to Screaming in the Cloud. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. You can usually find him sharing reusable, well architected, serverless patterns over at or behind the scenes bringing CDK Day to life.Īnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. He is focused on creating the right environment for empowered teams to rapidly deliver business value in a well-architected, sustainable and serverless-first way. Architect in Belfast, an AWS DevTools Hero, Serverless Architect, Author and conference speaker.
0 kommentar(er)
