
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…
I finally read the GitHub incident report and have two thoughts.
Found it interesting that they use HAProxy and Istio together. Have not seen that combo before. Feel like those technologies are generationally far apart.
Setting retry polices and timeouts are hard. Having clients that are well behaved and back pressure helps a lot. Wish them luck fixing all this stuff.
githubstatus.com/incidents/z…
Congratulations, Pierre, on the launch! Love your product and impeccable branding.
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.
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…
Congrats @_Evan_Boyle and everyone on the GitHub copilot team!
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
Washington does have “surprise, more mountains” and you can’t visit them in all in one day!
If you are visiting, use this map to determine where you want to go!
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
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.
Achieving six 9s is an impressive feat. No wonder temporal has the reputation of being reliable.
SVP of engineering at @temporalio @psomal talking about how a blameless engineering culture leads to great results
No SLA violations even under cloud provider outages 🔥
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
I thought I provide a counterpoint of what Tauri provides, as we migrated our Electron app to Tauri. As with any technology, everything is just full of tradeoffs.
Since Tauri has a rust core, locks, threads, shared runtime memory, and os calls are much more performant than javascript/typescript. We heavily leverage concurreny, as we read and write to files on disk. Using a system language is going to be far more performant when manipliating a filesystem.
Tauri is also inherently secure out of the box. Tauri explicitly requires you to grant permissions for the filesystem, network, etc., and lets you scope resources. With Electron, you do have to open a port to communicate with the Node.js runtime, which might be a feature for some people. Tauri uses native bridges and function closures between the webview and Rust core, which is inherently safer than local-network IPC (you can encrypt data between the network calls, but you pay for that in performance) as the data never leaves the runtime. Also, using the OS webview, your app benefits when users update their OS, and the binary is smaller because you do not have to package Chromium separately.
But the real reason we migrated: native libraries. Using libgit2 via FFI and jj-lib natively is worth the tradeoff of WebKit bugs. We pass an OAuth2 token at runtime and run git push / git clone under the user's own credentials.
Yes, we do face painful WebKit bugs, especially around rendering the text cursor. But we thought that the cross-platform bugs were worth the trade-off of the security benefits.
I do believe that you can make an Electron app just as secure by using service workers and iframes. It is more work, and you do give up performance for it. But you can do it. If you want to go deeper, I gave a talk at Git Merge: youtube.com/watch?v=4UVzX3UF… that covers our migration in more detail.
















