* People ask LLMs to write code
* LLMs recommend imports that don't actually exist
* Attackers work out what these imports' names are, and create & upload them with malicious payloads
* People using LLM-written code then auto-add malware themselves
https://t.co/Va9w18RpWu
@thomaslevesque@Dave_DotNet If you declare a private nested type it will be available for name collision in the different file or the same partial class.
File1:
partial class A {
private class B {
}
}
File2:
partial class A {
private class B { <-- collision
}
}
An interesting approach like https://t.co/1tgFAbeT1r . IMO that can be used as pinning tests for limited amount of scenarios, but for most of cases explicit declaration of assertions is preferable. TaxAmount.Should().Be(Base * Rate) is more readable than TaxAmount.Should().Be(15)
The biggest bugfix actually required me to build a private copy of https://t.co/rwDbYWh5qL.Forms.dll 😬 .NET 7 shipped with a nasty bug in Form.ShowDialog(), and a fix is being fast-tracked for the 7.0.2 servicing release in January. https://t.co/20W5F25XqB
😢 R.I.P.
Fred Brooks was the author of "The Mythical Man Month" a book that was hugely influential on so many of us. Also his paper "No Silver Bullet" would be on most people's shortlist of most influential papers.
“XML provides a proper engineering solution to data exchange, so we use JSON instead. JSON gives software developers a more convenient experience by not addressing the hard problems that XML took on.”
@IevgenMir@oFce Hello. Cause can be in ER or in a specific report. ER has some memory optimization features disabled by default. You can enable them and test reports or just contact support. Er features are in the "org administration" module