On the peculiarities of running a network for a university... this is an interesting way to frame it as basically being an ISP with benefits.
A deep dive into the events which led to the SolarWinds breaches. The responsibility from Microsoft as an organization is staggering. Their handling of security matters massively failed once more. I don't get how governmental agencies or other companies can still turn to Microsoft with sensitive data.
This is indeed a good way to classify events probability in requirements. It definitely impacts how you handle them in software.
Very unsurprising, the harm is probably done though. They'll have to work hard for their reputation to recover (even though it was probably low already).
Nice trick, definitely should use it more often.
Indeed this is not for any environment and projects. So take it with a grain of salt. That said, I think this piece has a core truth to it which is more general. Software architectures shouldn't be considered as something fixed as soon as they are planned, they need to be validated through use and to be prepared to evolve over time as needed.
Need to know if two shapes overlap? Good explanation of an elegant algorithm to do it.
The ordering used for matrix multiplications definitely matters.
Little and to the point reference on safer SQLite use. I should check if some of this would apply or is used by Akonadi as well.
The right and wrong approaches for paginating results coming from a database.
Ever wondered where fuzz testing is coming from? This is an important bit of history.
Interesting status report about HTTP/3 support in curl. Shows quite well the various alternatives and how special HTTP/3 can be.
How trustworthy are the extensions you get in your editor or IDE? I'd expect most marketplaces to not be well harmed against such attacks.
Good reminder that firewalls need to be adjusted for proper HTTP/3 support.
Nice reminder that even though we try to make things simpler to understand to people, there is a point where we can go too far.
Chatbots can be useful in some cases... but definitely not when people expect to connect with other humans.
Interesting deep dive in where the PIDs seen in user space come from. And also yes, there is something matching PID 0 which can be traced back to early UNIX systems.
SIMD keeps providing interesting performance boosts for parsing work loads.
Unsurprisingly they had to adjust under the pressure. The most blatant issues might be gone, it is still a bad idea at its core.
Good advice on designing your database tables. The comments are good too, they allow to complete the picture.