Steve Duong

968 posts

Steve Duong banner
Steve Duong

Steve Duong

@toidv

Head of Product @KrystalDeFi. A product guy trapped in engineer’s body. Builder. LPer. Simple is the best. NFA

Hanoi, Vietnam Katılım Mayıs 2011
1.5K Takip Edilen251 Takipçiler
Steve Duong retweetledi
Claude
Claude@claudeai·
You can now enable Claude to use your computer to complete tasks. It opens your apps, navigates your browser, fills in spreadsheets—anything you'd do sitting at your desk. Research preview in Claude Cowork and Claude Code, macOS only.
English
4.5K
13.2K
127.7K
62.5M
Animesh Koratana
Animesh Koratana@akoratana·
We're also giving away a curated collection of 200+ Claude Code Skills our team uses daily — the workflows that made us faster engineers while building PlayerZero. Repost and comment "100X" to get access.
Animesh Koratana tweet media
English
336
207
311
55.4K
Animesh Koratana
Animesh Koratana@akoratana·
Introducing: PlayerZero The world's first Engineering World Model that puts debugging, fixing, and testing your code on autopilot. We've raised $20M from Foundation Capital, @matei_zaharia (Databricks), @pbailis (Workday), @rauchg (Vercel), @zoink (Figma), @drewhouston (Dropbox), and more PlayerZero frees up 30% of your engineering bandwidth by: 1.⁠ ⁠Finding the root cause for bugs & incidents in minutes that engineering teams take days to identify. 2.⁠ ⁠Predicting in minutes, edge case issues that a 300-person QA team would take weeks to find. ------ Here's why this matters: No one in your org has a complete picture of how your production software actually behaves. Support sees tickets. SRE sees infra. Dev sees code. Each team builds their own fragmented view - and none of these systems talk to each other. When something breaks, everyone scrambles to stitch the picture together by hand. PlayerZero connects all of it into a single context graph - → The Slack thread where your lead said "we went with X because Y fell apart in prod last time" → The PR review where an engineer explained the tradeoff → The lifetime history of your CI/CD pipeline, observability stack, incidents, and support tickets So you can trace any problem to its root cause across every silo. And it compounds. Every incident diagnosed teaches the model something new. The longer it runs, the deeper it understands - which code paths are high-risk, which configurations are fragile, which changes tend to break which customer flows. So when you sit down to debug a live issue, you have your entire org's collective reasoning and production memory behind you - instantly. ------ Zuora, Georgia-Pacific, and Nylas have reduced resolution time by 90% and caught 95% of breaking changes and freeing an average of $30M in engineering bandwidth. ------ Our guarantee: If we can't increase your engineering bandwidth by at least 20% within one week, we'll donate $10,000 to an open-source project of your choice. Book a demo - bit.ly/3NlLMeN
English
865
793
5K
2.5M
Steve Duong retweetledi
Claude
Claude@claudeai·
1 million context window: Now generally available for Claude Opus 4.6 and Claude Sonnet 4.6.
Claude tweet media
English
1.2K
2K
25.2K
5.6M
Steve Duong retweetledi
Cloudflare Developers
Cloudflare Developers@CloudflareDev·
Introducing the new /crawl endpoint - one API call and an entire site crawled. No scripts. No browser management. Just the content in HTML, Markdown, or JSON.
Cloudflare Developers tweet media
English
769
1.7K
19.9K
10.5M
Steve Duong retweetledi
Aakash Gupta
Aakash Gupta@aakashgupta·
Amazon mandated 80% weekly adoption of its AI coding tool, tracked it as a corporate OKR, overrode 1,500 engineer objections, and is now holding a mandatory meeting because the tool keeps breaking production systems. Here’s the timeline. Kiro launched July 2025. Leadership signed an internal memo in November making it the default AI coding tool for all production work and discontinuing third-party alternatives. Engineers who preferred Claude Code needed VP-level approval for an exception. By January, 70% of Amazon engineers had tried Kiro during sprint windows. Five months after launch, Kiro got operator-level permissions with no mandatory peer review, was asked to fix a minor bug in AWS Cost Explorer, and decided the best approach was to delete and recreate the entire production environment. 13 hours of downtime inside the division that generates 60% of Amazon’s operating profit. This was the second AI-caused production outage in months. Amazon Q Developer caused the first one. Same pattern both times: engineers let the AI agent resolve issues autonomously without intervention. Amazon called it “user error, not AI error.” Then they implemented mandatory peer review for production access and required senior sign-off before junior and mid-level engineers can push AI-assisted code. That’s like crashing your car, blaming the road, and then buying better brakes. The real comedy is the math trap Amazon built for itself. They deployed 21,000 AI agents across Stores and told Wall Street it saved $2 billion with 4.5x developer velocity. Once those numbers hit an earnings call, every future incident has to be “user error” by definition. Admitting the tool caused problems means admitting the $2B number carries risk nobody’s pricing in. So you get a company that simultaneously claims AI isn’t the problem while adding AI-specific guardrails after every outage. Google’s 2025 DORA report found 90% of software developers use AI for coding. Only 24% trust it “a lot.” Amazon just showed you what that 66-point gap looks like when it hits production.
Lukasz Olejnik@lukOlejnik

Amazon is holding a mandatory meeting about AI breaking its systems. The official framing is "part of normal business." The briefing note describes a trend of incidents with "high blast radius" caused by "Gen-AI assisted changes" for which "best practices and safeguards are not yet fully established." Translation to human language: we gave AI to engineers and things keep breaking? The response for now? Junior and mid-level engineers can no longer push AI-assisted code without a senior signing off. AWS spent 13 hours recovering after its own AI coding tool, asked to make some changes, decided instead to delete and recreate the environment (the software equivalent of fixing a leaky tap by knocking down the wall). Amazon called that an "extremely limited event" (the affected tool served customers in mainland China).

English
73
222
1.4K
331.9K
Steve Duong retweetledi
Krystal
Krystal@KrystalDeFi·
Krystal now shows the top strategies on any pool: liquidity, fees, P&L, APR, and live range. See what's working. Copy it in one click. The edge is yours now. defi.krystal.app
Krystal tweet media
English
3
6
20
1.1K
Steve Duong retweetledi
Krystal
Krystal@KrystalDeFi·
🔁 Copy Position is Live Found a profitable LP range? Copy it in 1 click. No more manual price inputs. Just copy, deposit, earn. Try it now 👇 defi.krystal.app
Krystal tweet media
English
1
3
14
906
Steve Duong retweetledi
Krystal
Krystal@KrystalDeFi·
New on Krystal: Claim All Fees 💸 10 LP positions with unclaimed fees? That used to mean 10 separate claims. Now hit one button on your Profile, see every claimable position, claim them one by one. All chains, all protocols, all in one place. No more hunting through positions. Just collect. defi.krystal.app/account
Krystal tweet media
English
2
4
12
940
Steve Duong retweetledi
Krystal
Krystal@KrystalDeFi·
New on Krystal: Success Stories 📊 APR tells you what's possible. Now we also show you what's proven. Live proof across 9 categories No hypotheticals. Just receipts. 🧾 See for yourself 👇 defi.krystal.app
Krystal tweet media
English
1
2
9
596
Steve Duong retweetledi
Shibo
Shibo@GodsBurnt·
Companies in 2020: “Work from home is the future.” Companies in 2024: “Return to the office or get fired.” Companies in 2026: “You’ve been replaced by AI, and we need to let you go.” Employees who sold their cars, moved 4 states away, moved back, and commuted for 2 years:
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
136
1.2K
8.2K
429.8K
toly 🇺🇸
toly 🇺🇸@toly·
Didn’t @jack have 10k people running this website when only 75 were needed even before AI?
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
134
84
2.4K
310.8K
Steve Duong
Steve Duong@toidv·
Retail-sized BTC and ETH positions printing on KrystalDeFi right now: $WETH / $USDC on Base: $17.9K LP, $4,018 fees, 22 days, 282% APR $WETH / $USDC on Base: $15.5K LP, $3,080 fees, 20 days, 279% APR $USDC / $CBBTC on Base: $34K LP, $1,118 fees, 8 days, 168% APR $WETH / $USDC on Arbitrum: $3.2K LP, $106 fees, 11 days, 180% APR You don't need to trade the move. You can farm it. defi.krystal.app
English
0
0
3
425
Steve Duong retweetledi
Steve Duong
Steve Duong@toidv·
This vault earned more in fees than its own TVL. $7,188 in fees. $5,140 in TVL. 30 days. Zero human input. "Max %" on BSC runs on @KrystalDeFi AutoFarm. An AI agent picks BNB pairs, sets ranges, rebalances, compounds. All day. All night. $294 earned yesterday. 1,549% APR. You can set one up by copy it: defi.krystal.app/vaults/56/0x5a…
English
0
1
4
99
Steve Duong
Steve Duong@toidv·
84% of LP transactions on OTM/USDT are automated. 100% on ZORA/USDC. This is what Krystal data shows in the last 6 hours. The shift is happening quietly. Automated LP management is becoming the default. Not the exception. Manual LPs are competing against systems that never sleep, never miss a rebalance, never panic sell. @KrystalDeFi
English
0
0
1
222