Pinned Tweet
Here is the demo:
saphyra-examples.vercel.app/…
Took a while because I had to stabilize the new API "onFinish" (was sleeping in a branch for like a month).
Source code is bloated because of all the page settings are intermingled.
Good to know:
There is no built-in revalidation, Saphyra only gives a callback to run when a subtransition (async().promise) is done (onFinish API). You build revalidation logic on top
It's low-level by design, so others can build higher level APIs
Async effects in a React app would be fired by useEffects, which don't participate on transitions afaik, so you can't batch them like I did in this example.
Clicking multiple times on the same button won't dispatch them right away cause there is a before dispatch (beforeDispatch API) handling this conflict. There is multiple conflict solving resolution strategies that before dispacth can handle, check the Before Dispatch page.
In the console, I attached the store to the window, so you can check "revalidationList.history" while you interact with the page.
Expand the transitions devtools transitions, that will help understand what is happening. Don't forget to sort by name and filter by transition names.
Have fun.
Vitor Markis retweeted
We’ve raised $1.3M from YC & Afore Capital so you never have to type or speak again.
Typing is slow. Talking into your computer is awkward. Subvocal fixes both
Our glasses give you the speed of speech without you making a sound or touching a keyboard.
It tracks your internal speech muscles with non-contact sensing and decodes silent, almost invisible mouthing into text at more than 200 words/min.
Pre-orders are now live at:
subvocal.co/preorder?utm_sou…
não tem demanda por essas coisas que agora voce consegue fazer
esse que é o problema, nao tem demanda
*amo o deschamps
a AI potencializa a experiencia do dev em 100x, o software de antes consegue ser criado por alguem com 100x menos experiencia
a gente ainda nao sabe o tipo de software que apenas engenheiros com 10 anos de experiencia conseguem proporcionar
Vitor Markis retweeted
Vibe coder:
prompt -> app release -> 0 revenue
Software engineer:
Rent vps -> prompt -> build their own software factory system before build the app -> write hundreds of markdown spec -> thinking of scalability from day 1 -> mocking vibe coder -> app release -> 0 revenue
esse deve ser o sentimento de quem sobrevive aos layoffs de IA e tem dinheiro infinito da empresa pra torrar em qualquer ideia que vier pro negocio
Vitor Markis retweeted
Maestri's simplicity is making it the AI agent orchestrator of choice, far beyond developers. I keep hearing from students, researchers, and professionals in every field.
So I'm starting the School of Maestria. Videos to help you master Maestri.
Lesson one: Getting Started.
Vitor Markis retweeted
I am looking for my next career opportunity!
I'm Corbin Crutchley; an engineering leader, consultant, author, and open-source maintainer.
Previously as a VP of Eng, I've sped up engineering efforts for companies. My teams rework large-scale systems while building new features at the same time.
You may also know of my OSS projects (@tan_stack & others) or my books (@playful_program).
Roles I'm looking for:
- CTO / VP of Engineering for small/medium companies
- Staff+ Engineering roles, esp developer tooling
- Consulting gigs
Likewise, if your project is particularly challenging and / or complex, let's talk.
Know of a good role for me? Book some time on my website or reach out in direct messages:
corbincrutchley.com
quem era diferenciado antes da IA vai continuar sendo depois dela, isso é confortante
sobre se vale a pena ou nao criar software hoje em dia
surgiu uma anomalia na historia chamada claude code (e derivados) que permite fazer qualquer trabalho computacional com custo 0
todo software criado antes disso nao considerava esse concorrente, então cada um criava sua solução custom para o problema
claude code agora é uma ameaça a essas soluções custom, o usuário precisa considerar tradeoffs e se realmente vale a pena assinar seu saas, seu plano, contratar sua empresa, contratar seu serviço... ou assinar anthropic $20 por mes
software em 2026/27 não pode competir com claude code, deve se aliar a ele. deve ser criado a partir dele. não a partir do claude code em si, mas desse modelo generico de modelo bom + harness + conhecimento de dominio
o que claude code nao consegue fazer? quais dores de quem tenta criar solução a partir dele? quais os medos? vale o trabalho de vibecodar solução?
criando tendo modelo + harness como core do negocio, o usuario nao negocia tradeoffs, é claude code ou claude core super powered buffed 5000
Vitor Markis retweeted
one Opus 5.5 prompt, and now I run around a virtual office managing agents to work on github issues and merge conflicts
I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.






















