AWS What's Next Event: Key Takeaways and Confusion

Well that was weird. What’s next with AWS (https://aws.amazon.com/events/whats-next-with-aws/), scheduled for 90 minutes, cut just short of it. Featured Sam Altman virtually (assuming on account of the lawsuit), and a very interesting studio design/outfits for the AWS folks.

I had mastered the webinar multitasking thing in the 2020s but in the past few years just couldn’t manage it, but made it work yesterday. Mainly because I was interested in Connect and was hoping to get some nuggets of what the NLX acquisition meant for Connect. New SKUs, as others put it, seemed to be the primary topic of discussion, which is good and promising, but with the current set of materials, doesn’t really paint a complete and understandable picture.

As a side tangent, I am surprised that both the document history (https://docs.aws.amazon.com/connect/latest/adminguide/doc-history.html) and release notes pages (https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-release-notes.html) are light/incomplete/delayed in providing information, and I have to go to the Newsletter (https://newsletter.connect.aws.dev) to figure out what’s going on, which tends to put me up to a month behind. Despite all these advancements in AI, something that’s become very evident to me, especially in the last year, is despite talent, despite technology, you still need process. I’m going to assume that AWS’ mass layoffs and poor hiring practices (despite academic justification for them) is playing a role until I am told otherwise. By the way, there are about a dozen pages like this I check daily, some not updated in well over 2 years. I wonder why I keep checking? On occasion there is a serious update, which keeps me coming back.

Having invested just short of an hour and a half yesterday, and finding myself with more questions than answers, and general confusion, I sought validation from the Internet, granted, not very in depth (LOL maybe I should have used AI), and since Twitter’s destruction, do not have a very solid place to go anyway (right now Instagram thinks I’m obsessed with 3D printing).

Deeper Dive into the Event and Its Implications

The AWS What’s Next event was anticipated with much excitement, especially considering the recent developments in the tech industry and AWS’s continuous push for innovation. The event’s abrupt conclusion left myself scratching my head. The studio design and the outfits worn by the AWS team were notably modern and visually engaging, setting a fresh tone for the event. (Nova re-wrote that, BTW, I was not very nice in what I had to say).

Connect and the NLX Acquisition

My primary interest in the event was Amazon Connect and the implications of the NLX acquisition. The focus on new SKUs is promising, indicating AWS’s commitment to enhancing its offerings. However, the materials provided post-event were lacking in depth, leading to more questions than answers. This highlights a broader issue: the need for comprehensive and timely documentation. The document history and release notes pages were sparse, and the newsletter, while helpful, often left me playing catch-up. This is a critical area for improvement for AWS.

The Importance of Process

One of the key takeaways from the event, and my experience with AWS in general, is the importance of process. Despite the talent and technology at AWS, the apparent lack of a robust process has led to delays and gaps in communication. The mass layoffs and subsequent hiring practices, while justified from an academic perspective, seem to have had a tangible impact on the quality and timeliness of updates and documentation.

Exploring New Tools and Features

Amid the confusion, there was a silver lining: the introduction of a new fat client for Quick. This app, previously known as Quicksight, is set to absorb Q for business purposes (in my opinion). The return of the fat client, or app, is something I’m genuinely excited about. These apps provide a more focused and less cluttered experience compared to browser tabs. I’ve already downloaded and installed the app, connected it to various services, and started exploring its features.

Security and Trust in Data Usage

One of the reasons I feel more comfortable with AWS’s approach is their practices around security and data usage. While I am hesitant to give Open AI access to my data, I trust AWS more in this regard. The app offers a promising way to organize my information, communications, mail, calendar, and files in a way that feels comfortable and secure.

Looking Ahead

With an update already available and the app not yet reaching version 1.0, I anticipate a rapid evolution similar to Kiro. I’m hopeful that this new tool will help streamline my workflow and look forward to potentially paying for a subscription once the trial ends. The journey with AWS continues, and I remain optimistic about the future developments, despite the current challenges.