The traditional Dev/QA dichotomy is analogous to the Dev/Ops dichotomy DevOps aims to solve. The same solution can work for both.

How do you use the scientific method in your daily work?

Talking to users isn't the job of a user researcher. It's your job as a developer, product owner, UX designer, or any other product contributor.

Facebook has revealed the cause of their 6-hour outage: human error. I hope those pesky humans learned their lesson! Or is there more to it?

When you can't scale down a large feature, think of it the other way around: How could you deliver this by tomorrow?

The distinction some make between "testing" and "checking" is valuable. But the terminology is not. We can do better (with practically no effort).

“Is it a good idea to look for specifically DevOps roles, or other positions like sys admin, engineer, etc?”

"Developers are optimistic, testers are pessimistic." I don't buy it.

"Testing" and "checking" are two different types of activities. They deserve a distinction.

"Check" is one of the most ambiguous function names I see. Avoid it.

Just as software delivery can be separated from deployment, feature deployment can be separated from release.