Live data from Hacker News

'Sloppenheimer:' Amazon employees mock the company's AI on Slack

404media.co

91–100 of 105 posts

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#91
Amazon employee here.

- Can confirm that channel exists and it's great. Rofl every day for all the stupidity happening in the company.

- Despite many seeing Amazon as outsider for AI, it's actually a great place to work (if not fired). We have free access to all frontier models, including today's Mythos release for all employees.

- Every model available on Bedrock is available for free with no caps. I think it's because these models are deployed on trainium chips which is essentially free for Amazon.

- Claude code and Codex are available unlimited for employees.

- For this one I will be bitten, but I actually like Kiro CLI. It's powered by the same Anthropic/OpenAI models. It's a bit easier to understand for me than CC and surprisingly does a better job at writing research papers.

- Amazon Quick, alternative to Claude Cowork, also has some nice features like in-browser presence so you don't have to copy/paste content from the web.

- I personally haven't seen a push to use AI at all costs. Yes, there are many internal tools being developed (e.g. meshclaw) but no one tracks their adoption for redundancy purposes. I think leaders are pretty consistent with what they communicate externally (e.g. hiring of juns).

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#92
post #2

"Sign up for free access to this post". There should be a rule about this kind of posts. If there isn't already. https://archive.ph/1YRCE

It’s the same as posting paywalls articles. There’s no need to make a new rule. If the users can’t read it, the conversation will simply devolve into title commenting.

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#93
post #3

I recently wound up in conversation with someone working at Amazon. Inevitably, the convo steered into AI/LLM's at some point. Here is what I learned: - AWS had an in-house LLM tool that was terrible they tried to use for a while - A lot of them still use Kiro - Claude Code is currently the de-facto standard - They're in the process of getting some custom Codex variant that doesn't phone-home and is audited approved…

- claude is relatively new, was only whitelisted about 1-2 months ago. kiro is still de-facto, a lot of ai tools use its acp as a back-end.

- there are no token budgets

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#94
post #13

Earlier quoted context omitted.

> If there isn't already. There is![0] [0] - https://news.ycombinator.com/item?id=10178989

Importantly, in that rule: > Complaints about paywalls are off topic, so please don't post them.

Which is ironic because if you cant read the article, how can you have a discussion?

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#95
post #79

Earlier quoted context omitted.

> There's no mandated organizational standard for what exact tools to some, various teams have different levels of adoption and stacks > No org-wide/team-wide conventions for Claude Code Just for context, this pattern (different teams using different tools in different ways) is extremely normal within Amazon, and is intentional. These shouldn't necessarily be seen as a failure. Amazon likes to have multiple competing…

How does anyone intentionally decide to migrate to Teams?! I've only ever seen it in Microsoft shops that used it from the beginning.

Some dipshit with too much power and not enough brain cells nor incentive to care about making good choices. That's also an intentionally chosen pattern throughout the company. :)

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#96
post #37

Earlier quoted context omitted.

You guys haven't been going to the meetings?

No, my horse broke down so I've been stuck at the farm.

No worries, comrade.

I've gone ahead and moved this week's meeting, which happens to be tonight, to your place.

We'll be there soon.

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#97

Another one of these 404 Media bait posts, okay, we got it, there's internal staff memes. Related: Google employees internally share memes about how its AI sucks https://news.ycombinator.com/item?id=48400311

agree. im already beginning to see this domain as indicator of trash quality post

why would hackers be interested in this

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#98
post #83
post #59

Earlier quoted context omitted.

Would be really curious what the internal market share for Kiro is. Not a really good look for it if it's just smattering use here and there.

It's the worst harness i ever used. And they are selling it like crazy to all their enterprise customers who don't know any better. A true money printer at this point.

i like it a lot. why dont you?

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#99

Amazon employee here. - Can confirm that channel exists and it's great. Rofl every day for all the stupidity happening in the company. - Despite many seeing Amazon as outsider for AI, it's actually a great place to work (if not fired). We have free access to all frontier models, including today's Mythos release for all employees. - Every model available on Bedrock is available for free with no caps. I think it's beca…

Reminds me of Memegen from Google, the one thing I miss about working there.

Memes were top shelf; absolutely masterclass

Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack

#100
post #3

I recently wound up in conversation with someone working at Amazon. Inevitably, the convo steered into AI/LLM's at some point. Here is what I learned: - AWS had an in-house LLM tool that was terrible they tried to use for a while - A lot of them still use Kiro - Claude Code is currently the de-facto standard - They're in the process of getting some custom Codex variant that doesn't phone-home and is audited approved…

> There's no mandated organizational standard for what exact tools to some, various teams have different levels of adoption and stacks > No org-wide/team-wide conventions for Claude Code Just for context, this pattern (different teams using different tools in different ways) is extremely normal within Amazon, and is intentional. These shouldn't necessarily be seen as a failure. Amazon likes to have multiple competing…

You've missed out on migrating to Zoom, Asana, and Sharepoint now.
Post reply on HN