CWatt250

6.7K posts

CWatt250 banner
CWatt250

CWatt250

@C_Watt250

Katılım Ekim 2017
939 Takip Edilen1K Takipçiler
たかちん
たかちん@takachiiiiii3·
Beniくん予約購入した! かわいすぎる。早く同行させたい🥺
日本語
19
106
1.2K
207.4K
CWatt250
CWatt250@C_Watt250·
@krassenstein @AOC Did she show what it was before the data centers?? If not, then it’s here say
English
0
0
0
34
Brian Krassenstein
Brian Krassenstein@krassenstein·
SICKENING: AOC Just showed off the Georgia drinking water from Meta's AI Data Centers. Thank you @AOC: "This is the current drinking water in Morgan County, Georgia. Right after a data center was constructed, the metadata center was constructed, the only difference between the clean water and this was that data center. I have another one as well. So this wasn't just one well, these wasn't just one family's situation. This is what the drinking water now looks like next to that data center. And I think both of us can agree that neither one of these things are drinkable. These families now have to ship, in a rural area, have to ship water to their house in order to cook and bathe themselves."
English
2K
9.3K
26.2K
1.8M
CWatt250
CWatt250@C_Watt250·
@Teknium Just 8 hours? You make it sound like that is less than normal?!?
English
0
0
1
80
Teknium 🪽
Teknium 🪽@Teknium·
The amount of time it takes to review all the notifs from just 8 hours of sleep on here is getting a bit ridiculous lol
English
83
4
384
16.6K
CWatt250
CWatt250@C_Watt250·
@LeRobotHF Bro - where is the rest of his body?!?
English
1
0
1
222
LeRobot
LeRobot@LeRobotHF·
We built a bipedal robot for about $2,500. A real, mostly 3D-printed robot you can build, repair, simulate, train, and control. Today we’re releasing LeRobot Humanoid: an open robot-learning platform with hardware, runtime, identification tools, and training environments. Blog post: huggingface.co/blog/VirgileBa… Repo: github.com/Virgileboat/le…
English
32
180
1K
194.4K
Zeb Evans
Zeb Evans@DJ_CURFEW·
Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why. First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it. Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands. Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition. I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively. THE 100X ORGANIZATION The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago. Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken. The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems. These roles will evolve. But waiting for that to happen naturally means falling behind now. The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working. THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS — THE BUILDERS: 10X ENGINEERS I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality. Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment. AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down. Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed. So who do you want orchestrating and reviewing code? And how do you want your best engineers to spend their time? If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code. The new world is about enabling your 10x engineers to become 100x. The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated. I call this the great reckoning of AI coding, and every company will face this soon if not already. More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well. — THE BUILDERS: 10X PRODUCT MANAGERS Product management and design roles are merging. Designers that have customer focus, become more like product managers. And product managers that have intuition for UX become more like designers. The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results. The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy. Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on. To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production. Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck. That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time. — THE SYSTEM MANAGERS Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp. The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world. You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is. — THE FRONT-LINERS In a world that will become saturated with AI communication, the human touch will matter more than anything to customers. This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings. One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers. REWARDING 100X IMPACT In a world where companies are able to do so much more with less, where does that excess money go? In our case, much of the savings in this new operating model will flow directly back to those that enabled it. We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them. You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace. Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems. THE FUTURE Nearly every company will make changes like these. The ones that do it proactively will define what comes next. The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago. ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.
English
1.7K
3.6K
7.6K
9.1M
CWatt250
CWatt250@C_Watt250·
@AlexFinn He even used AI to write his post 😆
English
0
0
1
37
Alex Finn
Alex Finn@AlexFinn·
Another round of massive layoffs All CEOs using the same script of "We are dominating right now! But we must lay off 20% of the company." Despite the fact that this script is toxic and makes Americans hate AI, your takeaway should be this: If you have not mastered AI by now, you are completely useless in today's workforce and are waiting to be laid off You have 0 leverage and the clock is ticking Crying on blueski that the data centers are drinking all the water and AI is just capitalism slop machines is only digging your own grave AI is here. It will bring far sunnier day, but in the meantime it will bring massive disruption If you're not preparing for this now, you are filled with entitlement and only hurting you and your family And while I think many of these leaders are using AI as an excuse for their insane overspending in 2021 and not being prepared for market conditions (and you can now vibe code half these tools), the same takeaway should be had: learn all the tools available today including Codex, Claude Code, Hermes, OpenClaw, ChatGPT, Claude Design and others, or be doomed to being a statistic in a PR written tweet by your CEO on a Thursday afternoon
Zeb Evans@DJ_CURFEW

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why. First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it. Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands. Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition. I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively. THE 100X ORGANIZATION The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago. Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken. The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems. These roles will evolve. But waiting for that to happen naturally means falling behind now. The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working. THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS — THE BUILDERS: 10X ENGINEERS I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality. Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment. AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down. Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed. So who do you want orchestrating and reviewing code? And how do you want your best engineers to spend their time? If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code. The new world is about enabling your 10x engineers to become 100x. The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated. I call this the great reckoning of AI coding, and every company will face this soon if not already. More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well. — THE BUILDERS: 10X PRODUCT MANAGERS Product management and design roles are merging. Designers that have customer focus, become more like product managers. And product managers that have intuition for UX become more like designers. The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results. The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy. Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on. To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production. Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck. That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time. — THE SYSTEM MANAGERS Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp. The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world. You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is. — THE FRONT-LINERS In a world that will become saturated with AI communication, the human touch will matter more than anything to customers. This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings. One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers. REWARDING 100X IMPACT In a world where companies are able to do so much more with less, where does that excess money go? In our case, much of the savings in this new operating model will flow directly back to those that enabled it. We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them. You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace. Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems. THE FUTURE Nearly every company will make changes like these. The ones that do it proactively will define what comes next. The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago. ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

English
131
55
836
273K
Antonio Li
Antonio Li@AntonioSitongLi·
The Unitree G1 is smaller than I imagined
Antonio Li tweet media
English
1
0
4
306
CWatt250 retweetledi
Dude 3.0™
Dude 3.0™@NamelessDudeZA·
@kanavtwt Breaking: Jeffery Epstein has joined Anthropic
Dude 3.0™ tweet mediaDude 3.0™ tweet media
English
0
3
170
13.7K
Jun Song
Jun Song@jun_song·
I’m officially ambassador of @Alibaba_Qwen now! Thank you to all of my followers 😁
Jun Song tweet media
English
61
10
520
16.9K
CWatt250
CWatt250@C_Watt250·
@NeoAIForecast Wait we can run it with just the X premium subscription?!? I might have to run it.
English
0
0
1
80
Neo
Neo@NeoAIForecast·
I was close to buying Heavy for this, but the team pulled it off and we’re running hermes+xAI on my Premium+ subscription LFG!
Neo tweet media
English
8
1
41
1.8K
CWatt250
CWatt250@C_Watt250·
@HermesAgentTips Gemma 4 & Deepseek for me. I was having problems with ollama/ QWEN
English
1
0
1
225
Hermes Agent Tips
Hermes Agent Tips@HermesAgentTips·
Local LLM folks if you had to choose only one local model & you’re stuck with it for a month Which one would you pick? •Llama 4 Scout •Qwen 3.6 27B •DeepSeek-R1 •Gemma 4 •Mistral 7B •Phi-4
English
70
1
77
16.7K
CWatt250
CWatt250@C_Watt250·
@atomicbot_ai I’ve had both and I don’t believe these results in 2 seconds. 🤦‍♂️
English
1
0
4
409
atomicbot.ai
atomicbot.ai@atomicbot_ai·
Hermes Agent vs OpenClaw using Qwen 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations
English
79
50
697
599.3K
CWatt250
CWatt250@C_Watt250·
@LottoLabs I fully believe grok will win the ai race. Even starting way behind.
English
0
0
1
59
Lotto
Lotto@LottoLabs·
Idk why but I want grok to win the
English
13
0
38
1.7K
Teknium 🪽
Teknium 🪽@Teknium·
I dont love to gloat but we are almost 2x'ing openclaw just 3 days after surpassing their daily token volume 🤗
Teknium 🪽 tweet media
English
116
53
1.4K
91.3K
Todd Hanford
Todd Hanford@thanford7·
@chamath User error All you have to do is setup an agent swarm with: consolidator agent splitter agent analysis subagents deck generator agent
English
10
1
39
3.5K
Chamath Palihapitiya
Chamath Palihapitiya@chamath·
Use Claude they said. Upload your decks the said. Unleash all this productivity they said. But apparently, I first need to start a new chat, delete some of the deck and not exceed the maximum image count…just like my existing brain.
Chamath Palihapitiya tweet media
English
378
65
2.5K
378.1K