Tabflows π΄ββ οΈ retweeted
black pill: enterprises are putting their AI transformation (and the most existential business risk/opportunity of a lifetime) in the hands of their IT department
Welcome Health got their pumpkin, and the front desk sent the love right back ππ«Ά Happy Halloween week to the whole Welcome Health team in Augusta π»
Our pumpkin found a good home at DirectMed DPC π Right there with the stethoscope and the otoscope, where it belongs. Happy Halloween week to the whole DirectMed team π»
I think of max effort as βthere are a lot of things you should think about and the correct solution is unlikely to be the solution you lazily come up with firstβ
Which when you put it that way makes more sense why max effort on some tasks is either wasteful or makes the agent fail to do the simple stupid thing
Winning bets that accidentally payed off
1. Aws making their ui unusable because agents like clis
2. Effect.ts making typescript unreadable because we stopped reading the code
3. Rust making the learning curve unreasonable because we stopped writing the code
Tabflows π΄ββ οΈ retweeted
Why are you still using pull requests?
Is it for code review?
If so, do you really think your or your colleagues catch bugs and mistakes that an Opus 5.5 or Fable or Astra won't find? You can literally spawn all three of them and have them check four times each.
(Also, don't tell me you don't have a "stamp plz" Slack channel or group chat somewhere.)
Is it for knowledge sharing?
Surely there's better ways for that now than the PR, no? We have models that can generate explainer videos, presentations, podcasts, games, quizzes, walkthroughs, ... for any piece of code it can reach.
Is CI the reason?
Well ackshually, CI means continuous integration and its original meaning is the *opposite* of having long-lived branches and PRs.
But, leaving that aside, your agents are hopefully already running the tests before they push something, and hopefully they can run as long as they want and don't block you so they can run the whole test suite and generate "irrefutable proof" and end-to-end demo videos and so on... And so they run the tests and confirm and then you push to a branch and everything runs again and then you merge and then it runs again? That doesn't make sense, does it?
Maybe you work in open source and you accept contributions, in which case I can't speak to the value of pull requests. It's been 2 years since my last OSS contribution. But from what I heard, the time of the PR is coming to an end in OSS too?
I honestly don't get why people still stick to PRs.
With agents you can now move 10x faster, you can finally do real continuous integration, and get more confidence in the changes the agent made.
Don't slow yourself down by having all the changes pile up in a PR.
if you think you fit this, send me a dm!
i'm hiring for the sales team at Tabflows, $100β120k base, $200β240k OTE + generous equity
we've been growing 10% week over week since August and want to hire the best of the best.
a good portion of the best engineers have moved around to companies where they can more directly work with ai
so you see founders of the companies they're leaving posting how they're doing really interesting ai work
but it's futile, competing for talent is impossible right now











