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.
This is in the context of a game, but from my experience in other domains... this is definitely why you want Linux users when you make a product. Might not generate a lots of sales but the signal/noise ratio in the bug reports is just great.
It's a very nice paper on spreadsheets and how we use them. It got enough history in it to make me tick (goes back all the way to the 1300s!). Also it's well balanced, it's not just about blindly blaming tools but looks at their shortcomings but also how we often use the wrong tool for the task... and then end up managing data and knowledge really badly.
Very interesting exploration on software engineering "facts" and what we can really do to increase quality. Unsurprisingly caring for the people seems to be the top factor.
AST tooling is great for porting code and code quality checks. Here are a couple of examples in python.
Overall good piece about how to make quality software. That being said the whole section about "Hire the Best Engineers You Can" should be read with caution... it clearly starts from the "10x coder" fallacy, it's not true and suddenly completely ignores the project context.