@acemarke.dev
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!
@danielroe.devReposted by @acemarke.dev🙋♂️ so, what are the git forges you are using - or want to be using? asking for … reasons. (would appreciate sharing for reach)
@replay-io.bsky.socialReposted by @acemarke.dev20 years in web dev. 14+ active client projects. No dedicated QA hire.
"You don't need to hire a QA resource for your projects. Replay can definitely take a handle on it."
Natacha Grey, founder of swoon.ai
@acemarke.devI am so scared of what that car ride conversation must be like :)
@replay-io.bsky.socialReposted by @acemarke.devFull write-up: replay.io/blog/what-ou...
@replay-io.bsky.socialReposted by @acemarke.devWe ran a self-healing loop on our own codebase for two weeks - FullStory detecting, Replay QA diagnosing, Obvious fixing, humans merging. 152 PRs. 80 merged. 5.4 bugs/day. What earned engineer trust wasn't velocity. It was proof of reproduction.
@acemarke.devWe've turned our time-travel debugging tech and expertise into a powerful automated app QA system that can find bugs in any website! Check out how much it's helping one of our customers manage app QA load (especially with the rise of AI-driven dev)
@tmir.reactiflux.comReposted by @acemarke.devTMiR 2026-09: React 19.3; a eulogy to software engineering?
@crutchcorn.devReposted by @acemarke.devI am looking for my next career opportunity!
I’m an engineering leader, consultant, author, and open-source maintainer.
I've been VP of Eng, written books, get 20M weekly downloads on NPM, and more.
Know of a role you think I'd be a good fit for? Book time on my cal or DM me:
@zurichjs.comReposted by @acemarke.devAnd we think we managed to do just that, with your help. So here’s a heartfelt thank you for showing up. For believing in the craft and its people For being an important part of what connects us all across the globe. And for being true artisans of the web.
@zurichjs.comReposted by @acemarke.devWHAT. A. CONFERENCE. 💛 It’s been a couple of weeks, and we’re still recovering from the high from our first ZurichJS Conf edition. With our dopamine resets comes a time for reflection and starting to plan the very loudly requested second edition.
@stephanietuerk.netReposted by @acemarke.devSeparated by handclaps: Use LLMs to write deterministic code that get called at runtime rather than asking an LLM to do the thing during runtime. Truly hope this is obvious to everyone here, but, just in case it's not...
@jovidecroock.comReposted by @acemarke.devPreact 11 is out 🎉 We’ve been hard at work at making our diffing use modern features like moveBefore , leveraging ESM for tree-shaking Preact Compat and ensuring you have a great experience with resumed hydration.
@acemarke.devalso I have been accumulating more Opinions on how I feel about using AI for development, and after recent conf conversations I'm pretty sure I have enough material to put together a third post in that series. Not concrete yet, but thoughts are bubbling around in my head :)
@acemarke.devsorta self-indulgent question, but: would there be any interest in me writing up a career history retrospective blog series? Not sure I have a particular goal in mind, but might be neat to write at some point. (obviously I can post whatever I want, just curious if it's worth prioritizing)
@acemarke.devThis helps clear the way for the next wave of Redux library major versions that I'm planning out. Quick preview: RTK3 API tweaks to improve types and enable new features, a couple breaking changes for DX, and dropping CJS to go ESM-only in all our packages. Details soon!
@acemarke.devFor the prior background and PR links, see:
The merge included deduplicating content and links from the separate sites.
I also did a massive cleanup pass on the core docs, modernizing all pages that had obsolete legacy info.
@acemarke.devThis had been frequently requested over the years. My standard answer is "we'd have to merge our repos into a mono-repo and that'd be too hard". Last year I figured out a viable approach (clone all repos in CI), and over the last couple weeks was able to push that through to completion.
@acemarke.devExcited to announce that:
**We now have a single combined docs site for all the Redux libraries!**
so, all of our docs for Redux core + usage, Redux Toolkit, React Redux, and Reselect now live together in:
hopefully this makes it easier to navigate our docs!
@jovidecroock.comReposted by @acemarke.devReleasing Preact 11 with better hydration, moveBefore support and some reshuffling may sound like a boring release but to me it feels like completing something I've thought about for a while, I want to thank everyone for supporting Preact and enabling my journey
@acemarke.devCongrats! and yes, some similar feelings on my side working on Redux: