Good reminder that those two aspects are not necessarily competing which each other. In the long run quality improves productivity. In the short term it might as well.

No, your model won't get smarter just by throwing more training data at it... on the contrary.

Definitely a good idea, we'd need several such institutes across the world. Would governments be willing to try this?

Interesting study on the impact generative AI can have on people performances in business settings. There are a few nuggets in there. In particular anything related to problem solving people do worse with generative AI tools than without. And even worse than that when they've been trained (probably due to overconfidence). The place where it seems to help is for more creativity related tasks... at the individual level, but at the collective level creativity decreases due to homogenization. Definitely things to keep in mind.

Indeed, don't mindlessly add tests. I find interesting that the doubts raised in this piece are once again concluded using an old quote of Kent Beck. What he was proposing was fine and then over time people became clearly unreasonable.

Something is definitely bonkers regarding the use of JavaScript on the web. The amount of bloat is staggering.

Faster with less effort doesn't seem to lead to quality code overall.

Understandability is indeed a very important goal. There are easy ways to improve it in a system.

This study does a good job looking at the impact of community smells over the presence of code smells. This is an excellent reminder that the organization influences greatly the produced code.

Interesting study, the amount of bugs which could have been prevented by the introduction of static typing in Javascript code bases is definitely impressive (15% is not a small amount in my opinion).

An interesting interpretation of what was behind the "move fast and break things" motto which is nowadays blindly followed by some. A bit of a long piece but does the job and propose a more complete view and an alternative approach.

Shows why it's important to go for a blameless culture, also outside of postmortem. This is definitely not easy but worth it.

This is a good set of properties to strive for. Since the SOLID principles start to show their age this might be a worthwhile alternative.

Interesting statistics, this show how important it is to have well structured and focused change sets as much as possible.

Good summary that TDD is many things... it helps for quite a few dimensions of writing code, still, it's not a magic bullet in term of design. Your software design abilities are crucial to practice it well.

Looks like a promising linting tool for Python. Feature packed and faster than most other options out there.

A bit too much written in superlatives for my taste. Still, this is an interesting set of qualities indeed. Definitely things to aim for.

Interesting plugin for SonarQube to evaluate the footprint of a mobile application. This should complete well what exists for desktop applications and web frontends.

In our industry, we obsess too much over individual performance. In turn it means that the systems we put in place within or around our teams get neglected... this is a problem because it is what has the biggest impact on quality and performance.

Good explanations on why trading quality for speed is always a bad idea. It also goes on about how to avoid sacrificing quality through the definition of done and proper estimates.