One Love

#ShoutForFloyd ‘justice for floyd... justice for floyd... ‘ Do you share the idea ? retweet

[LearnKube @learnk8s]

Luxury Yacht is a cross-platform desktop app for managing Kubernetes clusters, available for Linux, macOS, and Windows, built with Go and Wails

➜ https://t.co/atgDmmUFwu

[Roan @RohOnChain]

https://t.co/h2Ea2y97ZS

[0xMarioNawfal @RoundtableSpace]

A CHINESE STUDENT STARTED TRADING 2 DAYS AGO WITH $0.90 AND TURNED IT INTO $408,292.

Someone reverse engineered his bot in 20 minutes with one Claude prompt. It doesn't predict the market. It exploits the latency.

[Vaishnavi @_vmlops]

Someone wrote a 680 page interactive book on cs algorithms

and every single concept has a live visualizer you can pause, rewind & mess with

no static diagrams...no passive reading...you actually see the algorithm think

embedded python, code playback, 100+ solved problems, complexity analysis all in one app

https://t.co/MGosgpqI8V

[Kawsar @Kawsar_Ai]

🚨 BREAKING: Google Gemini can now analyze any stock like a Wall Street analyst (for free).

Here are 09 insane Gemini prompts that replace $4,000/month Bloomberg terminals:

Save for later🔖

[FinRadar.ai @StuckInStock]

See where the smart money flows.

- Track ANY fund's 13F filings
- Create up to 10 custom fund baskets (Tech, biotech...)
- Screen across ALL funds collectively

The ONLY all-in-one institutional flow tracker.

Built for serious investors.

Try free See where the smart money flows.

- Track ANY fund's 13F filings
- Create up to 10 custom fund baskets (Tech, biotech...)
- Screen across ALL funds collectively

The ONLY all-in-one institutional flow tracker.

Built for serious investors.

Try free See where the smart money flows.

- Track ANY fund's 13F filings
- Create up to 10 custom fund baskets (Tech, biotech...)
- Screen across ALL funds collectively

The ONLY all-in-one institutional flow tracker.

Built for serious investors.

Try free →

[Abhishek Tiwari @baanditeagle]

@Fried_rice Drafted a detailed list of all Hidden and unreleased features! Hail Opus!!
Claude Code — Hidden & Unreleased Features
https://t.co/5NfbGTOk9m
https://t.co/UUJun8rzxt

[Shruti @heyshrutimishra]

Anthropic leaked 512,000 lines of Claude Code source code yesterday.

What happened in the next 12 hours is absolutely wild.

4 AM. Anthropic pushes an update to npm. Inside the package: their entire codebase. A 60 MB debugging file accidentally bundled in.

23 minutes later, researcher Chaofan Shou spots it. Downloads the zip.

Posts it on X. Within 6 hours: 3 million views.

By the time Anthropic’s team woke up, the code was forked 41,000+ times across GitHub. Anthropic started firing DMCA takedowns. Too late.

A Korean developer named Sigrid Jin woke up to his phone exploding. He’s Claude Code’s biggest power user.

WSJ reported he burned through 25 billion tokens last year.

He read the leaked code.

Rewrote the entire thing in Python in 8 hours. His repo hit 30,000 stars faster than any GitHub project in history.

Then he rewrote it again in Rust. That version now has 49,000 stars.

Someone mirrored it to a decentralized platform with one message: “will never be taken down.” The code is permanent. Anthropic cannot get it back.

Here’s the part I can’t stop thinking about: Anthropic built something called “Undercover Mode.” Its only job: prevent Claude from accidentally leaking internal secrets.

They shipped an entire anti-leak system in their own product. Then leaked their own source code in a .map file. Irony is beautiful

[Hedgie @HedgieMarkets]

🦔 Oracle laid off between 20,000 and 30,000 employees Tuesday morning, roughly 18% of its global workforce, via a single email sent at 6am EST with no prior warning. System access was revoked almost immediately after. The cuts are expected to free up $8-10 billion in cash flow. Oracle's stock has lost more than half its value since September 2025 and the company now carries over $124 billion in debt, up from $89 billion a year ago, with free cash flow running negative $10 billion last quarter.

My Take
Oracle posted a 95% jump in net income last quarter and still eliminated 18% of its workforce by email before most people finished their morning coffee. This is not a company in distress in the traditional sense. It's a company that made an enormous debt-funded bet on AI infrastructure and is now converting its workforce into cash flow to service that debt.

We've covered Oracle's AI gamble for months. The $300 billion OpenAI deal through Stargate, $50 billion in capital expenditure this fiscal year, over $124 billion in total debt. Multiple US banks have pulled back from financing Oracle-linked data center projects. Bondholders have sued Oracle claiming it concealed how much additional debt the OpenAI deal would require. The credit default swap spread hit a three-year high earlier this year, meaning debt investors are genuinely nervous about getting paid back.

The workers who got that 6am email built the products Oracle has monetized for decades. The bet that eliminated their jobs was made by people who were already paid regardless of how it turns out. That is the part of the AI infrastructure race that doesn't show up in the capex announcements.

Hedgie🤗

[Alvaro Cintas @dr_cintas]

This is the most complete Claude Code setup that exists right now.
27 agents. 64 skills. 33 commands. All open source.

The Anthropic hackathon winner open-sourced his entire system, refined over 10 months of building real products.

What's inside:
→ 27 agents (plan, review, fix builds, security audits)
→ 64 skills (TDD, token optimization, memory persistence)
→ 33 commands (/plan, /tdd, /security-scan, /refactor-clean)
→ AgentShield: 1,282 security tests, 98% coverage

60% documented cost reduction.

Works on Claude Code, Cursor, OpenCode, Codex CLI. 100% open source.

[Claude @claudeai]

New in Claude Code: auto mode.

Instead of approving every file write and bash command, or skipping permissions entirely, auto mode lets Claude make permission decisions on your behalf.

Safeguards check each action before it runs.

[The Code Newsletter @CodeNewsletter]

The founder of Claude Code just dropped his team's entire workflow.

His 10-step setup is worth trying.

Sign up for The Code newsletter for more

[shirish @shiri_shh]

Palantir AI + Claude was used to detect, prioritize, and strike over 1,000 targets in the first 24 hours of Operation against IRAN.

The success was so ridiculous, so game-changing, that the Pentagon didn’t even wait.

What used to be just a pilot project, just something they were testing out… suddenly became official, permanent, and everywhere.

Palantir is now the core AI brain of the entire U.S. military. It’s getting rolled out across ALL branches.

[Interstellar @InterstellarUAP]

🚨 Simulation Theory: The Double Slit Experiment proves particles act like waves until observed then they snap into particles.

What if our reality only "renders" when we're looking, just like a video game optimizing resources?

Check out this episode from The Why Files breaking it down, tying it to Simulation Theory. Are we in a sim?

This could be the key to unlocking the true nature of existence!

The Why Files video did a great job on explaining the Double Slit Experiment & Simulation Theory

What do YOU think—real or rendered? Drop your thoughts below!

[Google Labs @GoogleLabs]

Introducing the new @stitchbygoogle, Google’s vibe design platform that transforms natural language into high-fidelity designs in one seamless flow.

🎨Create with a smarter design agent: Describe a new business concept or app vision and see it take shape on an AI-native canvas.
⚡️ Iterate quickly: Stitch screens together into interactive prototypes and manage your brand with a portable design system.
🎤 Collaborate with voice: Use hands-free voice interactions to update layouts and explore new variations in real-time.

Try it now (Age 18+ only. Currently available in English and in countries where Gemini is supported.) → https://t.co/pmT9iHEpZa

[The Nobel Prize @NobelPrize]

“Timing is very important. You need to pick hard problems to solve and be ambitious with them. But you've also got to pick the right time when the world and the context that you're in is the right kind of environment for those ideas to flourish.”

In his official Nobel Prize interview, Demis Hassabis discussed how his aspirations as a young gaming programmer were ahead of their time.

Watch our official interview: https://t.co/2ovRqsSAtc

[Utkarsh Sharma @techxutkarsh]

Instead of watching a 2-hour movie, watch this Claude FULL COURSE (Build & Automate Anything):

[Shruti @heyshrutimishra]

BREAKING: Perplexity just killed your entire software stack.

Yesterday they announced Personal Computer.

It runs 24/7 on a Mac mini, controls your local files, and replaces tools that cost $100K+/year.

[Peter Girnus 🦅 @gothburz]

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.