it's 2026 and Microsoft needs to briefly throttle your machine into full power maximum performance mode to open the start menu without lag, sorry, with less lag, and they think this is something worth announcing to the press and public and giving it a name
The ultimate Counter-Strike showdown comes to the Lion City 🇸🇬
In 2027, we return to Singapore as 16 of the world’s top Counter-Strike teams will go head-to-head at the BLAST Premier Open!
📅 15–28 March 2027
📍 Singapore
👉 https://t.co/pJkjAjRVUr
#BLASTPremier
Microsoft spent 4 years stuffing Windows 11 with unwanted ads, forced Copilot integrations, and other bloatware, now they want applause for promising to remove it 😂 I guess Microslop & SlopOS social media shaming campaign is working out
JUST DROPPED: Anthropic's research proves AI coding tools are secretly making developers worse.
"AI use impairs conceptual understanding, code reading, and debugging without delivering significant efficiency gains." -- That's the paper's actual conclusion.
17% score drop learning new libraries with AI.
Sub-40% scores when AI wrote everything.
0 measurable speed improvement.
→ Prompting replaces thinking, not just typing
→ Comprehension gaps compound — you ship code you can't debug
→ The productivity illusion hides until something breaks in prod
Here's why this changes everything:
Speed metrics look fine on a dashboard.
Understanding gaps don't show up until a critical failur and when they do the whole team is lost.
Forcing AI adoption for "10x output" is a slow-burning technical debt nobody is measuring.
Full paper: https://t.co/JeRZr6up6P
41% of all code shipped in 2025 was AI-generated or AI-assisted. The defect rate on that code is 1.7x higher than human-written code. And a randomized controlled trial found that experienced developers using AI tools were actually 19% slower than developers working without them.
Devs have always written slop. The entire software industry is built on infrastructure designed to catch slop before it ships. Code review, linting, type checking, CI/CD pipelines, staging environments. All of it assumes one thing: the person who wrote the code can walk you through what it does when the reviewer asks.
That assumption held for 50 years. It broke in about 18 months.
When 41% of your codebase was generated by a machine and approved by a human who skimmed it because the tests passed, the review process becomes theater. The reviewer is checking code neither of them wrote. The linter catches syntax, not intent. The tests verify behavior, not understanding.
The old slop had an owner. Someone could explain why temp_fix_v3_FINAL existed, what edge case it handled, and what would break if you removed it. The new slop has an approver. Different relationship entirely.
Arvid’s right that devs wrote bad code before AI. The part he’s missing: the entire quality infrastructure of software engineering was designed around a world where the author and the debugger were the same person. That world ended last year and nothing has replaced it yet.
As 2026 rolls in & we approach the one-year anniversary of when Elon Musk did a full-on Nazi salute at a rally after Trump’s inauguration, let us remember he is the main reason why at least 600K people have died (2/3 were children) due to the gutting of USAID.
Fuck Elon Musk.
Blogged: Step Back
"Instead of trying harder, do the opposite. Take a break. Properly. Don't just switch to another screen to browse memes, graze cat pics, answer your email or catch up with notifications, messages and socials."
https://t.co/8Z2qazlkjZ