slowdog

100% agree with this, seems weird to call an engineer “smart” for triggering an API that allows any input but can’t handle it. I also kind of doubt it was an engineer testing vs some much more subtle issue as billing is in line for everything.

If this was 10 years ago, this was also the era when any real customer could write any ARN (resource identifier) they wanted including commas due to no expected standardization across services. This could have been trivially triggered by a customer.

Just a matter of time if no one is escaping commas in billing files.

Even still, it's not as much information and doesn't excuse deleting creators work without any warning.

Not earlier commenter but their username is a reference to “ableton live” which is music production software. Not “able to live” which is just a one letter difference

It’s less that they’re flailing and more that it’s become some sort of lord of the flies culture with senior leaders directly competing with each other to try to take their bite of the pie.

The way AWS is structured with strongly owned independent businesses just doesn’t work, as GenAI needs a cohesive strategy which needs

1. An overall strategy

2. A culture that fosters collaboration not competition

Or at least an org charts to make them not compete with each other. (Example: Q developer vs Kiro)

I bet if you looked at the org charts you would see these teams don’t connect as they should.

As a heavy EC2 user who hasn't used ECS, the behavior makes perfect sense as ECS is running on EC2 but unless I sat and thought about it my first instinct would be that AWS would make it "secure by default" on a container level since containers often have different permission requirements and so the container would be the security boundary.

That said, I'm guessing it would have been obvious to anyone once they start setting up IAM permissions and therefore not much of a pitfall.

So it's a good reminder, but I agree with you, maybe the article doesn't need to be so long to get to the same point.

It's a reasonable take from the author, but the argument that you shouldn't use a tool you don't understand cuts both ways. Avoiding powerful tools can be just as much of a trap as using them blindly.

Like any tool, there's a right and wrong time to use an LLM. The best approach is to use it to go faster at things you already understand and use it as an aid to learn things you don't but don't blindly trust it. You still need to review the code carefully because you're ultimately responsible for it, your name is forever on it. You can't blame an LLM when your code took down production, you shipped it.

It’s a double-edged sword: you can get things done faster, but it's easy to become over-reliant, lazy, and overestimate your skills. That's how you get left behind.

The old advice has never been more relevant: "stay hungry."

A lot of what drives feed algorithms are interactions rather than just follows.

I imagine it’s one reason why X/Twitter made likes private as they want people to like things for the algorithm but not be judged for their likes.

I think most folks would disagree that the other commenter is on the "extreme" end of the privacy spectrum. It's very context specific. Some ISPs are state specific or even town specific.

I agree with my sibling comments, your evasiveness isn't helping us make up our own opinions on this matter.

Not sure how I’m demanding, just pointing out some differences between how different groups tackle this

This is one of the great parts of America, personal liberties. But simultaneously one of the downsides of the individual > whole scheme, sometimes sacrifices hurt the individual but are good for the whole.

Quite the conundrum, once you go down the whole > individual route, where do you stop?

I understand your sentiment and I’m sure you’re well meaning. But Asian Americans are one of the most diverse groups, it’s a huge part of the world and part of the problem is people assuming all Asian Americans are the same personality