
into devtools. Avid splitboarder. CTO at @moment_dev. previously @lyft and @Dreamworks. @recursecenter W14! She/Her
Seattle, WA
Joined April 2009
- Tweets2.9K
- Following1.1K
- Followers1.5K
- Likes6.7K
Lita 조원경 retweeted
Ok can finally talk about what I’ve been working on at Reflection. Introducing Mirror, our own open source coding agent optimized for Beam.
I started the mirror project when I first joined Reflection, and it has gone through many iterations since then.
Install it today with: uv tool install reflection-mirror
github.com/reflection-oss/mi…
Signups are now open on Code[dot]Storage.
Today, more new repos are created per second on Code Storage than any other platform.
Lovable, Bolt, Amp, Poke, and many more of the largest agentic workloads store their code and agent memory at scale using Code.Storage.
Lita 조원경 retweeted
I'll be saying this a few times for the next month or so, but @gitbutler is hiring. Pref in SF or Berlin if possible. TS, Rust, git infra. Come build cool shit with us.
jobs.gitbutler.com/
Lita 조원경 retweeted
Should have shut down the CFP on Git Merge by now, but due to extreme laziness I haven't flipped the switch. We have 40+ great P's, but if you want to join us in Lisbon and talk about Git, throw your hat in the ring now, because I'm about to shut it down.
git-merge.com/
Finally got @amadeus to write about what goes into making our diffs so special.
A love letter to FE development: web workers, WASM, novel virtualization and memory management techniques, and more.
Fun read if you're a perf geek and hate blanking.
pierre.computer/writing/on-r…
Lita 조원경 retweeted
The GitHub Copilot App is now GA!
- multi-repo and multi session with /orchestrate
- build personalized agent-driven UI and tools with canvases
- isolated worktrees, cloud sessions in GitHub sandboxes (stateful microVMs)
- local and cloud automations
Lita 조원경 retweeted
WELCOME TO WASHINGTON, SOCCER FANS. Get acquainted with our state via this highly accurate and mostly-to-scale map.

ALT A hot mess of colorful scribbles all over a map of Washington, featuring doodles of iconic Washington features like mountains, orcas, ferries, cherries, onions, and other produce. The map emphasizes the busyness of the Seattle area, I-5, I-90, US 2, and the U.S./Canada border during the World Cup games.
Lita 조원경 retweeted
If you've been wondering what I've been up to, the team and I have been cooking up something new.
A new agent-native development environment deeply integrated with the GitHub graph. Not just for writing code, but all of the meta-work as well.
Lita 조원경 retweeted
If you have a project that needs fast, reliable, git based code storage that is built with modern, agentic workflows in mind then we should have a chat about code[dot]storage
DM here or email kris[at]pierre[dot]co
Lita 조원경 retweeted
I am trying to build the fastest way to query a CSV with SQL. I have it down to 2 clicks.
Lita 조원경 retweeted
I've turned this into a blog post with an interactive visualization: "TurboQuant, or: why are random compression schemes often nearly as good as carefully-designed ones?". Link in reply.
The first time you hear about the JL lemma, it will seem too good to be true. And it is, kind of, I'll explain. The idea is: if you have points in large d-dimensional space, a RANDOM projection to much smaller k-dim subspace will be "nearly optimal" "in the general case." Or, more specifically: with high probability, the pairwise distances between points are preserved, given a couple other requirements around d and k.
So why don't we just use random projections instead of carefully-constructed ones all the time? This is the most common misunderstanding of the JL lemma, and the one thing to really understand about it: in many (most?) datasets that are meaningful to humans, you actually CAN do better with something like maybe PCA. If your dataset is pathological, e.g., the points all lie on a plane even though it's technically in 3 dimensions, then clearly some planes you project onto will be better than others. The JL lemma does not apply to 2 and 3 dimensions, but you can imagine this would be true in large numbers of dimensions too. (See screenshot 1, i hope you like it because i made it myself lol.)
If you know just those facts, you will be pretty well-prepared to answer most questions about its use. Most of the papers Delip mentions do presuppose that you know this. At least when I was a student, I found this to be non-obvious.
Lita 조원경 retweeted
Alex is bringing markdown to life and it can't happen soon enough.
"Run your entire business out of a markdown file", aws COGS edition. Look. When I search resource list for `gitea`, the total/forecasted costs should update too, so that I just see the costs for `gitea` resources. This is my #1 request for @JoinVantage. I got tired of waiting so I built a template on top of the API (see next tweet).
Lita 조원경 retweeted
"Run your entire business out of a markdown file", aws COGS edition. Look. When I search resource list for `gitea`, the total/forecasted costs should update too, so that I just see the costs for `gitea` resources. This is my #1 request for @JoinVantage. I got tired of waiting so I built a template on top of the API (see next tweet).
Lita 조원경 retweeted
Ok. For the last, like, 15 years, I've constantly been told that CRDTs (and Yjs in particular) solve collaborative text editing. Both the offline and live-collab cases. After an excruciatingly painful evaluation, I argue not only is this completely false, they're generally not appropriate for production-grade editors... at all.
Yeah, I know: everyone uses Yjs, so the problem must be us. Right? That's what I thought too. Well, did you know that on every single collaborative keystroke, Yjs will REPLACE YOUR ENTIRE DOCUMENT? (See this GitHub issue: github.com/yjs/y-prosemirror…) Did you know that this is BY DESIGN? (See this discussion on the ProseMirror boards: discuss.prosemirror.net/t/of…) Did you know that this breaks, like, every editor plugin? (See the ProseMirror author's commentary here: discuss.prosemirror.net/t/of…)
I am not trying to bag on anyone, but to me this kind of mistake belies a fundamental misunderstanding of what text editors need to perform well, in any situation, let alone a collaborative one.
Anyway, learn from my pain. I wrote a somewhat long-form article about all the other challenges we ran into with CRDTs on our blog: moment.dev/blog/lies-i-was-t…
Lita 조원경 retweeted
We're hiring a senior PM - does this sound like you?
Here in @GoogleLabs we're leaning hard into a "continuous AI" future - a fluid cycle of ideating, building, monitoring, and iterating.
One of my teams focuses on AI coding, and we're making this future real!
We're looking for a senior PM who is excited about enabling a next generation of builders, has technical experience themselves, and is ready to build in an AI-native way.
Pls share with folks you think would be great! google.com/about/careers/app…
Lita 조원경 retweeted
Moment is Google docs, but for markdown, with a git backend.
@southpolesteve was just complaining to me about this
Google docs but for markdown with github/gist backend
Lita 조원경 retweeted
I missed this at the time, sorry. Yes, this is what we do @samuelcolvin at @moment_dev. The product is basically a Notion-like workspace (live collab, tables, buttons that do things) but (1) it's also plain-old Markdown files, living in git repositories, on your local disk, and (2) it's programmable (because markdown) and therefore natively amenable to use with `claude`.
Here, for example, are two templates claude pretty much one-shotted. An NES emulator with living memory space visualization:
and a dashboard for our team's live PRs:


















