Here is my re:invent take away: DevOps was conceived before we had ELBs. We had a couple EC2 instances we treated like we racked ourselves and we ran Nginx or Apache with round robin. The keynotes should be a dead giveaway that learning software engineering and the cloud is harder today than it was when I learned it. There is a demand for infrastructure, even in a single organization, that the old DevOps loop can not fulfill. We need better tools to stitch the pretty good tools together and silo expertise in a fully expressive self service model. The pain is very real on both sides and I am excited for the challenges ahead.
Ian Sherwood
1w
100% I felt things getting harder with ecs and in retrospect that was smooth sailing compared to setting k8s up. Completely agree it feels like it's getting more complex to glue the pieces. do you think there will be a movement back to the basics?
Zothan Sanga
1w
debugging AWS Lambda code is much more difficult than troubleshooting it in Pycharm IDE
Developer, Speaker, Observability Evangelist and Microsoft MVP
1wWe see this in the o11y space too, applications and infrastructure have evolved, using the same old tooling and expecting the same, if not better, results is just a fantasy. I see the reason for cloud being "hard" is because the people teaching it are tackling it from a legacy up perspective (trying to teach the old then the new) rather than teaching the current paradigm. This is easier to solve in some languages and infrastructures, but some, where they rely on containers directly, you still need the old school knowledge of things like chmod/chown etc. My takeaway is we need to stop pandering to the old generation and focus on helping new people in tech do things in the new ways.