AWS in 2025: The Stuff You Think You Know That's Now Wrong

Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by simianwords on Thursday August 21, 2025 @03:52AM (#44970234)

I agree but its about the extent. I'm willing to accept the risk of ocassionally making S3 public but getting things done much faster, much like I don't meticulously read documentation when I can get the answer from stackoverflow.

If you are comparing with stackoverflow then I guess we are on the same page - most people are fine with taking stuff from stackoverflow and it doesn't count as "brave".

[ Parent | on HN ]

Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by dcminter on Thursday August 21, 2025 @04:09AM (#44970340)

I think anyone who just copies and pastes from SO is indeed "brave" for pretty much exactly the same reason.

> I'm willing to accept the risk of ocassionally making S3 public

This is definitely where we diverge. I'm generally working with stuff that legally cannot be exposed - with hefty compliance fines on the horizon if we fuck up.

[ Parent | on HN ]

Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by simianwords on Thursday August 21, 2025 @04:39AM (#44970487)

That's fair - I would definitely use stackoverflow liberally and dive into documentation when situation demands it.

[ Parent | on HN ]

Re:AWS in 2025: The Stuff You Think You Know That's Now Wrong by awongh on Thursday August 21, 2025 @06:31AM (#44971089)

The thing is that you can now ask the LLM for links and you can ask it to break down why it thinks a piece of code, for example, protects the bucket from being public. Things that are easy to verify against the actual docs.

I feel like this workflow is still less time, easier and less error prone than digging out the exact right syntax from the AWS docs.

[ Parent | on HN ]