João Drapala

[João Drapala @joaodrapala]

O mano inventou um foguete que dá ré
O outro da ré no foguete

[ERIKA HILTON @ErikakHilton]

Um único ser humano acumulou mais de um trilhão de dólares em patrimônio.

Um patrimônio capaz de acabar com a fome, a sede e as doenças do mundo.

Mas nem a cura pra calvície Elon Musk financiou.

Isso é sintomático dum sistema econômico no qual a acumulação é o objetivo em si.

Os donos do sistema exploram a terra e a mão-de-obra humana pra acumular poder econômico e, então, usar esse poder econômico para acumular ainda mais poder econômico.

É uma corrida de ratos, soltos em uma ilha com recursos abundantes, interessados apenas em consumir até que nada reste.

Essa ilha é o nosso planeta, e está na hora dos seus habitantes pegarem a vassoura.

[Aakash Gupta @aakashgupta]

If you’ve been procrastinating on learning loops, read this.

[João Drapala @joaodrapala]

@HeglerHenri Sou programador e te garanto uma coisa; todo profissional da minha área que veio te diminuir são uns bostas e tão com a própria identidade ameaçada.

[João Drapala @joaodrapala]

@QuinnyPig @steipete Remember when Mythos was a thing?

[Papo Econômico @opapoeconomico]

PIB do 1º tri cresceu 1.1%

Antes de comemorar, olha por dentro:

Consumo das famílias +1.0%. Turbinado pela isenção de IR até R$ 5 mil, antecipação do 13º e Desenrola 2. Crédito PF cresceu 12% mesmo com Selic a 14.75%

Investimento subiu 3.5% no tri, mas caiu 1.4% no ano. A taxa de investimento despencou de 17.6% pra 16.5% do PIB

Indústria de transformação ficou em +0.1%. Parada. Essa é a que gera emprego de verdade

Exportações -1.7%. Importações +4.4%

Tradução: crescimento puxado por gasto público, não por produtividade

O governo injeta dinheiro, o consumo sobe, a inflação resiste, o BC aperta e o investimento definha

Fernanda Guardado (BNP Paribas): "A composição da demanda é ruim. Sinaliza menos crescimento potencial à frente"

O PIB cresce hoje. A conta chega amanhã

[Perucy @PerucyACM]

@elder_plinius that was fast! i think we are going to see more of it and it is time for llms to adopt some adaptive defenses. https://t.co/7m2IM4b9dY

[Sid @sidbid]

Super excited to finally share Dynamic Workflows in Claude Code!!

We built this a couple months ago, and it has slowly become a daily driver for a bunch of people at Anthropic. A few tips for getting the most out of it 🧵

https://t.co/WtwkSd3JPp

[Sam @samsantosb]

Uma SKILL é uma função. Tudo que for dinâmico, parametrizavel tu deve pedir pro Agent te questionar no chat.

Ainda da pra aperfeiçoar skills com um MEMORY.MD que a AI adiciona memorias/experiencias da execução da SKILL.

Seja pra sua leitura ou pra melhoria do contexto dela mesma.

A memória pode ser salva com data/contexto da execução por exemplo.

[Crémieux @cremieuxrecueil]

Sneak peak of a small handful of the evidence from my forthcoming manuscript (summary coming to @palladiummag!) on how there's A LOT of quantitative evidence for the European Dark Ages.

There are so many more graphs than these ^^

[Vincent Hus @vincent_hus]

p99 latency spike. Root cause at 94% confidence. Fix recommended. Report delivered to incidents channel.
This is what AI SRE looks like in production.
Open source. Apache 2.0.

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

[Papo Econômico @opapoeconomico]

NTN-B 2045: IPCA + 7,4%.

O governo brasileiro tá pagando mais que na crise de 2015.

Se a inflação for 5%, você ganha 12,4%. Se for 10%, ganha 17,4%.

Garantido até 2045.

A maior anomalia da renda fixa mundial tá aberta. Vou explicar como capturar. 🧵

[BOOTOSHI 👑 @KingBootoshi]

I don’t want to review code manually anymore.

if codex 5.5 can test e2e and report critical paths and security working then what’s the point?

if i can garden my codebase after blasting crazy features with guardrails why should I review?

why shouldn’t I vibe my way to the top?

[BOOTOSHI 👑 @KingBootoshi]

I created a skill that improves the quality of goal runs for both Codex and Claude Code:

It's called the Goal Ledger, and lets agents track the progress of their goal in a HTML file that you can view.

Minimal, yet VERY powerful for long running goal runs!

Git Link Below 👇🔗

[AVB @neural_avb]

https://t.co/rsXiQW1HWu

[Nick Winder @nicknamewinder]

I built a slightly creepy thing called synthteam.

It distills personas of my colleagues from their public Slack history — what they know, believe, and how they decide — so i can pressure-test an idea without waiting ~12h for a reply across timezones.

https://t.co/9q1zaEzMWX

[✪ Felippe @FelippeRegazio]

se vc pensa assim é pq vc tá tão distante de um CEO/CTO que mal sabe o que eles fazem. é igual quando vc é junior e vc ACHA que trabalha igual ou mais que o senior do seu time, até que um dia vc vira senior rs... galera de business não é santa, e muito menos burra, não subestime.

[Paul Iusztin @pauliusztin_]

`agent-memory` by @neo4j is the best open-source repository for building a unified memory layer for AI agents via knowledge graphs.

They did such an amazing job modeling short, long, and reasoning memory, their ontology, and extraction algorithms.

After spending 2 days dissecting and testing their code, I wrote a full piece on https://t.co/NYVGH6MvYd explaining how it works. I will publish it tomorrow.

[Rafael Cardoso Sampaio @cardososampaio]

O objetivo ao usar a IA para escrever é ela nos ajudar e não escrever em nosso lugar.

O problema é que ela deixa marcas em nosso texto, então é bom usar skills para evitar isso.

Hoje, achei uma super completa feita pelo @carlosferreira. Recomendo D+.

https://t.co/JtF2vwMthJ

[Kyle Mistele 🏴‍☠️ @0xblacklight]

seems like folks liked the article on forking so I turned it into a blog post https://t.co/XXR6tOETMq