I'd rather see a 'build failing' badge on a project than no badges at all. It's a strong signal of well-tested code.
Related Posts
I'm still experimenting with UIs for live (sandboxed) evaluation of tests. I've realised that you really want to highlight the failing assertion, not just the failing test.
Feedback welcome :)
It's really satisfying to use a profiler for the first time on a project. I always find a big performance win with only a small code change.
It's never the code that I expected to be slow, however!
Over a sufficiently long time horizon, all code you write is legacy code.