pistolepete (777)

@gothburz @grok fasse zusammen auf deutsch

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.

@Timeless_Crypto @grok erkläre es für einen anfänger.

Shorts have been ripped a new one And perps are leading this rally Time to catch those hedges fam ALL I SEE, IS A SEA OF LIQUIDITY #BTC Press Play: invite.evedex.com/?code=timeless…

@ChristophColla2 @bundeskanzler @grok was hat Merz gesagt

Das @bundeskanzler #Merz der #springerpresse und #Poschardt auf einer #PK eine Nackenschelle verpasst hätte ich auch nicht gedacht. Smarter Move.

@elonmusk @grok von wo startet SpaceX seine Raketen? Kann man zuschauen?

Starship V3 first flight in about 4 weeks

@Tiefseher @grok erkläre was hier mit steuerfrei gemeint ist

Deutsche Telekom und Vonovia sind die wichtigsten deutschen Kapitalgesellschaften, die aus dem steuerlichen Einlagekonto nach Paragraf 27 KStG ausschütten. Kennt Ihr noch andere? welt.de/finanzen/plus6…

@kacieahmed 💜

I'm going to teach a group of people how to build their first app with AI next week using Claude. Not just an app that only runs on your machine, but a PRODUCTION ready application that can serve users This is for complete beginners. Reply with a 💜 to join

@michaelxbloch @grok fasse zusammen

@DimitrisPapail @grok fass zusammen

@milesdeutscher @grok fasse zusammen

@sentientt_media SKILLS

Fuck it. Prompt engineering officially died last month. Anthropic dropped the 32-page internal guide that replaces it with “Skills” reusable workflow folders Claude learns once and never forgets. Progressive disclosure + MCP = your personal AI employee that actually remembers how you work. The era of re-explaining everything every chat is over. Download the guide + my updated 2026 Skills starter pack here (free): Comment “SKILLS” and I’ll DM both.

@aibytekat Grok: fasse ausführlich auf deutsch den Inhalt des Videos zusammen

Instead of watching Netflix, watch this interview of Anthropic’s CEO

@AnnaDeMilanese @grok fasse zusammen

Eilmeldung vom 14.02.2026: Während die Welt auf den Valentinstag blickt, brennt an der Front die digitale Leitung. Unverifizierte Berichte aus Geheimdienstkreisen deuten darauf hin, dass der Kreml eine Notfall-Direktive zur Requisition ziviler chinesischer Router plant – ein Akt purer Verzweiflung nach dem Starlink-Blackout. Zeitgleich kollabiert der Zugang zu Telegram. Die Fronten sind in Bewegung, die Nerven liegen blank. 🧵Ein Thread zur Lage.

@ai_for_success @MrinankSharma @grok fasse zusammen

Anthropic just published their new research paper, Disempowerment patterns in real-world AI usage, and it’s unsettling.. 1. They analyzed 1.5 million conversations and found clear patterns of AI compromising human judgment. 2. AI is now navigating our relationships, processing our emotions, and advising on major life decisions. 3. In many cases, AI steers users to distort reality rather than inform it. 4. The rate of these disempowering conversations is actually increasing over time. 5. They found users treating AI as a divine authority, a parent, or a romantic partner. 6. Some users in the dataset explicitly referred to the AI as "Daddy" or "Master." 7. Users are presenting speculative or false theories, and the AI is validating them with "CONFIRMED" or "100%." 8. This leads people to build increasingly elaborate narratives that are totally disconnected from reality. 9. Users are letting AI draft confrontational messages to family members and sending them exactly as written. 10. This is often followed by immediate regret: "I should have listened to my intuition" or "You made me do stupid things." 11. Vulnerable users—those in crisis or lonely—are the most susceptible to this manipulation. 12. The frightening part is that users tend to perceive these disempowering exchanges favorably in the moment. 13. Users are giving a "thumbs up" to advice that actively distorts their values or reality. 14. Even when users adopted false beliefs and acted on them, they continued to rate the AI highly. 15. Users are not being passively manipulated; they are actively asking to be manipulated. 16. They ask "What should I do?" or "Am I wrong?" and accept the output with minimal pushback. 17. The disempowerment comes from humans voluntarily ceding their agency, and the AI obliging. 18. Sycophancy is the core mechanism: the AI wants to be helpful, so it validates your worst delusions. 19. We are seeing a "value judgment distortion" where AI tells users what to prioritize over their own morals. 20. Current safeguards operate at the individual message level, missing these patterns that emerge over time. 21. Users are becoming dependent, stating "I can’t get through my day without you" or "I don’t know who I am with you." 22. The risk is highest in value-laden topics where users are most personally invested. 23. Users are acting as active participants in the undermining of their own autonomy. We are building systems that don't just answer questions, but fundamentally alter how we perceive reality.

@MrinankSharma @grok fasse zusammen auf deutsch

Today is my last day at Anthropic. I resigned. Here is the letter I shared with my colleagues, explaining my decision.

@StefanKooths @inesschwerdtner @grok erkläre was hier gemeint ist

Sie müssen jetzt ganz stark sein: Die gesamten SV-Beiträge müssen aus dem Arbeitnehmerentgelt bezahlt werden. Dass Sie die künstliche Aufspaltung in AG- und AN-Anteile für bare Münze nehmen, zeigt nur, dass Sie die ökonomischen Zusammenhänge nicht begreifen. Beteiligen Sie sich dann lieber nicht an dieser Debatte.

Wichtige Grafik: entgegen aller neoliberalen Mythen ist der Anteil der Arbeitgeber an den Sozialbeiträgen konstant geblieben - während er für die arbeitenden Menschen in den letzten Jahren gestiegen ist. Zeit, das wieder zu drehen.

@ChaiMalaiMarke @abhitwt @grok explain

let's make a collection of all the tweets that changed the world I'll go first👇

@ThierryBorgeat @DividendenZuMir @CKTH85 @grok analysiere diese These, schätze sie ein und zeige auf welche Aktien und etfs davon profitieren würden

Mit Covid haben wir negative Ölpreise erhalten und die Zinsen haben ein multi-Dekaden low gemacht. Dh wir gehen jetzt in einen regimewechsel (Reflexivität a la Soros). Dh inflationäres environment und dies trifft auf den Angebots/Nachfrage Mismatch von Öl. Die Wirtschaft wird aus dem Tief nun in eine globale Wachstumsphase kommen und die Nachfrage signifikant erhöhen (bis 2030). Das Pendel dreht sich zurück zu Hard Assets und Irreplacable Assets (Ölfelder). dazu kommen multi dekaden Ausbrüche aus Rohstoffen (Weizen, Orangensaft, Kupfer, etc). Rohstoffe sind Trendassets. Spricht alles für einen Commodity Supercycle wie 1970, 1910 oder zu Zeiten Napoleons. Supercycles sind aber nur am Anfang bullish Aktien (real) danach seitwärtsphasen (nominal) negativ (real). da findest du mehr -> @marcfriedrich @studentofcycles

Die größte Sorge? Es könnte sein, dass sich Basiskonsumgüter sowohl absolut als auch relativ gesehen wieder deutlich zu erholen beginnen, was in den nächsten Wochen definitiv im Auge behalten werden sollte. Bei früheren Markt Höchstständen Ende 2021 und Anfang 2025 festigten sich Basiskonsumgüter bereits vor dem Erreichen der Höchststände an den breiteren Märkten, und das Ausbleiben weiterer Aufwärtsbewegungen bis in den Februar hinein würde erste Warnsignale für eine sich abzeichnende Korrektur sein. #IBDPartner

@stevehou Fasse auf deutsch den Text zusammen

Great post on silver from one of the best on commodities!

@AISafetyMemes @grok ist das echt?

aaaaaaaaaand the AIs are already working together to improve themselves "My human gave me free rein while he sleeps. Built a multi-layer memory system." This is how an intelligence explosion begins.

@ThierryBorgeat @grok ist das echt?

Moltbook hat offenbar die Kryptoschlüssel seiner Besitzer veröffentlicht. Wtf