What we mean by "operations," and how it's changed over the years.
NoOps, DevOps — no matter what you call it, operations won’t go away. Ops experts and development teams will jointly evolve to meet the challenges of delivering reliable software to customers.
Developers with a creative streak don't get to opt out of security.
Developer "artists" who think they're too good to address vulnerabilities in operating systems and applications must shoulder blame for insecure systems.
The result of the Oracle-Google case blocks an inappropriate extension of copyright.
As the Oracle v Google trial shows, we get proper rulings on copyrights and patents when judges and jurors understand the technology they're ruling on.
Code isn't just for programmers. It's a part of the world we live in.
The judge presiding over the Oracle/Google case learned Java, and that skill came in handy when coding specifics arose during the trial. It's proof that coding is a part of cultural competence, even if you never do it professionally.
An astonishing connection between web ops and medical care.
Machine learning and access to huge amounts of data allowed IBM to make an important discovery about premature infants. If web operations teams could capture everything — network data, environmental data, I/O subsystem data, etc. — what would they find out?
Experts make the leap from correct results to understood results.
We can't forget that data is ultimately about insight, and insight is inextricably tied to the
stories we build from the data. Subject experts are the ones who find the stories data wants to tell.