DevOps with a Slice of Pie

DevOps with a Slice of Pie

I work as a DevOps Engineer. For a long time, I could not explain my career in a way that my mother could understand. She wanted to understand, but something as abstract and complex as DevOps can be hard for a lay person to grasp. 

Eventually, I realized that my explanations focused only on the technical aspects of DevOps—the pipeline, automation, Infrastructure as Code—and not on the foundational principles of DevOps itself: Flow, Feedback, and Continuous Improvement. These three principles, called the Three Ways, I can explain to my mother by using her favorite hobby—baking—as a metaphor. 

A Story of the Game-Changing Value of Tacit Knowledge: “Is There a Doctor in the House?”

A Story of the Game-Changing Value of Tacit Knowledge: “Is There a Doctor in the House?”

MITRE’s talents for strategic modernization (e.g., enterprise planning, organizational change, business innovation, technology transitioning) are informed by both our explicit knowledge and our tacit knowledge. Explicit knowledge is what we objectively know. Explicit knowledge can be readily articulated, codified, stored and accessed, and transmitted to others, and represents an estimated 20% of our knowledge (e.g., plans, reports, data analysis). Implicit or tacit knowledge is more subjective.

Pin It on Pinterest