Good advice to get (back) into sketch noting or visual thinking.
Was it all going to end up as a management fad? I'd say yes. It's not to say the values and principles in the manifesto are useless... but if something gets successful you'd better have guardrails on how it'll be warped. It didn't happen here.
This is something I've definitely seen indeed. There are clearly a threshold effect in the amount of code you have to manage. Solutions working at smaller amounts don't work anymore a couple of order of magnitudes higher, and vice versa.
Such a nice business model... not. There's really a lack of regulation in this space.
Nice little intro of the various components you need for graphics drivers. It's very much geared toward how it's organised on Linux.
They produced Apertus, and now this for the inference. There's really interesting work getting out of EPFL lately. It all helps toward more ethical and frugal production (and use) of LLMs. Those efforts are definitely welcome.
This is definitely an exciting new option for Python development.
Use the log levels responsibly in your applications. Indeed, what are at most warnings are too often reported as errors.
Finding the right level of abstraction for the tests is important indeed. It helps keep them useful longer. Scope and complexity are linked and can help find the right balance of tests.
For technical tasks, the user stories common structure (the "Connextra format") is not adequate. We can indeed take inspiration from other long forgotten agile approaches for alternatives. I particularly like this one, and it works for user stories as well in my opinion.
Definitely the right rule to follow to designing classes in C++ in my opinion.
This is a good pattern, use it! This article does a good job showing variants and where it makes sense to reach out for it.
It's fine to surround yourself with people smarter than you. It's a good thing... except if they are competitive. Then it can become a curse and kill your motivation.
Looks like a nice tool for UX design and getting insights from conversations with users.
Nice explanation of what Bloom filters are for and how they work.
Looks like that following parts were never written. This piece is interesting by itself though, it's nice to have a record of the early times of SCCS and RCS.
It's something I've been trying to practice for year when someone is in a crisis. Seeing the situation as concentric circles of people around the one affected is a simple and powerful idea. Of course, we're humans and sometimes we'll fail at following this advice. At least that gives a good idea about why we'll likely get offended reactions.
Interesting history outlook on where Lean Software Development is coming from. The focus on flow efficiency rather than resource efficiency is definitely key.
There is definitely something tragic at play here. As we're inundated in fake content, people are trying to find ways to detect when it's fake or not. While doing so we deny the humanity of some people because of their colonial past.
That's one of those pieces where the clear cut categories look a bit like caricature. That said, that gives an idea of the kind of posture one should try to reach to be a good manager.