interests: (security, AI, and open source) ∈ healthcare
San Jose
Joined December 2019
- Tweets129
- Following6.3K
- Followers2.5K
- Likes348K
august (foss/acc) retweeted
I’m so appalled by the hatred towards her. Yes, she’s a little over the top and millennial-cringe filming herself crying, but her struggle is real. Not everyone can just reinvent themselves overnight.
If you stand to gain financially from the AI boom (founder, investor, etc) you need to work extra hard on your empathy. If you were unfortunate to be on the other side of the isle, you’d be crying too.
Of course the only practical solution is to eventually adapt. But a little crashout in the meantime is perfectly acceptable.
august (foss/acc) retweeted
Pokemon letting me officially remix Lavender Town for the Pokemon rave was maybe one of the coolest things I’ve gotten to do in a LONG time. Thank u everyone for the nicest feedback ever 😭 I really cared about this !!!
august (foss/acc) retweeted
If your planner dies, your robot can keep executing the last command it received. That’s a problem in safety critical robotics systems.
General code review models catch a lot, but they usually miss the robotics-specific safety stuff (stale commands, missing watchdogs, actuator limits, real-time bugs).
So I built a Claude skill to check for those!! ⬇️
github.com/catplotlib/roboti…
august (foss/acc) retweeted
6/ Remarkably, when we reconstructed the image using neural activity from one of the states, it looked exactly like the conscious face, and when we did the same from the other half of time, it looked exactly like the suppressed face. This means that just from neural activity, we can reconstruct in rich detail not only something that you consciously perceive, but also something that escapes your awareness.
august (foss/acc) retweeted
the models love to add so much extra code for cases that will never happen
one example is in review it 'caught':
"changing a setting while being demoted from admin in the same request" which no user would ever hit
but then they miss the obvious things that grind down your codebase quality over time
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.