HackerTrans
TopNewTrendsCommentsPastAskShowJobs

ke4qqq

no profile record

Submissions

Oracle Opens MySQL Governance

blogs.oracle.com
6 points·by ke4qqq·19 giorni fa·0 comments

[untitled]

1 points·by ke4qqq·mese scorso·0 comments

ExtendDB – DynamoDB API compatible adapter for Posgresql

aws.amazon.com
3 points·by ke4qqq·2 mesi fa·1 comments

OpenAI Models Coming to AWS

twitter.com
3 points·by ke4qqq·3 mesi fa·0 comments

[untitled]

1 points·by ke4qqq·4 mesi fa·0 comments

You deleted everything and AWS is still charging you?

jvogel.me
46 points·by ke4qqq·4 mesi fa·33 comments

AWS Free Tier now limits billing by default

docs.aws.amazon.com
2 points·by ke4qqq·12 mesi fa·0 comments

Neutral WordPress package manager launches at the Linux Foundation

fastcompany.com
7 points·by ke4qqq·anno scorso·0 comments

Inter-Agent Communication on MCP

aws.amazon.com
1 points·by ke4qqq·anno scorso·0 comments

[untitled]

1 points·by ke4qqq·anno scorso·0 comments

comments

ke4qqq
·11 mesi fa·discuss
As the cited ‘boss’ I’ll say the publicity wasn’t the concern. The concern was that someone wanted to use our services and we had made that so frustrating that they were writing blog posts about how it had gone wrong.

The various teams (anti-fraud and support) are investigating how we failed this customer so we can improve and hopefully keep this from happening again. (This is the ‘Correction of Error’ process that’s being worked on. And CoE’s aren’t a punitive ‘blame session’ - it’s figuring out how a problem happened and how we can fix or avoid it systemically going forward).

To be fair, the publicity did mean that multiple people were flagging this and driving escalations around it.