Day 4 of AWS re:Invent 2023 has come to a close and it was just as epic as the other nights. The day itself was a little slower due to my Day 3 evening ending fairly late, but there’s still a good bit to share. If you are looking for a full recap, I’m going to do one soon to sort of close the loop on my 2023 AWS re:Invent experience.
Let’s dig into Day 4 of AWS re:Invent 2023.
So this one is rough in the best of ways possible. It’s currently 2 AM Las Vegas time and I’ve been up since 7 AM the previous day. Back to what I said a few days ago, re:Invent is a marathon and not a sprint. At this point in the week, it feels like mile 18. I am tired but in the best of ways. The only thing I have to do is finish this race strong and to the best of my ability. Day 3 was better than day 2 and I’m excited to share with you how it went.
Let’s dig into Day 3 of AWS re:Invent 2023.
Amid everything going on, I stayed up after Day 2 of re:Invent to get my hands on the new Amazon S Q Digital Assistant. For more on the release here is the announcement. While sitting in the Adam Selipsky Keynote yesterday, a use case instantly popped into my head. The below example has no CDK or SAM but is purely a simple walkthrough of the functionality. Let me tell you about a time that Amazon Q met Taylor Swift.
Day 2 of re:Invent 2023 has come and gone and it was personally my best day yet. By the numbers, I’m at the halfway point with my two busiest days ahead. Let’s get right to my recap as it’s filled with all kinds of fun interactions.
Let’s dig into Day 2 of AWS re:Invent 2023.
Day 1 of re:Invent has come and gone and it was an epic start to the week. I’ve often heard it said that re:Invent is a marathon and not a sprint and that’s a very true statement. If you are reading this and are at the conference, pace yourself. And if you are at home watching virtually, do the same, but perhaps more mental pacing than physical.
Let’s dig into Day 1 of AWS re:Invent 2023.
Here goes the beginning of a nightly blog post recapping my experience at AWS re:Invent 2023 in Las Vegas. AWS re:Invent officially kicks off on Monday 11/27/2023 but for those of us who arrived early, the week started a bit early. Let’s recap Day 0.
For this series, I’m going to do a nightly recap of the things that I experienced at re:Invent. I plan to share my highlights from people I meet, exciting news drops or sessions I found to be fantastic.
I’ve had a few people ask me about my writing process and how I produced the articles and code that I do here on my blog. At first, I thought, no way anyone cares what it takes for me to produce the articles that I do. But as I stepped back and thought about it, looking back on my 1 year of solid writing I have developed a method to my creating. Hopefully, this proves useful and whether you are a veteran writer or just getting started, there could be something in here for you. Let’s dive in and take a look at writing a technical blog article.
I’ve been working recently with some data that doesn’t naturally fit into my AWS HealthLake datastore. I have some additional information captured in a DynamoDB table that would be useful to blend with HealthLake but on its own is not an FHIR resource. I pondered on this for a while and came up with the idea of piping DynamoDB stream changes to S3 so that I could then pick up with AWS Glue. In this article, I want to show you an approach to building a partitioned S3 bucket from DynamoDB. Refining that further with Glue jobs, tables and crawlers will come later.
I’ve been trying to learn Rust for the better part of this year. My curiosity peaked a few years back when I learned the AWS-led Firecracker was developed with the language. And I’ve continued to want to learn it ever since. Fast-forward and I’m jumping both feet in. That’s usually how I work. I must admit that right now, I’m the most noob of noobs, but that’s not going to keep me from sharing what I’m up to and what I’m learning. For me, this blog is as much about sharing as it is about learning and communicating to those reading that it’s OK to be where you are in your journey. There are no straight lines. Only periods of growth and plateaus. In this article, I’ll walk you through consuming an SQS Event with Lambda and Rust.
Some find that handling bad news as a leader is tricky. Their first thoughts range from figuring out who to blame, how to hide the damage or even just how to make the problem go away. I like to look at it from a different perspective. I want to embrace bad news. Treat it as a learning experience for those involved. And ultimately use it as an opportunity to build trust.
Follow along as I give you a few tips on how to embrace bad news as a leader.
