I can't immediately think of what a useful shader test would look like (beyond perhaps, shader doesn't crash program) - if this is something worth discussing, it would probably be useful to see some real world shader code; perhaps especially two versions of the same shader as it evolve.
I don't generally test css code to check that a background is now indeed set to "a more mauvey shade of pinky-russet" after a change - but I might want to.
I might at least want to run a test with browser automation to check that any text is readable on the background.
I could at least find an example of looking at the rendered page for text (as opposed to in the DOM); Google AI had some ideas of how to check the contrast in a screenshot - but no idea if that would actually work as written.
Having read and enjoyed ghost in the wires (and at some point all of mitnicks books) - I still enjoy the infamous takedown movie. I think it still shows a lot of mindset around social engineering - and realistic holes in security measures. I do understand why a lot of people were pissed off, though.
Surprisingly good is a stretch. Barley adequate more like it.
Now that they've hidden mail access behind oauth (imap and SMTP, additionally SMTP behind global default off policy) and graph api behind oauth2 - it looks like they don't have to worry about real mail clients competing.
Actually fighting [f] to get mail in/out working with freescout right now - and having had learn more than I care to about o365 and PowerShell etc - I wonder how hard it would be to write a couple of stand alone tools to get fetch/send/sync mail working with o365 and local maildir - to get my/sup/any sane Mua to really work with o365/exchange/outlook.
Then there's calendar and teams to deal with..
[f] Thankfully our o365 reseller does most of the fighting - I'm happy to not have tenant-wide admin in AD/entra/whatever kerberized LDAP is called today.
Ed: obviously the 50/30/20 rule sums to 100% so would need to be net - although the US is weirdly treating health insurance as a "premium service" that go into the 50% here, not into taxes like in a modern society.
How so? Let's say that over a year, a given section of code needs to be read and understood once a month. Taking some time to keep the code succinct and free of distraction will increase productivity all those occasions, as well as the rest of the lifetime of the system. Say the next decade.
https://news.ycombinator.com/item?id=48686947