I've never worked in a big corporate environment, so I'm always surprised that these companies allow employees to mock their own products/managers/bosses. (Not saying it shouldn't be allowed, just that it's surprising based on how controlling I'd expect a big corp like Amazon to be.)
'Sloppenheimer:' Amazon employees mock the company's AI on Slack
71–80 of 105 posts
Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#72I'm surprised with Amazon and Meta in terms of AI. Less surprised with Google, I think Google has a very specific niche they picked. If you really think about it, you don't have to be the absolute best, you just have to keep refining your model for efficiency and cost, and I think that's Google's true goals and secret sauce. Google will snowball into place. They're also used more than most people realize. https://clo…
> Then there's Mark Z who is throwing away piles of money, but nothing to show for it other than letting people easily hack his social media sites? I mean, FB/Meta have been using lots of GPUs and compute for well over a decade at this point, they definitely are one of the few companies who can make use of relatively absurd amounts of these to drive revenue (i.e. improve ranking for both personal/organic and paid pos…
Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#73[flagged]
If you've been 20 years in and built the infrastructure you might disagree with new management and have a very clear view on the harm new policies are making. Professionals might be the ones that have skin in the game.
A professional recognizes the above and someone just there to pay the bills isn't.
Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#74Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#75Earlier quoted context omitted.
From the outside it always seems laughably circuitious compared to just learning skills ourselves. Even if it did let me fill out TPS reports 20% faster, who even cares compared to all of this chaos?
the problem is scale. there's a tension between an individual developing technical skills (transfer cost is high, slow, expensive) and developing agent skills (transfer cost is low, instant, free). so, just like a manager manages employees, or you consult a contractor, agents are a way of getting leverage over a system. that said, if you want to learn to play saxophone, you're free to do so. just note your personal e…
Additionally, for tech work. There is a tension about doing work and not knowing that output is correct or not. I have seen ai spit out thousands of lines of opencv code for a simple color lut. The person doing this had no idea what was going on. If they continued, the token cost and time waiting for agents spinning only goes up.
Yes, agents get smarter and cheaper but the above example replays over and over again even on crud apps. You still need to dev the skills and transfer costs for it to be effective.
Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#76Amazon’s attempts at AI tooling are just far too behind to be taken seriously. Kiro, Quick whatever, the Alexa updates. All just a hot mess. Amazon’s own employees appear to have abandoned Kiro en mass when allowed to just use Claude. Amazon should just focus on being a utility compute provider. Anything they try to do on top of that is just consistently second rate.
It’s all relative. Kiro is second to Claude Code, but Amazon isn’t really competing with Anthropic. They need something better than Microsoft/Github Copilot and that is a low, low bar.
Why?
What's wrong with using Claude Code/Codex?
Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#77Sidebar: I love how Amazon basically gave up on AWS Chime for Slack. Even dogfooding their own messaging product didn't work.
Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#78Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#79I 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…
I've only ever seen it in Microsoft shops that used it from the beginning.
Re: 'Sloppenheimer:' Amazon employees mock the company's AI on Slack
#80Earlier quoted context omitted.
It’s all relative. Kiro is second to Claude Code, but Amazon isn’t really competing with Anthropic. They need something better than Microsoft/Github Copilot and that is a low, low bar.
> They need something better than Microsoft/Github Copilot Why? What's wrong with using Claude Code/Codex?