Day Four – I’ve had all the AWS I can take (see project overview here)
More Pluralsight’s “AWS Developer: Getting Started” course by Ryan Lewis. The last couple sections cover CloudFormation and Elastic Beanstalk. I’ve made a preliminary decision to use Terraform instead, so I’m just going to listen to/watch these sections in the interest of time. The title of this page is Day Four, after all. While I haven’t been spending 100% of my time on this course, it has taken up a bunch of my time. Following along step-by-step is the only way to really learn something, but it’s time consuming!
Next up: AWS Developer: Designing and Developing. I’m going to breeze through this one, too. I am not planning to use node.js anytime in the near future. My plan is to hone my Python skills, so, while I’ll be using AWS to deliver my apps, I’ll be developing them in Python. I’m choosing Python because it seems more in-use at this time. I want to do my own thing, but I will definitely need to augment my income with “real” jobs. Based on what I’m seeing on job sites, Python is much more popular for real jobs than node.js. That could change. I’ve used node.js and I love it, but one must be practical.
I’m flying through, here. None of this will stick unless it’s just totally new. Sometimes flying through makes me aware of something I would otherwise be totally ignorant of.
This is a bunch of work to set up an environment with sdk code. It will be fun to see how Terraform (hopefully!) simplifies this work.
Boring, boring boring…
The AWS Developer: Designing and Developing course repeats a bunch of stuff from AWS Developer: Getting Started. That may be good for folks who are taking them at a slower pace. But, for me (these courses are all I’m doing for the awhile), it’s torture.
Bad day when torture comes up in the decription!