cbro retweeted
Individual objections are easy to ignore, and employee leverage shrinks as models improve. That's why the @UTAW_uk / @CWUnews recognition effort at Google DeepMind matters: independent ethics oversight, whistleblower protection, and a right to refuse projects on moral grounds.
ALT Two documents. 2018, Project Maven: about 4,000 employees sign a petition against the Pentagon drone-imagery project, some resign — Google does not renew the contract (The New York Times, June 2018). 2026, Pentagon contract: 600+ Googlers and DeepMinders sign an open letter asking Sundar Pichai not to put AI models on classified networks — the deal is signed anyway, days later (The Information, Apr. 2026). Kicker: Individual objections are easy to ignore. That is the argument for collective representation.
this could have been an email
and it could have stayed in drafts
Andrew's thoughts on the Bun Rust rewrite .. andrewkelley.me/post/my-thou…
cbro retweeted
Long post incoming, but I'm desperate at this point and need the internet's help. (For the TLDR, check the replies for links and action items)
So my little sister Chizo has been fighting leukemia for the past 2.5 years. She's been in remission twice, once after a bone marrow transplant from our brother and then again after a CAR-T treatment after another relapse last year. She is now in her third bout of the fight, as the leukemia has returned yet again in December of last year.
She's spent the majority of this year in the hospital and they tried an alternative CAR-T treatment, which did not work this time. Afterwards, the doctors gave her two options: manage her pain and spend time with her family and loved ones until it's time to pass on, or to take a In order to address this third bout, they tried an alternative CAR-T treatment that did not work this time. The doctors gave her two options:
1) Manage her pain and spend the rest of her time here with her family and loved ones
2) Take a life-threatening chemotherapy treatment that can lead to heart/liver failure based on the intensity of it to bridge her to her next treatment, whether it's another CAR-T treatment or a bone marrow transplant if they find a donor.
She's a fighter, so she chose the chemotherapy treatment and is still fighting to this day. So I'm here to ask for y'alls help as she continues this fight.
How you kill a developer ecosystem
When you care more about OKRs and launchcals than solving real problems
I have no idea what exactly happened here (but I can guess) but you will never ever retain your DevRel talent if they have zero autonomy to solve real developer issues.
Two months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days.
It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories.
I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming.
I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing.
Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.
I'm a strong believer in comments that explain the intent next to the code that should align with that intent
ca-caw!
experimenting with a lightweight IDE that doesn't have an editor.
@pierrecomputer absolutely cooking
@tilt_dev underrated imo
I did 150+ interviews and ended up working with a lot of the people I interviewed.
My preferred interview length would be an hour. That's enough to go deep on a problem with someone.
In literal 5 seconds all you're getting are vibes. Vibes are important but foolish to hire on.
Replying to @Steve_Yegge
It's very obvious when you should hire someone or not. If they're good or not. You know within 5 seconds. I never thought that gathering signal was a problem. If eliciting signal from the candidate is difficult, maybe the candidate just doesn't have enough signal to begin with
the "Member of Technical Staff" title originated at Bell Labs. almost 100 years ago.
I found and patched three minor issues in Caddy, which is an extremely high quality Go codebase.
github.com/caddyserver/caddy…
I've verbally accepted an offer to join as staff eng @buildwithfern to sling some yaml (the currency of the future).
I'm excited to be a part of a small team scaling it up with @getpostman.
I'm excited to try a bun runtime that doesn't segfault! This is some pretty crazy work (see thread)
Replying to @jarredsumner
why: I am so tired of worrying about & spending lots of time fixing memory leaks and crashes and stability issues. it would be so nice if the language provided more powerful tools for preventing these things.