#aws

I usually just take notes while I'm working on something that I will write up into an article, then work from those notes when I put the piece together. My latest I started working on, using AWS to deploy a rather simple API application, has become so complicated at this point I'm tempted to throw it away. The wild thing though, is that it is almost purely based on the utter chaos and madness that is the current state of AWS services. There are so many and the interface has, at this point, become so jumbled and disorganized it is nearly impossible - without reading tons of material about where things are or have gone - to figure out how to get anything built and deployed. It's definitely not the early era of AWS anymore, and it makes sense that they're attempting to push Q (or whatever the name is) so AI just sorts out the mess for ya. The way it is all organized (or not) that's about the only way you'll be able to make any sense of it all. All that said, this is indeed a perfect example of where something that is relatively unusable can be made usable with some good models that know how to effectively use it via skills files or what not. On that note... back to the mines.

Still amazing that AWS is wasting all that time managing that Python CLI when they could just move it to Golang and actually get us real native binaries that run cleaner. It's such a surrealist mess of glued together libs and all. 😑