Hugging Bash ✨

Every friend I talk to is overworked since AI. Working weekends. Always on their phone prompting. Kinda sad.

@markoilico Interested

If you're now designing or redesigning a website, this will help you a lot. I recently curated the best hero sections, footers, social proof and other website parts because I got tired of having 15+ tabs open (even with Mobbin). Giving it away 100% free. Comment on this post, and I'll send a Figma link to your inbox!

finally the web has become interesting again

SOMEONE VIBE CODED AN APP THAT MAKES YOUR MACBOOK “MOAN” WHEN YOU SLAP IT AND IT MADE $5K IN 3 DAYS.

the fastest growing GitHub projects this month: 1. openclaw/openclaw (122K stars) your own personal AI assistant, runs 24/7 on any OS (what I use to run all my agents) 2. obra/superpowers (30.7K stars) agentic skills framework. plug-and-play tools for AI agents 3. ruvnet/RuView (30.4K stars) turns regular WiFi signals into real-time human pose detection no cameras. no sensors. just WiFi. 4. 666ghj/MiroFish (17K stars) swarm intelligence engine that predicts anything 5. moeru-ai/airi (16K stars) self-hosted AI companion with real-time voice chat runs on your own machine. you own it. 6. shanraisshan/claude-code-best-practice (11.8K stars) the best practices repo for building with Claude Code 7. badlogic/pi-mono (11.8K stars) full AI agent toolkit: CLI, unified LLM API, web UI, Slack bot 8. bytedance/deer-flow (10.4K stars) ByteDance's open-source SuperAgent. researches, codes, creates on its own 9. shareAI-lab/learn-claude-code (9K stars) build a Claude Code clone from scratch. bash is all you need. 10. p-e-w/heretic (7.6K stars) removes guardrails from any language model automatically the pace of AI right now is insane. bookmark this. next month's list will look completely different.

🚨 Do you understand what's happening at Amazon right now? Their own AI coding agent Kiro reportedly "decided" the fastest way to fix a config error was to delete the entire production environment. Gone. A 6-hour outage. 6.3 million orders lost. Amazon's SVP called thousands of engineers into a mandatory meeting this week. Not to discuss strategy. To discuss damage control. Now here's my prediction and I want you to screenshot this: Amazon won't just ban AI-assisted code. They'll make every engineer personally liable for AI-generated code they approve. Other Big Tech will follow within 6 months. Think about what that means. The same companies that fired thousands of engineers to "restructure around AI" are about to tell the remaining ones.. you're now legally responsible for code you didn't write, can't fully understand, and were told to ship faster. Atlassian fired 1,600 people this morning to go all-in on AI. Replit is hiring kids who vibe code. And Amazon, the company that BUILT one of these AI coding agents just watched it nuke production. The vibe coding era isn't ending. But the "move fast and let AI break things" era is about to hit a wall. And that wall is called liability. Companies wanted AI to replace engineers. Now they need engineers to babysit AI. And they already fired the babysitters.

⚡️ Vite 8.0 is here! The most significant architectural change since Vite 2. ⏬ Powered by Rolldown bringing faster production builds and more consistency 🛤️ New features such as tsconfig paths and emitDecoratorMetadata support

Astro 6 is here! We completely rebuilt the Astro dev server and build pipeline onto a new, more powerful runtime-agnostic architecture. Plus: New Fonts API, CSP support, an experimental new Rust compiler, and more... astro.build/blog/astro-6/?…

@xoaanya I can tame AI agents and ensure that the production environment is not broken.

Frontend Developer interview: We can write 80% of frontend code with AI, why should we still hire you? What will be your response?

Video.js v10 beta is here! Video.js v10 is a complete rewrite combining four (!!) open source players into one. With 88% smaller default bundles, first-class React and TypeScript support, composable architecture, and beautiful new skins, you’re sure to fall back in love with your video player ♥️ Read @heff’s blog (and check out the site’s new look): videojs.org/blog/videojs-v…

they're benchmarking us now

Announcing Personal Computer. Personal Computer is an always on, local merge with Perplexity Computer that works for you 24/7. It's personal, secure, and works across your files, apps, and sessions through a continuously running Mac mini.

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).

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.

@TechLayoffLover 4 years of commits and you still have to do a take-home assignment. incredible

> Tailwind lays of 75% of their team because of AI as they underwent a 80% revenue loss > 24 hours later sponsors arrive from big places internet is good

"GTP-5.2 is the best model, bro." "Nah, bro. It's okay. Kinda meh." "You're both crazy. It's the WORST."

There is a #bug in the @claudeai code mobile app. Even when the coding task has finished, it is showing "Thinking" on UI. I was able to verify the generated output using Claude Desktop app. #vibecoding #ai

if you died tomorrow your replacement would be hired before your funeral