kierenj

Despite almost all of the comments already saying it - I cannot fathom how something selling itself as producing flawless UI/UX.. does not demonstrate it in the README, or one click from it

I'd welcome someone pointing out where I'm wrong in my critique of this critique..

"The reason AI is a bad tool is that generally speaking, it is completely opaque."

"The real question is, who can verify that what the AI built is good and true?"

Well, you? The developer? The person responsible for using the tool, no?

Isn't this article just saying, "using a tool blindly and not checking the result" is bad? Which, of course, it would be.

microsoft.com is back -

edit: it worked once, then died again. So I guess - some resolvers, or FD servers may be working!

FWIW, all of our databases, VMs, AKS clusters, services, jobs etc - are all working fine. Which services are down for you, maybe we can build a list?

Sorry - my bad. I literally just connected an old XP VM to the internet to activate it.

Ouch, and login.microsoftonline.com too - i.e. SSO using MS accounts. We'd just rolled that out across most (all?) of our internal systems...

And microsoft.com too - that's gotta hurt

I had a fun pet project, once. Made it available for free to use. Regular releases, and others in the small community made other similar tools.

The amount of shit I got because it wasn't open source was astounding. Akin to bullying.

It was MY pet project! Literally every week, every release, I'd get negative or downright nasty comments.

I wasn't forcing anyone to use it.. people are just so entitled.

Just my experience..

"Top interior design trends" - title of the login page?

The article points out it's technical debt..

No, why? You have to click Approve but then the tweet shows

> Does CrowdStrike do any testing whatsoever? Obviously they didn’t or the incident wouldn’t have happened.

Eh, parts of this article aren't very reasonable. Even if they did a buttload of testing, it only takes one failure in one part of the chain (near the end).

They didn't test something they should have, sure, but obviously they didn't do "no testing whatsoever"

Solution in C#: use named parameters: RaiseInvoice(taxInvoice: false, sendEmail: true)

Looks great! Although with the example.. I couldn't get it to show the "you need to be 21.." message to appear as a state