Roberto Carlos Navas

6K posts

Roberto Carlos Navas banner
Roberto Carlos Navas

Roberto Carlos Navas

@rcnavas

I've seen things you people wouldn't believe ... All those moments will be lost in time, like tears in rain.

El Salvador Katılım Kasım 2008
2.6K Takip Edilen3K Takipçiler
Sabitlenmiş Tweet
Roberto Carlos Navas
Roberto Carlos Navas@rcnavas·
Lo intente, pero Dios sabe lo que hace.
Roberto Carlos Navas tweet mediaRoberto Carlos Navas tweet media
Español
250
373
1.5K
0
Roberto Carlos Navas
Controversial, pero esto es lo que ya esta pasando en muchas empresas: adoptan AI para ser más productivos, luego el personal que no logra ser 10x más productivo con AI o se reúsa a automatizar su trabajo con AI, es la primera que se recorta.
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.

Español
0
0
0
31
Roberto Carlos Navas retweetledi
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.6K
1.1K
12.3K
8.4M
Roberto Carlos Navas retweetledi
Bryan Johnson
Bryan Johnson@bryan_johnson·
Sending good energy your way. That you'll have the strength to overcome what ails you. The tenacity to achieve what you dream of. The inner calm to forgive those who have wronged you. The strength to be kind to others. And the insanity to dream without care of what others say.
English
245
389
4.6K
140.6K
Roberto Carlos Navas retweetledi
Brivael Le Pogam
Brivael Le Pogam@brivael·
Tu confonds deux choses, et c'est exactement le piège que la French Theory a tendu. Liberté, égalité, fraternité — égalité *de droits*, égalité *devant la loi*, égalité *de dignité*. C'est la promesse républicaine, et personne ici ne l'attaque. Le wokisme, ce n'est pas ça. C'est l'égalitarisme des résultats. Et l'égalitarisme des résultats, contrairement à l'égalité des droits, n'est pas un élargissement de la liberté — c'est sa négation. Quelques exemples concrets : — San Francisco supprime les classes de maths avancées au collège pour "réduire les inégalités". Résultat : les écarts entre élèves explosent, les familles aisées prennent des cours privés, les pauvres se font enterrer. L'égalitarisme a creusé l'inégalité. — Les politiques de discrimination positive à Harvard : étudiants admis avec des scores très en dessous de leurs camarades, taux d'échec dispropportionné, sentiment d'imposture, ressentiment généralisé. On a saboté ceux qu'on voulait aider. — L'aide humanitaire qui distribue du riz gratuit pendant 30 ans en Afrique : effondrement des filières agricoles locales, dépendance institutionnalisée. Donner un poisson, c'est empêcher d'apprendre à pêcher. Le wokisme ne détruit pas l'humanité dans le sens dramatique. Il fait pire : il dessert systématiquement ceux qu'il prétend protéger, et il génère du ressentiment des deux côtés — ceux qu'on infantilise et ceux qu'on culpabilise. La fraternité républicaine dit : tu es mon égal, donc je te traite en adulte capable. Le wokisme dit : tu es ma victime, donc je dois te protéger de toi-même. L'un élève. L'autre infantilise. Ce n'est pas la même chose, et confondre les deux est exactement le tour de passe-passe qu'on dénonce.
Eduardo Suarez@EduardoSuarez25

@brivael Francia exporta libertad, igualdad y fraternidad desde hace 237 años. Quienes invocan el "wokismo" como destrucción de la humanidad simplemente reflejan su falta de respeto de la identidad ajena, y su necedad de valores, mientras piden respeto a sus ideas niegan las de los demás.

Français
1.1K
8.4K
33.9K
55.5M
Roberto Carlos Navas retweetledi
Elon Musk
Elon Musk@elonmusk·
ZXX
5.9K
11.4K
99.4K
86.9M
Roberto Carlos Navas retweetledi
The Hacker News
The Hacker News@TheHackersNews·
🚨 WARNING: The self-spreading “Mini Shai-Hulud” worm compromised npm & PyPI packages tied to TanStack, Mistral AI, Guardrails AI, OpenSearch & more. The attack used GitHub OIDC token hijacking and cache poisoning to spread credential-stealing malware across 42 TanStack packages and 84 versions. Check your dependencies immediately → thehackernews.com/2026/05/mini-s…
The Hacker News tweet media
English
28
210
610
95.5K
Roberto Carlos Navas retweetledi
International Cyber Digest
International Cyber Digest@IntCyberDigest·
‼️🚨 UPDATE: The TanStack npm attack is now a full campaign. 'Mini' Shai-Hulud has hit: - OpenSearch - Mistral AI - Guardrails AI -UiPath - Squawk packages across npm and PyPI The malware specifically targets AI developer tooling. It hooks into Claude Code (.claude/settings.json) and VS Code (.vscode/tasks.json) to re-execute on every tool event, long after the infected package is gone. npm uninstall does not fix this.
International Cyber Digest@IntCyberDigest

‼️🚨 BREAKING: A new npm supply-chain attack uses a dead-man's switch. The payload plants a watcher on your machine that nukes your home directory the second you revoke the GitHub token it stole from you. The compromise happened today, across 42 official tanstack npm packages, 84 malicious versions in total. tanstack/react-router alone pulls more than 12 million weekly downloads. The attacker forked TanStack's repository and pushed a single hidden commit. From there, they tricked TanStack's own release system into signing the malicious packages as if they were the real thing. To npm, and to anyone checking the cryptographic proof of origin (SLSA provenance), the poisoned versions looked 100% legitimate. Maintainer Tanner Linsley confirmed the whole team had 2FA enabled. It didn't matter. This is the first documented npm worm in history that ships with a valid, signed certificate of authenticity, the same one defenders rely on to know a package wasn't tampered with.

English
129
744
4K
2.7M
Roberto Carlos Navas retweetledi
Three.js
Three.js@threejs·
> Hey Gemini, would Jesus agree with this take? Based on the New Testament, here is how that take might be measured: 1. Utility vs. Pretense A core theme in Jesus' teachings was the rejection of unnecessary complexity and religious "gatekeeping." He often criticized the Pharisees for focusing on the minute details of the law (the "C++ from scratch" equivalent of the time) while missing the weightier matters of justice and mercy. The Three.js Perspective: If the goal is to create something beautiful or helpful for others, Jesus would likely favor the tool that makes that possible most effectively. Using a library to help people is more in line with his "fruit of the tree" philosophy (Matthew 7:17) than building the tool itself just for the sake of technical purity. 2. Humility and "Vibe" The tweet calls the obsession "stupid" and promotes a more rigorous path. The Teachings: Jesus frequently championed the "poor in spirit" and the simple-hearted. He likely wouldn't care for the elitism inherent in the "just use C++" argument. He tended to use simple parables—the "Three.js" of storytelling—rather than the dense academic or legalistic language of the era's scholars. 3. The "Stewardship" of Time The tweet suggests that AI models are "more than capable" of handling the harder path. The Parable of the Talents: This teaching emphasizes using what you have to create value. If building an engine from scratch takes years and yields no "fruit," while using Three.js allows you to build ten helpful applications in the same time, the latter could be argued as better stewardship of one's life and talents. 4. The "Foundation" Argument Jesus did have a famous take on foundations (the house built on the rock vs. the sand). The Counter-Argument: A purist might argue that C++ is the "rock" and Three.js is a layer of "sand." However, in a theological context, the "foundation" is the intent and the heart, not the complexity of the masonry. The Verdict: It is highly unlikely he would agree. The "vibe coder" using a library to bring an idea to life aligns more closely with the ethos of accessibility and "letting your light shine" than the gatekeeping of technical elitism. He’d probably tell the original poster that the Sabbath (and the engine) was made for man, not man for the engine.
English
13
4
95
7.5K
Roberto Carlos Navas retweetledi
Claude
Claude@claudeai·
We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity. This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.
English
4.8K
12.1K
131K
23.9M
Roberto Carlos Navas retweetledi
Unity for Games
Unity for Games@unitygames·
Unity AI is now in Open Beta 🎉💫 We believe AI has the most impact when it helps creators move faster while staying in control of the creative process. Use our built-in agent tuned for Unity workflows or connect the AI tools you prefer via AI Gateway and MCP Server.
English
357
590
5.5K
2.5M
Roberto Carlos Navas retweetledi
NOX Corp
NOX Corp@NOXCorpAI·
Being human is no longer enough. Prove you are still useful. Start at noxcorp.io and Apply for human positions
English
2
4
8
674
Roberto Carlos Navas retweetledi
OLA Guild Games
OLA Guild Games@OLAGuildGames·
🚨 OLA en @gamescomlatam 🚨 Vamos a estar presentes llevando lo mejor del gaming Web3, conectando con la comunidad y mostrando lo que se viene 👀 📅 30 de Abril al 3 de Mayo 📌 Distrito Anhembi, São Paulo 🔥 Prepárense para novedades, contenido y mucho más 😏
OLA Guild Games tweet media
Español
4
3
17
647
Roberto Carlos Navas
Roberto Carlos Navas@rcnavas·
Cursor sabía que con su modelo Composer 2 —que dicen es Kimi 2.5 open source— no iba a competir con Anthropic Claude o OpenAI Codex
SpaceX@SpaceX

SpaceXAI and @cursor_ai are now working closely together to create the world’s best coding and knowledge work AI. The combination of Cursor’s leading product and distribution to expert software engineers with SpaceX’s million H100 equivalent Colossus training supercomputer will allow us to build the world’s most useful models. Cursor has also given SpaceX the right to acquire Cursor later this year for $60 billion or pay $10 billion for our work together.

Español
0
0
0
118
Roberto Carlos Navas retweetledi
Qwen
Qwen@Alibaba_Qwen·
🚀 Introducing Qwen3.6-Max-Preview, an early preview of our next flagship model Highlights: ⚡️ Improved agentic coding capability over Qwen3.6-Plus 📖 Stronger world knowledge and instruction following 🌍 Improved real-world agent and knowledge reliability performance Smarter, sharper, still evolving. More Qwen3.6 models to come. Stay tuned! 🔗👇 Blog: qwen.ai/blog?id=qwen3.… Qwen Studio: chat.qwen.ai/?models=qwen3.… API: modelstudio.console.alibabacloud.com/ap-southeast-1…
Qwen tweet media
English
174
444
4.2K
346.3K
Roberto Carlos Navas retweetledi
Kimi.ai
Kimi.ai@Kimi_Moonshot·
Meet Kimi K2.6: Advancing Open-Source Coding 🔹Open-source SOTA on HLE w/ tools (54.0), SWE-Bench Pro (58.6), SWE-bench Multilingual (76.7), BrowseComp (83.2), Toolathlon (50.0), Charxiv w/ python(86.7), Math Vision w/ python (93.2) What's new: 🔹Long-horizon coding - 4,000+ tool calls, over 12 hours of continuous execution, with generalization across languages (Rust, Go, Python) and tasks (frontend, devops, perf optimization). 🔹Motion-rich frontend - Videos in hero sections, WebGL shaders, GSAP + Framer Motion, Three.js 3D. 🔹Agent Swarms, elevated - 300 parallel sub-agents × 4,000 steps per run (up from K2.5's 100 / 1,500). One prompt, 100+ files. 🔹Proactive Agents - K2.6 model powers OpenClaw, Hermes Agent, etc for 24/7 autonomous ops. 🔹Claw Groups (research preview) - bring your own agents, command your friends', bots & humans in the loop. - K2.6 is now live on kimi.com in chat mode and agent mode. For production-grade coding, pair K2.6 with Kimi Code: kimi.com/code - 🔗 API: platform.moonshot.ai 🔗 Tech blog: kimi.com/blog/kimi-k2-6 🔗 Weights & code: huggingface.co/moonshotai/Kim…
Kimi.ai tweet media
English
933
2.4K
18.2K
7.5M
Roberto Carlos Navas retweetledi
Polymarket
Polymarket@Polymarket·
BREAKING: Vibe-coding platform Lovable reportedly suffered a breach that exposed users’ AI chat histories, source code, & database credentials.
English
573
910
8.4K
2.1M
Roberto Carlos Navas retweetledi
VECERT Analyzer
VECERT Analyzer@VECERTRadar·
🚨 NATIONAL SECURITY ALERT: CRITICAL COMPROMISE OF CLARO EL SALVADOR (200 GB EXFILTERED) 🇸🇻🇨🇭 The hacktivist group Anonymous Switzerland has announced a successful intrusion into the internal network of Claro El Salvador, the country's largest telecommunications provider. The attack is attributed to geopolitical motivations and ideological retaliation. 🏢 Affected Entity: Claro El Salvador (América Móvil) 🇸🇻 👤 Threat Actor: Anonymous Switzerland 🇨🇭 📂 Leak Volume: 200 GB of total data stolen. 📊 Compromised Data: The group has begun publishing a 5 GB sample containing: Corporate contracts and internal files. Sensitive documents (PDF, DOCX, XLSX). Personal user data and service logs. 📅 Publication Date: April 17, 2026 🛡️ Monitor: analyzer.vecert.io ⚠️ Intelligence Note: This attack is not a typical cybercrime incident; it is a geopolitical hacktivism operation. The actor explicitly states that the objective is to punish nations with strategic ties to the US and Israel. The size of the data (200 GB) suggests a complete compromise of the administrative file servers and databases. #CyberSecurity #ElSalvador #ClaroSV #Anonymous #AnonymousSwitzerland #DataBreach #Hacking #InfoSec #VECERT #Ciberseguridad #DataLeak #TelecomHack #CyberWar 🇸🇻🛡️
VECERT Analyzer tweet media
English
21
127
287
64.4K