I've been giving this a proper crack over the past few weeks and am still shocked at how seamless and native the @figma agent feels on the canvas. Really feels aligned with the og figma ethos, delightful!

whoever re-designed the workers and workflows pages in @Cloudflare, i love you

Saw what’s apparently called cloud iridescence in Vietnam and freaked tf out

Some thoughts on the discourse around @Railway team's outage. I was a mid-level SE at @datadoghq ANZ in 2023 when the company had a major, long lasting outage (actually started while I was mid demo). I was in a sales role, and what was most interesting to me was the response from customers after the incident was resolved. A lot of small, smb and commercial customers were livid, demanding compensation, being a bit rude to staff etc. However, most the large enterprises and massively scaled orgs were annoyed, sure, but mainly just wanted to be spoken to throughout the process, and informed of how it happened, as they wanted to ensure it didn't happen to them as well. I don't think expecting your provider to never have an outage is feasible, but expecting them to communicate well throughout is how you can differentiate between your options. FWIW $DDOG is up 3x since that outage.

This tutorial I made on Figma 5 years ago secured me the job I have at Figma today youtu.be/Bwq6RHcGn8M?si=-_sL…

arrived in SF and got a flat tire immediately but it’s okay I found pizza on arrival

really feeling the dude on this lime bike blasting the smiths tonight

extremely excited to be working at figma right now, for my engineering friends, there's some absolutely wicked flows that are being made possible through figma in the near future!

First place at the OpenAI hackathon with my codex in Pokémon demo! 75k worth of credits yippeeeeeeeeee I made Sam Altman a Pokémon :))

The memory side of this was a compounding effort six months in the making. A 4x reduction in out-of-memory crashes. 76% fewer weekly out-of-memory events. 71% reduction for our highest-risk files. We got there through smarter memory loading, more aggressive memory cleanup, geometry cache reductions, font unloading, and data structure optimizations that cut roughly 100MB of memory usage. No single fix did it, but each one made the improvement larger. So proud of the team for the grit it took to deliver this win for our most complex files!​​​​​​​​​​​​​​​​ 🫶

Are anyone elses claude code sessions in the new GUI sometimes just disappearing? I just alt tabbed back to the window and a session I had running is now completely gone, as if it's been archived. This has happened a few times

Since @redbarkco launched I've been steadily improving the trial conversion rate over time. I've got a lot of this measured in @posthog to verify what I'm doing is working, and thought I'd share what's working the best. 1. Initially, there was 0 onboarding process, you just landed in the app and had to go from there. Obviously that was never going to work, so I built a first user onboarding process that took them through adding a connection, destination and then making a sync. So by the time they finish they had their data flowing through 2. I improved on this significantly by adding an escape hatch. Sometimes banks take too long to send data, or something just goes wrong, and users were stuck in onboarding. So if anything takes longer than 10 seconds to load, or an error is thrown, a 'skip' onboarding button shows up 3. The final change I made that I think is the most interesting is that initially I only gave users a limited subset of features to use on trial (saving me on the per user cost for account access). I've now given users much more access, and have noticed that they do indeed, on average, take advantage of this extended access to trial the product further, and are more likely to convert. That's it for now. Will share more as I optimise this further.