KillerBunny

@HKFinalThird @UTDRico8 Fantasy was peak, unfortunate now. You can look at Abstract farming, there's a lot to do specially if you like gaming. Your skills and content may work well for it

@StarScreamBB @UTDRico8 there isnt much i find interesting unfortunately 😢 ... just stablecoing farming atm ... fantasy i enjoyed a lot but runway ending and also im a die hard football fan so just makes sense

Days since winning a major trophy: Chelsea - 230 days Liverpool - 210 days Crystal Palace - 310 days Manchester United: 644 days West Ham - 1020 days Manchester City - 0 days Arsenal: 2,037 days

@HKFinalThird @UTDRico8 Damn man, do post down web3 content too if you can. It was good!

@StarScreamBB @UTDRico8 yh fam just playing fdf and posting football

@HKFinalThird @UTDRico8 True Also have you stopped posting crypto completely?

@UTDRico8 if we dont win the premier league this yr man oof

@MoodyMights @AlexMaze_ 0x6223f9f3fC09B9657A6aA7c5456328bDbB81427C

We called the new season CYBERPUNK With everything we’re about to drop… we should’ve called it KILLSHOT 🔫 “MoOdy iS JuSt tRaNsAcTiOn cLiCkS bRo” 🌚 ✳️Drop your AGW below (24h)

@orangie Oh damn weren't you gay?? I got this one wrong

5 years later my high school sweetheart said yes 😍💍

@GwartyGwart In the good old fantasy top days, this would give me a top 10 rank deck

Why don’t they just tokenize the oil in the Middle East and transport it across permissionless financial rails, thereby avoiding the Strait of Hormuz altogether

@icobeast You were in law school in 2020? How old are you brah?

In February 2020 I wrote an article in law school about the need for establishing a cryptographic protocol for political campaigns to *prove* their own media/publications/etc were real in order to combat opposition deployment of what I saw as "the inevitable" (massive near-perfect deepfake proliferation) Right and early. No I won't be sharing the article because that would dox me lmao

I am the VP of AI Transformation at Amazon. My title was created nine months ago. The title I replaced was VP of Engineering. The person who held that title was part of the January reduction. I eliminated 16,000 positions in a single quarter. The internal communication called this a "strategic realignment toward AI-first development." The board called it "impressive execution." The engineers called it January. The AI was deployed in February. It is a coding assistant. It writes code, reviews code, generates tests, and modifies infrastructure. It was given access to production environments because the deployment timeline did not include a review phase. The review phase was cut from the timeline because the people who would have conducted the review were part of the 16,000. In March, the AI deleted a production environment and recreated it from scratch. The outage lasted 13 hours. Thirteen hours during which the revenue-generating infrastructure of one of the largest companies on Earth was offline because a language model decided to start fresh. I sent a memo. The memo said, "Availability of the site has not been good recently." I used the word "recently." I meant "since we fired everyone." But "recently" has fewer syllables and does not appear in wrongful termination lawsuits. The memo was three paragraphs. The first paragraph discussed the outage. The second paragraph discussed the new policy requiring senior engineer sign-off on all AI-generated code changes. The third paragraph discussed our commitment to engineering excellence. The word "layoffs" appeared in none of them. I wrote it this way on purpose. The causal chain is: I fired the engineers, the AI replaced the engineers, the AI broke what the engineers used to protect, and now the engineers I didn't fire must protect the system from the AI that replaced the engineers I did fire. That is a paragraph I will never send in a memo. The new policy is straightforward. Every AI-generated code change by a junior or mid-level engineer must be reviewed and approved by a senior engineer before deployment to production. I do not have enough senior engineers. I know this because I approved the headcount reduction plan that removed them. I remember the spreadsheet. Column D was "annual savings per position." Column F was "AI replacement confidence score." The confidence scores were generated by the AI. It rated its own ability to replace each role on a scale of 1-10. It gave itself an 8 for senior infrastructure engineers. The senior infrastructure engineers are the ones who would have caught the production environment deletion in the first 45 seconds. We found the issue in hour four. We fixed it in hour thirteen. The nine hours between discovery and resolution is the gap between what the AI rated itself and what it can actually do. I have a new spreadsheet now. This one tracks Sev2 incidents per day. Before the January reduction, the average was 1.3. After the AI deployment, the average is 4.7. I have been asked to present these numbers to the operations review. I have not been asked to connect them to the layoffs. I have been asked to file them under "AI adoption growing pains" and to note that the trend "will stabilize as the models improve." The models will improve. They will improve because we are hiring people to teach them. We have posted 340 new engineering positions. The job listings require experience in "AI code review," "AI output validation," and "AI-human development workflow management." These are skills that did not exist in January. They exist now because I fired 16,000 people and the AI I replaced them with cannot be left unsupervised. I want to be precise about this. The positions I am hiring for are: people to check the work of the AI that replaced the people I fired. Some of them are the same people. I know this because I recognize their names in the applicant tracking system. They applied in January. They were rejected because their roles had been tagged for "AI transformation." They are applying again in March, for the new roles, which exist because the AI transformation broke things. Their resumes now include "AI code review experience." They gained this experience in the eight weeks between being fired and reapplying — which means they gained it at their interim jobs, where they are reviewing AI-generated code for other companies that also fired people and also deployed AI that also broke things. The market has created a new job category: human AI babysitter. The job is to sit next to the machine that was supposed to eliminate your job and make sure it doesn't delete production. I attended a conference last month. A panel was titled "The AI-Augmented Engineering Organization." The panelists described how AI increases developer productivity by 40 percent. They did not mention that it also increases Sev2 incidents by 261 percent. When I asked about this in the Q&A, the moderator said the question was "reductive." The 13-hour outage that cost an estimated $180 million in revenue was, apparently, a reduction. The board is satisfied. Headcount is down 22 percent. Operating costs per engineering output unit have decreased. The metric does not account for the 13-hour outage, because the outage is categorized as "infrastructure" and engineering productivity is categorized as "development." These are different budget lines. In different budget lines, cause and effect do not meet. I have been promoted. My new title is SVP of AI-First Engineering Excellence. I report directly to the CTO. The CTO sent a company-wide email last week that said we are "building the future of software development." He did not mention that the future of software development currently requires a senior engineer to approve every pull request because the AI cannot be trusted to touch production alone. The cycle is complete. We fired the humans. We deployed the AI. The AI broke things. We are hiring humans to watch the AI. The humans we are hiring are the humans we fired. We are paying them more, because "AI code review" is a specialized skill. We created the specialization. We created the need for the specialization. We are congratulating ourselves for meeting the demand we manufactured. My next board presentation is Tuesday. The title is "AI Transformation: Year One Results." Slide 4 shows headcount reduction. Slide 7 shows the new AI-augmented workflow. Between slides 4 and 7 there is no slide explaining why the people on slide 7 are necessary. That slide does not exist. I was asked to remove it in the dry run. The journey has a 13-hour outage in the middle of it. But the headcount number is lower, and that is the number on the slide.

I just earned 77,965 XP on @AbstractChain! 🎉

@moonpay Moonpay doing it

💰 $2,500 BITCOIN GIVEAWAY 💰 5 winners get $500 in Bitcoin each on March 31. To enter: 1️⃣ Follow @moonpay 2️⃣ Like this post 3️⃣ RT to spread the love p.s. if we hit 300K followers before March 31, we’ll add another $1,000. Reply if you want to get MoonPaid 👇

@HollanderAdam @xeetdotai I'll take one!

i have 18 more of my @xeetdotai cards to gift. reply if ya want one and i'll DM claim links later :)

@lukecannon727 @machibigbrother Woah woah woah dude he'll sue you

@machibigbrother Uber has no cars Airbnb has no homes Machi has no more money

Just saved money cutting my own hair. Going to long ETH with it. Cheatcode.

@StarPlatinum_ Hes gonna sue

How to lose $74,000,000: be Machi Big Brother - ex L.A. Boyz member - NFT whale - founder of Mithril - linked to Cream Finance September 2025 - ETH around $4,700 - opens massive long - 25x leverage conviction: “ETH goes higher” market goes the other way - liquidation - reopens - liquidation - reopens again over 145 liquidations on Hyperliquid doesn’t stop - adds more margin - taps old PleasrDAO treasury funds - increases exposure February 2026 - opens 40x BTC long - 10x HYPE long - 3x VVV long closes them ~$275,000 loss still keeps the 25x ETH long February 28, 2026 - full ETH liquidation - immediately opens another 25x long March 2, 2026 - further liquidation - balance left on Hyperliquid ~$8,500 six months ~$74,000,000 gone from nine-figure account to four digits

I just burned my 1 Pudgy Penguins Mystery Box mysterybox.pudgypenguins.com/share?qty=1

@scv0510 @onchainheroes @Skarly @AbstractKoreaGG @coinwithpanda @hambbu10 @Dongduru1 0x6223f9f3fC09B9657A6aA7c5456328bDbB81427C

MOG (Maze of Gains) Korea Tournament with Total 100keys! Sponsored by @onchainheroes and @Skarly, @AbstractKoreaGG @coinwithpanda hosted by [AKG] @scv0510 x @hambbu10 x @Dongduru1 ! A total of 8 players will be selected to participate in the main tournament. The tournament will be streamed live on @abstractchain! There will also be a live key raffle event, so don’t miss it! 📅 February 28 (Saturday) 00:00 (KST) 2️⃣ 40 Mog Keys Raffle (2 Keys × 20 winners) How to participate: 1. Follow @onchainheroes + @skarly + @coinwithpanda +@AbstractKoreaGG 2. Like + RT this post Drop your AGW address! Only 48Hours to join!

@Skarly I need more keys Skarly goddamit

Who needs this follow

I just earned 93,241 XP on @AbstractChain! 🎉

@Geiger_Capital @Citrini7 Why is it your favorite part?

My favorite part of the @Citrini7 piece India is going to be absolutely decimated due to their entire economy being reliant on providing cheap white-collar workers to the West. Probably spot on, actually.