Dynatrace

FEBRUARY 4, 2021

The term “site reliability engineering” was coined in 2003 by Google VP of Engineering Ben Sloss , who famously noted on his LinkedIn profile that “if Google ever stops working, it’s my fault.” ” According to Google, “SRE is what you get when you treat operations as a software problem.”

Engineering 249

Engineering DevOps Government Latency 249

Adrian Cockcroft

JANUARY 20, 2023

Here’s some predictions I’m making: Jack Dongarra’s efforts to highlight the low efficiency of the HPCG benchmark as an issue will influence the next generation of supercomputer architectures to optimize for sparse matrix computations. Next generation architectures will use CXL3.0 Next generation architectures will use CXL3.0

Architecture 52

Architecture Latency Benchmarking AWS 52

Dynatrace

FEBRUARY 4, 2021

The term “site reliability engineering” was coined in 2003 by Google VP of Engineering Ben Sloss , who famously noted on his LinkedIn profile that “if Google ever stops working, it’s my fault.” ” According to Google, “SRE is what you get when you treat operations as a software problem.”

Engineering 170

Engineering DevOps Government Latency 170

Rigor

JANUARY 13, 2020

Take, for example, The Web Almanac , the golden collection of Big Data combined with the collective intelligence from most of the authors listed below, brilliantly spearheaded by Google’s @rick_viscomi. ” – Andy King, 2003. This book is about performance problems and the various technologies created to fight them.

Performance 75

Performance Social Media Website Website Performance 75

Adrian Cockcroft

JUNE 21, 2022

I also learned a lot about how to work directly with customers, when to shut up and let the sales guy drive the conversation, and generally how technology sales works. I also applied Six Sigma to capacity planning and presented this at a conference in 2003.

Tuning 52

Tuning Benchmarking Engineering C++ 52

O'Reilly Software

MARCH 7, 2018

Build a more scalable, composable, and functional architecture for interconnecting systems and applications. So, software is a part of a greater whole, and typically multiple generations of technologies must coexist peacefully and purposefully to provide a viable service. They were too wrapped up in silly technology debates (e.g.,

Transportation 72

Transportation Java Programming Architecture 72