I Broke Amazon Twice. Here’s How. │ TWICE動画まとめ速報！

コメント（10件）

@ALifeEngineered より:

12月 19, 2024 10:48 pm

Use coupon code engineered at to get a free 3-month trial of NordPass Business, no credit card required.

🚀 Get promoted in 2025 by taking my FREE 5-Day Promotion Accelerator Challenge –
💥 Continue the conversation on my Discord server with like-minded ambitious tech professionals. #accountability is *chef’s kiss* and #wins is motivating –
📈Transform your tech career with my free weekly newsletter –
@anjunzhouJack より:

12月 19, 2024 10:48 pm

awesome vid. as a mid level engineer, i echo with what’s in the video. and hoepfully i’ll not be at the end of a sev1.
@BitCloud047 より:

12月 19, 2024 10:48 pm

Awesome video as always man!
@DiabeticGameGuy より:

12月 19, 2024 10:48 pm

God, I remember those. My team caused one sev 1 while I was there and it still hurts.

The year was 2008, and my team (Warehouse Deals) had just migrated to a new order and fulfilment pipeline. Everything was working well, BUT none of the reports were prepared for orders to flow through this channel. There was a hard coded value to ignore us in the main Amazon reports, but after the migration all our orders were double counting. This polluted all the data in the Datawarehouse for every category where Warehouse Deals had products. The revenue and COGS were off by millions!!!

It was a brutal time as it was a major issue completely impacting the business, finance and DW teams, and our little team was the main root cause. All the retail VPs and Directors saw a decrease in their WBR metrics. The consequences were above my paygrade as I was just a L6 Software Engineer Manager. Our whole team was reorged to retail from ops shortly after this happened.

Another incident that was only a sev 2 happened when we misran a pricing script for WarehouseDeals. This was in 2007, and our mistake made the NBC national news. This was about 5 months after I joined the company, and I was sure that I’d be fired. Thankfully, I lived through it though.
@drew_echo より:

12月 19, 2024 10:48 pm

The learning from the mistakes part is important. Once we had a principal level engineer with a prod breakage rate that was measurably 10x higher than anyone else in the company. The company took the blameless culture too far & each time the answer was what can we do to prevent this from happening rather than addressing the elephant in the room. We ended up spending significant resources babyproofing everything for one engineer rather than surgically operating on the root cause. “Lightsaber night is cancelled. Thanks Todd!”: If you aren’t willing to act on gross recklessness, then the organization will build layer on top of layer of bureaucracy that punishes everyone. We extended procedural due diligence by two weeks or more to release changes for the entire organization to blamelessly prevent one engineer from breaking prod nonstop.
@jhors7777 より:

12月 19, 2024 10:48 pm

Great video and channel Steve. Thanks so much. You have a wonderful gift for communication.
@bstancel12 より:

12月 19, 2024 10:48 pm

Your describing between you and the S3 department sounds just a tad better than every interaction with AWS Business Support.
@randxalthor より:

12月 19, 2024 10:48 pm

Great insights! Thanks for sharing your experiences so that we can all avoid making the same mistakes.
@Phanboy より:

12月 19, 2024 10:48 pm

That interaction with services team is 💯. Make no assumptions, treat everyone like AI 😂
@BentleyPascoe より:

12月 19, 2024 10:48 pm

During my time at one of the experimental teams for Amazon Games, as a QA Stakeholder, I was extremely proud that my projects never caused a sev2. Sad to say that was a first for Game Growth, but great learning for our entire team and it created a number of process changes and guidelines for our QA work that lead to an increase in our quality bar. The interaction skit between Steve and S3 is something I experienced to, with another QA team doing tax and accounting User Acceptance Testing. I was the stakeholder for Amazon Games Studios’ (AGS) new Tax and Accounting team and trying to get help deploying some specific testing and tooling was a similar process:
Do you have a tool or process that allows [various testing scenarios], I have not found documentation on it in my searches so far? “Yes.”
Can you share that with me? “Sure!” *waits for document link*
Uhm, not to rush, but I have a short timeline here, can you please share the documentation and where I find those tools “Oh, well why didn’t you ask – let’s get in a call and I’ll get you set up!”

Fun times!

I Broke Amazon Twice. Here’s How.

twiceカテゴリの最新記事

Con mala calidad porque capcut esta hambriento :: #mina #minari #twice

مومو مرة ضابط معها الصوت#enhypen #engene #jungwon #twice #explore #kpop #idol

JAJAJAJAJA NSE Q HICE #kpopgrupo #twice #tzuyu #momotwice #nayeon #humor #nomedejenenflop

How Twice Mina was looking really beautiful at Cannes 2025…#shorts#twice#mina#kpop#kpopidol#fyp#fypシ

top 5 des groupes…🧸🦋 #kpop #twice #seventeen #straykids #blackpink #bts

فديتهم 🤏🏻😾💗 #dancehall #remix #newmusic #music #dance #blackpink #المراه #twice #المراره #kpop