With too many alerts, you can be paralized into inaction.

The importance of personal branding as an engineer, plus tactical strategies you can implement today.

Don't blame the devs, or the testers. Blame the bad system.

Software is like surgery. Nobody wants surgery.

If the goal is to uncover better ways of developing software then, well, yeah.

I've seen a broken deployment go unnoticed for several hours before being fixed. No more!

Incremental/iterative software development challenges many of our deeply-ingrained assumptions about efficiency and control.

I'd rather see a conversation about planning, rather than ending debate with a cheap quip.

Yishai Beeri of LinearB discusses strategies to improve flow of PRs and code review with smarter tooling.

How can we unambiguously represent a password safely for shell, YAML, JSON, etc, and also know if it needs to be unescaped?

How frequently are you incorporating feedback into your code?