The 'Descriptive' versus 'Prescriptive' distinction is irrelevant for actual writing

I sometimes get asked whether I’m a “prescriptivist” or “descriptivist”, or—worse still—labelled as one. This has always struck me as beside the point. In none of my roles, not as a writer, teacher of writing, or editor, has this distinction ever provided useful guidance. Instead, I base my usage choices upon some combination of assessed ambiguity to the reader, existing convention, degree of formality, emotional impact, and other considerations. The resulting choices might sometimes conform to prescriptive rules or existing usage or neither. Effective writing is a balance of competing requirements, not rote adherence to an overarching “philosophy”.

more ...

Designs don't have "superpowers"

Time for another rant about a word seeing increased use in technical discussions (and elsewhere): superpower. It just doesn’t mean what people imply it means.

more ...

"Opinionated" design as design rationale

I see increasing use of the phrase “opinionated design”, frequent enough to risk it becoming a vogue word in our field. What makes a design “opinionated”? If someone declares a design to be “opinionated”, what might that tell you about it? How would a designer justify that claim?

more ...

The external interfaces to Kubernetes ingress

Defining a Kubernetes ingress seems simple enough: Define a YAML file and you’re good. But that only defines the interface from services inside the cluster to whatever external agent is connecting external client requests to cluster services. It says nothing about the interface from that external agent to the Kubernetes control and data planes. If you are building a cloud provider, how do you connect your external load balancer to Kubernetes clusters inside your cloud? If you are configuring an entire on-prem cluster from scratch, how do you set up access to the Internet?

more ...

Three rings of abstraction in Kubernetes

A common analogy for Kubernetes presents it as “the operating system for microservices”, identifying Kubernetes as a kind of operating system. I don’t think this analogy is wrong but I do think it’s underinformative, leaving the key question unanswered: What abstractions does this “operating system” provide? I suggest that unlike the more focused set of abstractions provided by the classic Unix model, the abstractions of Kubernetes can be grouped into three concentric rings. This highlights the different kinds of benefits Kubernetes affords and clarifies the decisions an organization must make when adopting Kubernetes.

more ...