Mark Erikson

@acemarke.dev did:plc:oajtxomomwvbm5vhvvagyogy

Redux maintainer, building time-travel devtools at Replay.io. I blog about React, Redux, and TS at https://blog.isquaredsoftware.com . Answering questions anywhere there's a textbox on the internet, and otherwise out on the golf course!

Sur Bluesky depuis le 27 août 2023

Abonnés: 7 963
Abonnements: 506
Posts: 1 434
Jours dans les classements: 0

Résumé

Mark Erikson (@acemarke.dev) est sur Bluesky depuis le 27 août 2023. Le compte a 7 963 abonnés, suit 506 comptes et a publié 1 434 posts.

Présence dans les classements

Les meilleurs jours où les posts de ce compte sont entrés dans le top quotidien de Debya.

Ce compte n’est encore apparu dans aucun classement quotidien.

Posts aimés récemment

J’aime publics du réseau Bluesky.

Rodger Sherman@rodger.bsky.social03/11/2026 13:34
Remember, your job is NOT over once you leave the voting booth! Here’s what to do next after you place your vote: —go home —sit on your couch —take out your phone —open Bluesky dot Com —scroll until something good happens
Voir le post
Dominik 🔮@tkdodo.eu03/11/2026 13:31
mainly what I see is agents seeing open issues and then wanting to file PRs against it to "contribute" to open source, or, even worse, agents filing PRs for random edge-cases that are just not worth fixing because no one has hit them in 8 years and likely won't ever.
Voir le post
Dominik 🔮@tkdodo.eu03/11/2026 13:31
yeah best I could come up with today is: only accept external PRs if they are linked to an issue that has a certain label (`verified issue`) attached by a maintainer.
Voir le post
Ivan Akulov@iamakulov.com03/11/2026 11:08
👎 i should’ve asked for a 30-min call • comms on github had a LONG turnaround time (weeks), which made the project super slow. i should’ve made some slides with questions and just asked for a 30-minute call to discuss all questions and align. didn’t think of this!
Voir le post
Ivan Akulov@iamakulov.com03/11/2026 11:08
✅ talking to googlers at conferences helped • one google devrel told me who works on devtools and who owns lighthouse. i also learned why this was moving very slowly (turns out the devtools team is tiny!) • the fix saw light in part because @kurtextrem.de asked some other googlers to nudge this
Voir le post