Automated accessibility testing needs to be in your loop, whether you are using an llm or not. Aria labels are easy to get right but they are also easy to forget.
There are documented ways to ensure that changes are visible across threads (e.g. locks). If these are not used, the compiler is within its rights to not go out of its way to pull changes from another thread.
Right, it's pretty inevitable given the incentives. I think it's made worse by PE for a few reasons. They are investing with relatively short time horizons because they will need to sell to pay profits. So the long term health of the business is of no interest. If the reputation of the business suffers, that's someone else's problem. Compared to an individual investor who is looking long term, they need to retain customers and reputation.
It probably still sucks in C, but the C++ DX got a lot better. Importing the idl would generate wrapper functions that made calling code look much more like a normal function. It would check the hresult and return an out param from the function. They also introduced types like _variant_t that help boxing and unboxing native types. It still wasn't fun but it greatly reduced line count.
Nah, unless talking about C++ Builder extensions for COM, in Visual C++ land it still sucks big time.
For some reason, there are vocal teams at Microsoft that resist anything in C++ that is comparable to VB, Delphi, .NET, C++ Builder ease of use regarding COM.
Hence why we got MFC COM, ATL COM, WRL, WinRT (as COM evolution), C++/CX, C++/WinRT, WIL, and eventually all of them lose traction with that vocal group that aparently rather use COM with bare bones IDL files, using the command line and VI on Windows most likely.
Then it does whatever is needed to make it safe. For example, it might use a hash ring to assign each meeting room to a single node, and that node processes one request at a time. Most distributed systems are like this.
A traditional database funnels all your data changes down to one leader node which then accepts or rejects them, and (if A+C in the case of single node failure is desired) makes sure the data is replicated to follower nodes before accepting.
A distributed database is similar but different pieces of data can be on different leaders and different follower sets.
This is a community that values a high signal to noise ratio and generally eschews small talk, a la nohello.org. Congratulating someone for learning something does not advance the conversation.
It also has a low tolerance of what it perceives as reddit- style in-group signaling via repetition of a common meme (xkcd, in this case). Again noise vs signal but also suspicion of karma farming.
There's also the cultural context of Monty Hall being a real person who had a real game show, on which he really opened doors with goats behind them. Most readers of her column would have been familiar with the mechanics of the show. And the question doesn't really make sense if there's a chance that he opens the door with a prize, there's no more hidden information in that case.
