Did you know you could submit your app's tests to the Flutter project, so that we would run them with every change to Flutter's APIs, and that we commit to not breaking you if you do this? flutter.dev/docs/resources/c… github.com/flutter/tests/blo…

every day i refresh moma.org/calendar/exhibition… hoping that there'll be some indication of when the 24h access days will be, and every day i am again disappointed

I just spent multiple hours trying to debug a new certificate setup only to realise that I'd just used the wrong Common Name. Why do crypto systems have such terrible developer experiences? A simple "CN doesn't match" message would have saved me so much effort.

I think it's a real lost opportunity that as an industry we haven't standardised on "bobbin" as the name for a group of strings, especially as in a localization file.

We just published a Whitepaper: The Business Value of Flutter ⭐ Some benefits: - Reduced cost, effort & time-to-market - Streamlined development process - Cut costs & enhanced user satisfaction - Fosters a productive engineering team Read it here 👇 verygood.ventures/whitepaper…

One of the reasons I care so much about our API docs is that I use them literally ALL THE TIME.

At the end of a 45 minute phone call with @citi to fix a transaction that keeps getting incorrectly declined, they literally told me they don't know what's wrong and to try using another vendor's credit card instead. 😧

youtu.be/ObOLGzSnNHI has so much historical video of trains being great.

If I had a quarter for every good musical I'd seen from Google-affiliated folks I'd have ¢50 which isn't a lot but it's weird that it's not zero (the other one being youtu.be/jhpASkz0JU0).

Every few years I watch Primer (runtime 1h17m) and then spend 3 hours examining the various conflicting explanations people have written and diagrams people have drawn trying to understand it.

PSA: renaming issues on GitHub is buggy. Contrast github.com/flutter/flutter/i… and github.com/flutter/flutter/i… (we renamed "severe: new feature" to "new feature" years ago).

I'm doing some analysis of activity on Flutter's GitHub repo. Shout out to our most intense participant, who in 2021 added five emoji reactions in one second and never returned. 👍😕❤️🚀👀

It's wild that several people have claimed to know which company/meeting/person this was, and none have been right: meaning that this exact scenario has repeated itself. Someone DMed me they were there in the room when this happened, but it was a different company from my friend.

There are two kinds of SDK developers: those who wish they could find a way to support shared-memory multithreading, and those who regret adding support for shared-memory multithreading.