After a couple of hours, I wished I’d counted the trees from the beginning.

Row after row, trunk after trunk, I’d connect a chain from the tractor to the Gravenstein apple tree. Once back in the seat, I’d lurch forward and pull another one out of the dirt.

This was part of life on a farm. During my teenage years, we turned that orchard into a vineyard.

Before vines could go in, the trees needed to come out. It was manual labor, even with the help of a tractor.

That’s one kind of “work.”

You may not get dirty and blistered in your job, but it can still be a lot of labor to reach developers.

It’s not physically grueling, but creating content is still a form of that definition of work.

There’s another meaning of the word, which is more synonymous with “function.”

A developer might ask, “does the code work?”

Code cannot sweat or strain. But it can most certainly work.

This type of work implies automation. When we employ it, our job gets easier. In fact, that tractor from my teens worked to make it much, much easier for me to clear the field of apples.

That’s the kind of work in the D.E.V. Content Framework.

It’s a mechanism that can help you better perform your role.

It won’t keep you from the other kind of work. You’ll still have to bring the effort of connecting with developers. But it streamlines and focuses that effort.