LA Wolves

@sterlingcrispin Using Claude 4.6 and it definitely consistently creates bugs. But it can also create/run test and eval plans that do seem to weed out a lot of the bugs it generates.

Claude 4.6 is a good programmer but writes insanely severe bugs constantly, it won't catch them all in audits, nor will other claudes You need codex 5.4 auditing every commit 4+ times. If you don't believe me, try it. I have an /auditcodex skill for it github.com/sterlingcrispi…

@ChrisO_wiki It's definitely giving 2022 vibes.

1/ A superpower invades a small island off the coast of an enemy nation. After a short bombardment, marines seize and hold the island. 126 days later, they stage a humiliating retreat under constant fire from the mainland. This is the story of Ukraine's Snake Island. ⬇️

@AKWilk LOL they’re just using it wrong mate.

You guys were right. Claude is amazing.

@avthar This is brilliant, regardless of your AI skill set/level. I’ve been vibe coding, building agents/apps for sometime now. But even the beginner section had nuggets I wasn’t aware of. Thanks @avthar for doing this!

💥NEW AI CODING TUTORIAL: 12 Months of Claude Code Lessons in 46 Minutes Claude Code just turned 1. So here's 52 lessons on how to get the most out of Claude Code, organized into 3 levels: Beginner, Intermediate, and Master. TIMESTAMPS 00:00 12 Months of building with Claude Code 02:01 LEVEL 1: Beginner 02:09 Installation and Setup 04:55 Models and Modes 09:04 CLAUDE.md (and what to put in) 10:30 Context Management 11:31 Debugging with Claude 12:22 Version control 14:12 Prompting, Just ask Claude 16:01 LEVEL 2: Intermediate 16:24 Customizations (Skills, Plugins, MCPs) 24:42 Workflows: Plan, Build, Test 29:52 Verifying and Documenting with Claude 33:10 LEVEL 3: Master 34:17 Multi-Agent Development (multi-clauding with git worktrees) 37:07 Self-improving Systems 38:45 Ralph Wiggum Agent Loops 40:11 Async Task Delegation 42:00 Agent Teams, Pre-configure permissions, Hooks 44:42 Continue your learning

@heynavtoor Seeing exactly this since my team adopted AI. Productivity/output way up, stress/hours also way up.

🚨BREAKING: Berkeley researchers spent 8 months inside a tech company watching how employees actually use AI. The promise was simple: AI will save you time. Do less. Work smarter. The opposite happened. Workers didn't use AI to finish early and go home. They used it to take on more. More tasks. More projects. More hours. Nobody asked them to. They did it to themselves. The researchers sat inside the company two days a week for 8 months. They watched 200 employees in real time. They tracked work channels. They conducted 40+ interviews across engineering, product, design, and operations. Here's what they found. AI made everything feel faster, so people filled every gap. They sent prompts during lunch. Before meetings. Late at night. The natural stopping points in the workday disappeared. People ran multiple AI agents in the background while writing code, drafting documents, and sitting in meetings simultaneously. It felt like momentum. It felt productive. But when they stepped back, they described feeling stretched, busier, and completely unable to disconnect. 83% said AI increased their workload. Not decreased. Increased. 62% of associates and 61% of entry-level workers reported burnout. Only 38% of executives felt the same strain. The people doing the actual work absorbed the damage while leadership celebrated the productivity numbers. Then came the trap nobody saw coming. When one person uses AI to take on extra work, everyone else feels like they're falling behind. So the whole team speeds up. Nobody formally raises expectations. But the new pace quietly becomes the default. What AI made possible became what was expected. The researchers gave it a name: workload creep. It looks like productivity at first. Then it becomes the new baseline. Then it becomes burnout. AI was supposed to give you your time back. Instead it's eating more of it. And the worst part? You're doing it to yourself. Voluntarily.

@yieldsearcher Yup! The S&P is getting pinned HARD at that 675 level.

Is it just me or equity market is far less sensitive to VIX moves lately?

@toddsaunders Fun realization: a nights-and-weekends project I’m building would normally require ~521 hours of engineering time and roughly $500k at market rates. 🤯🤯 Instead it’s mostly been me, some cheap software subscriptions, and AI. Feels like cheating.

Fun command built in Claude Code: /cost-estimate It scans your codebase and cross-references current market rates to calculate what your project would've cost a real team to build. It looks at all the APIs, integrations, everything. Without AI: ~2.8 years. ~$650k. With AI: 30 hours. It's absurd when you start to think about it like this.

@Liathetrader The real question is why unsanctioned weekend wars should be an acceptable pastime.

I don't care about your political orientation, but if you're supporting the Islamic Republic and condemning actions that would help people in Iran—and also us in the Western world—you're out of your mind. Simple and plain.

@yieldsearcher You can and they will. But it’ll be numerator up / denominator at best

You know you can improve the metric with numerators too… funny no one thinks that way these days… Almost, dare I say, deflationary mindset.

WE’RE NOT THE WORST PREMIER LEAGUE TEAM IN HISTORY

@Wolves @wanderersnews1 And Andre still dances like someone’s mom. 🤣🤣 Great to see! #COYW!!!!

Enjoy. These. Moments.

@wolvesfancast The limbs!!!!!

Rodrigoal Goalmes Billy Wright Stand POV #wwfc

@aakashgupta Don't disagree. Claude Code is a amazing. And a lot of software engineers will turn their noses up at Cursor. But the additional software wrapper Cursor provides is still more attractive for less technical areas of the business, like analytics so cursor lives on (for now!)

Investors valued Cursor at $29 billion across three rounds in 12 months. That’s looking pretty suspect right now. Cursor went from $1M to $1B ARR faster than any SaaS company in history. The trip back down could be just as fast. An entire engineering team at Valon just canceled their Cursor seats in 7 minutes over Slack. 9:55 AM: one engineer asks to unsubscribe. 9:56 AM: done. 9:57 AM: “same.” 9:58 AM: “Cursor is so cooked my god.” 10:02 AM: “same I will never use.” No migration plan. No evaluation committee. No vendor review. One developer said “I don’t use this anymore” and the dominoes fell. Cursor pays Anthropic hundreds of millions a year for Claude model access. Anthropic took that revenue stream, studied exactly what developers wanted, and shipped Claude Code, which crossed $1B ARR within six months and is now past $2.5B, growing faster than Cursor ever did. The model provider looked at its biggest distribution partner and decided to eat them. Cursor has its own models for tab completion and autocomplete. But the heavy reasoning, the multi-file edits, the architectural decisions that make developers stay, that all runs on Claude. Claude Code delivers that same intelligence without the $20/month middleman. Microsoft, the company that sells GitHub Copilot, has widely adopted Claude Code internally across major engineering teams. Cursor’s upstream provider is outgrowing them. Their competitor’s parent company chose the upstream provider’s tool over their own. Both happening at once. The churn is going to be brutal. Enterprise seats look sticky in a spreadsheet until you watch a Slack channel where one cancellation triggers five more in 7 minutes. When your product is a layer between developers and the model they actually want, and the model ships its own interface, you’re selling a toll bridge on a road that just got a free lane. Accel, Thrive, a16z, NVIDIA, and Google all thought they were buying the next platform shift in developer tools. They may have bought the most expensive wrapper in SaaS history.

@market_sleuth Quality meme! Well played 😂

Those $SPY puts that some random person on X told you to buy yesterday ahead of $NVDA earnings. ☺️🔽

@sh4mrock1 Amen!!

Why do people always resort to racism? Call him a cunt or a wanker like a real man

The strength of the Wolf is in the pack. I stand with Tolu 🧡🖤🧡🖤🧡🖤 #kickitout #Wolves #notoracism

@premierleague 👏👏👏

We are appalled by the unacceptable online racist abuse targeted at Wolves’ Tolu Arokodare. There are serious consequences for anybody found guilty and we will offer the club and player our full support with investigations. Football is for everyone – there is no room for racism.

@chrysb @openclaw Yup would say so

unpopular (maybe?) opinion: MCP is dead in the water @openclaw has shown me that api & cli will win. every MCP server you connect loads its tool definitions into your context window. name, description, parameter schema, all of it. connect 10 servers with 5 tools each and you've burned 50 tool definitions worth of tokens before your conversation even starts. context bloat will never be a good thing - performance-wise or economically. i assume this is why @steipete left it out of @openclaw. the "exec" tool paired with on-demand skills is all you need. it can run any command invented since the beginning of computers. a resurgence of glory for ancient, but powerful tools like curl, sed, awk, grep. command line tools once mastered by the greats, but long forgotten and buried underneath abstractions developed for us lesser mortals. now available to us all, piloted by the smartest models on earth. every founder gets their own mass army of greybeards. the inertia required for MCP adoption, imo, is too great to overcome the momentum @openclaw has breathed into api + cli + skills. the common defenses people bring up: • "MCP gives you typed schemas and validation" — so does a well-documented CLI • "MCP gives you explicit permissions" — so does a sandbox with an allowlist • "MCP is a standard" — a standard that scales poorly is still a standard that scales poorly lastly, i've heard many MCP servers are just wrapping existing APIs - that kind of redundancy and unnecessary indirection should be a red flag. so, let's drop it and redirect our efforts into cli tools & apis with accompanying skills.

@molineuxmusings TBF Tchatchoua had a brilliant match defensively but offered nothing going forward. Would have given up the improved defense against a poor Palace team, if it meant more attacking impetus.

Rodrigo Gomes not starting again should tell a story. A proper in-between player who has an inflated reputation within the fanbase because of his enthusiasm. Tchatchoua starting ahead of him is quite damning.

@ConceptScouting @MLS @AppleTV MLS is shocking mate

First match of the @MLS season and the coverage from @AppleTV is absolutely shocking.