This also carries privacy concerns indeed even for local models. It all depends how it's inserted in the system.

This is almost by definition. The post mortem needs to be wisely crafted to look also at previous incidents and the actions to mitigate them.

Nice trick! Using vim as man page viewer. I shall try this.

The introduction of concepts has indeed been a nice improvement to the language.

I wonder how much the focus on Python biased that study... Still, maybe we've been wrong at so much emphasis on math skills for computer science and computer engineering curricula.

Nice and down to earth tips for your technical talk to go well.

Interesting trick in Java internals which is especially improving map lookups.

This is an important position paper in my opinion. The whole obsession towards the ill defined "AGI" is shadowing important problems in the research field which have to be overcome.

This move is really unsurprising... It's bound to become another channel for advertisements to try to cover the costs of running it all.

A bit long and dated for a some advice. Still it does a very good job going through all the different type of tests you'll want to find on your project and how they're structured.

Need to teach security basics to your family, friends and neighbors? Here is a nice resource to do a good job there. We often approach the task the wrong way.

A good in-depth article about pair programming. Shows well the pros and cons.

Looks like a good summary of the book.

We often hear that question about the trade off between quality and cost. The question is badly framed though. If it's low quality it's requires more effort to add or change features... and so it's more expensive mid-term (not even long term).

A good reminder that reviewers have many things to keep in mind and evaluate. This is why what can be automated should be automated.

This is one of the best references I know on the topic. It's not that long, to the point and all developers should know it.

Probably shouldn't feel too bad if you're not doing 8h straight of deep thinking work. This is likely not reachable, and probably most people are lying about it too.

They're so misused that it's better to let them go. Indeed, we can go as far as wondering if estimating stories instead of slicing them is a good idea at all. Doesn't mean all estimates disappear of course, but at the single story resolution? You likely better invest time in slicing them better.

Or why the term "user" in "user stories" need to be seen very liberally.

Good proposals to shorten the time spent executing tests. Tighter feedback loops make everyone happy.