Matt Brown

@[email protected]

xleem = ROT11(mattb) because ROT13 was already taken...

[Radan Skoric @RadanSkoric]

@aarondfrancis Honestly, a mostly static UI having FPS like it's simulating a world in a game loop is the part that leaves me scratching my head every time I'm reminded this is an actual issue for React apps. :)

[Matt Brown @xleem]

@lennysan No spotify? Might artificially depress your subscribe metrics... Would love to listen, but via a webpage doesn't fit my podcast listening schedule/habits...

[Matt Brown @xleem]

@danielwithmusic and rule specification formats?

[RJ Scaringe @RJScaringe]

What if...

[Heather Adkins - Ꜻ - Spes consilium non est @argvee]

One of the worst vulns I’ve ever seen. Makes you wonder who else knew about it and for how long. Kudos to Dirk-jan for uncovering it. https://t.co/I41xUPZtLV

[Sam Rose @samwhoo]

✨ Big O ✨

Let me take you on a visual introduction to what big O notation is in my new blog post: https://t.co/Nt1jDSRTY8.

With big O notation you can better understand how algorithms will perform, finding orders of magnitude improvements with very simple changes to your code

[Matt Brown @xleem]

@robzolkos @jasonfried I'm interested in this angle!

[Richard King @rich_kingy]

Waipa Tech meetup in Te Awamutu! #AI #technz #waipa

[Matt Brown @xleem]

I'm pretty much 100% migrated to the new butterfly place for social media now. I still read here occasionally but I'd love to connect with you over there instead. My profile is under @mattb.nz there. Find me and connect :)

[Jon Yongfook @yongfook]

11am: this will be a nice self-contained feature I can finish before lunch

6 hours later:

[Matt Brown @xleem]

@samwhoo fascinating perspective (that it sets expectations that readers might feel bad not to meet) that I never even thought of....

I've like them (and added them to my blog) because it gives an up-front indication of whether I have time to read something now, or to save it for later.

[Matt Brown @xleem]

@samwhoo you're sure it's not a directive to citizens on whether or not to festoon their streets?

[Matt Brown @xleem]

@samwhoo nice! very clean and understandable, would consider stealing the structure (I x.., I y.., ...) myself. As a little detail, I love the hover animations on the visualisation links, I literally spent 60s exploring them ;)

[Matt Brown @xleem]

@ioquatix I don't really think you can in practice - do you know of an implementation in the wild where it reliably works?

The draft to clarify that QDCOUNT=1 is nearly done - https://t.co/gVQys6VHpt

[Matt Brown @xleem]

#F1Sprint what's up with all the missing timing graphics!?

[Matt Brown @xleem]

@EnergySRE @odataorg The only place I've ever encountered it is the MS Graph API (https://t.co/Pgqo5CjiAG) where it's definitely the thing.

[Matt Brown @xleem]

@danielwithmusic "...but it is now clear that this was indeed a Google Cloud bug."

Agreed. But what is the bug?
* Allowing a null parameter that defaults to a 1yr time-bomb?
* Acting on the configured intent at 1yr without a grace period?
* Both? Something else?

[Matt Brown @xleem]

@danielwithmusic although it does very much sound like there were at least 1 or 2 concrete bugs in Google's control plane that provided at least some of the holes in the swiss cheese that had to line up. Very bad look.

My takeaway: avoid 2nd tier cloud services like VMware private cloud ;)

[Matt Brown @xleem]

@danielwithmusic definitely a weird/worrying event... in both the initial occurence, and the strange comms!

Fault is such a hard concept in complex systems like this. No doubt there are contributing factors on both sides, any one of which might have prevented the outcome...

[apenwarr @apenwarr]

The reason nobody found this problem in dnssec before now is that, as they say, the fundamental design flaws were completely hidden by the superficial design flaws.

https://t.co/bvMc5ZF3qb