🇧🇷 Immigrant in 🇳🇱 learning Calisthenics | ex-AWS. Opinions are my own

The Netherlands
The second news is…. Powertools for AWS Lambda now has an official website! powertools.aws.dev/ There are countless people to thank as it took nearly 5 years to get here. Special thanks to @IsenbergRan @djfurman4tech and all public reference customers #aws #serverless
Sharing 3 important news about Powertools for AWS Lambda tomorrow... If you follow @IsenbergRan you might know one of them already
11
30
119
19,507
RT @antoniotabet: A família miliciana odeia tanto mulher preta, que resolveu atacar Nossa Senhora Aparecida!
26,740
24
How are you structuring adversarial reviewers for verification loops? Prompt or got predefined reviewers per domain like security, language, db, outcome verifier etc? I’ve got the latter and while it worked well, models advanced, and now I’m rethinking its efficiency atm
1
339
Heitor Lessa retweeted
The models are also very good at architecture only if you can see it. "The beauty is in the eye of the beholder." It's not I disagree - I just want to highlight "the nature of problem". An operator's skills and competence is the ceiling for LLM. Why? ⬇️
I understand the appeal in trying to find the first plausible fortress in our retreat from writing code, but if you think it's "architecture", I have bad news for you. The models are also very good at that.
1
4
9
4,108
Removing *all* unit tests because of agents take is mass hysteria
6
15
1,823
Heitor Lessa retweeted
This is a highly inconvenient state of affairs: Fable > Astra Codex > Claude Code
8
2
117
16,732
Heitor Lessa retweeted
Jev
165
1,289
17,897
697,566
Heitor Lessa retweeted
Bend 2 is here! It is a new programming language that blocks AI mistakes via *proof checking* - the same technique big AI labs used to solve open math problems, like Navier-Stokes. It is also very fast, and runs on GPUs. Watch the video. Link in the comments.
RELEASE DAY After almost 10 years of hard work, tireless research, and a dive deep into the kernels of computer science, I finally realized a dream: running a high-level language on GPUs. And I'm giving it to the world! Bend compiles modern programming features, including: - Lambdas with full closure support - Unrestricted recursion and loops - Fast object allocations of all kinds - Folds, ADTs, continuations and much more To HVM2, a new runtime capable of spreading that workload across 1000's of cores, in a thread-safe, low-overhead fashion. As a result, we finally have a true high-level language that runs natively on GPUs! Here's a quick demo:
633
1,261
11,013
1,916,441
Heitor Lessa retweeted
New experiment: json-render + jev The future Generative UI is instant Your components, your actions, your design system Rendered in milliseconds
221
503
7,777
1,332,111
Heitor Lessa retweeted
Jev seems ideally suited for this. Have AI constantly evalulating tiny in-progress chunks of work and deciding if it should send more more or less production traffic
Everybody's trying to figure out how to scale PRs/code review, but the bigger bottleneck is going to be deployment. If models keep getting cheaper, eventually you have 100s of agents working autonomously. What is the plan for getting all that code merged and deployed? You can't put them all in a single merge train. We need to start letting agents validate changes against tiny slices of production traffic before the PR is merged.
4
1
55
6,328
Heitor Lessa retweeted
Here's a 45-second TL;DR on Jev. I find the core idea beautifully simple, but the video made it really hard to understand. Hope you find it helpful.
After co-inventing ChatGPT, I kept asking myself: why have superhuman chat models not led to AGI? I’ve spent the last 2 years in stealth building a new way to train models (RLCD), and a new type of frontier AI model that we are releasing today: Jev • 20-200x faster • 40-400x cheaper (w/ output tokens free) • Frontier composable intelligence optimized for decisions AFAICT the shortest path to AI-based economic revolution
240
726
9,805
1,746,625
Heitor Lessa retweeted
Agentic coding in 2026
215
934
7,413
1,027,374
Heitor Lessa retweeted
Que vídeo espetacular, que aula sobre o escândalo do Banco Master! Sinceramente: quem assiste a isso e ainda insiste na narrativa tosca de que o esquema não começou no governo Bolsonaro, ou age por má-fé ou tá com a cognição totalmente comprometida. Não tem outra explicação. FLÁVIO É VORCARO BOLSOMASTER DA CORRUPÇÃO
178
4,568
12,437
206,011
Heitor Lessa retweeted
Okay, it took a week to get this done the right way, but it's finally all complete, my comparison of Astra and Fable 5.1 with @VulcanBench 🖖 A few things took longer here, the primary one being some updates to my benchmarking score to layer in code quality. This added 3-4 days of time, but for the right reasons. This new class of models requires a new class of benchmarks. I don't think we can just look at things like accuracy any more, we also have to look at code quality/maintainability factors. Now with VulcanBench-SWE v4, 33% of the score is code quality/maintainability. For me, and many other engineering leaders, seeing a model get a 98% on a benchmark doesn't really give us much signal. I created VulcanBench to help make decisions around model and effort level, and this means not just building evals that represent the kind of work teams give to these models, but the kind of output we expect from these models when building scalable system and working in large codebases. While I would normally share more about my thoughts, I'll let you come to your own conclusions about Astra and Fable 5.1. Both are excellent models, OpenAI and Anthropic have really created a new class of models here, now it's for us to decide if we need this horsepower for daily tasks, or just the hard stuff, and to be realistic about the quality of the output. Model card below, and if you want to do a deep dive, you can find more on the VulcanBench site here: vulcanbench.com/benchmarks/s… And of course, since VulcanBench is open source, you can review every detail of this benchmark, or even run it yourself. The GH repo is here: github.com/morganlinton/Vulc… Live long and benchmark 🖖
57
26
470
89,915
Update after 4 daily usage ChatGPT Work remote feature gives me what I was used to Claude code cloud sandboxes on iOS - trade is now I need always-on device for a working DX Once I learned to workaround the many brittleness and papercuts, the app was useful not practical +
Fully moved to ChatGPT from Claude today … already disappointed with the mobile app experience not having Codex 🤦‍♂️
3
5
1,234
With some care and attention to details, i do think ChatGPT Work can be as good if not better than Claude code app. GPT is still ahead when it comes to: - browser interaction - design UI/UX (no Claude design like tho) - token efficiency - no Claudish Verifications are A+ too
1
161
Update: tried ChatGPT Work and the Codex workaround on mobile. It needs some love - my impression of OpenAI for DX is that Coding is an afterthought for mobile. I don’t expect them to fix within a month (non-trivial) so I’ll likely cancel next month
Fully moved to ChatGPT from Claude today … already disappointed with the mobile app experience not having Codex 🤦‍♂️
7
2
1,174
Why I mention is non-trivial DX fixes. Claude code on mobile would’ve shared screenshots of what the HTML Components / visuals are in the session
146
Fully moved to ChatGPT from Claude today … already disappointed with the mobile app experience not having Codex 🤦‍♂️
45
1
104
21,885
Update: Codex does exist when logged in Safari iOS. In the mobile app, the expectation is to use ChatGPT Work - still miles behind Claude code on mobile Found a workaround but brittle with cloud tasks sub feature I’ll try for a month on Pro plan before reconsidering options
1
464
Heitor Lessa retweeted
This is an accurate take, but also not just an AWS problem. On top of the container ecosystem (k8s too) we've just not cracked really good easy app deployment/delivery pipelines. There's a few more niche companies out there, and I think there's good stuff in Cloud-run and Workers. But broadly deploying and managing containers at scale behind some sort of endpoint is a box of parts you hammer together each time. Lambda hasn't solved this either. Fluid Compute too niche. There's an app packaging structural model we're just completely missing (no not IaC).
Every layer AWS built on top of ECS is dead or dying I keep a list 🫡 • ECS CLI, archived November 2025 • Fargate CLI, archived May 2024 • Copilot CLI, end of life June 2026 • AWS Proton, end of life October 2026 • App Runner, maintenance mode since April 2026
17
11
142
29,991