"Process intensity" is a good way to describe the kind of programming work I find most interesting. The standard CRUD application being an example of a low-pro

"Process intensity" is a good way to describe the kind of programming work I find most interesting. The standard CRUD application being an example of a low-process intensity software in contemporary context. Often we can become mesmerized by systems of great scale that deal with large amounts of data. But what's really interesting and valuable is not the amount of data per se, but the things done with that data. Furthermore, data intensity and process intensity are orthogonal. That means you don't have to work at a company like Google with massive amounts of data to find interesting work. There's process-intensive work to be found at all scales of data intensity. I've even done interesting side-projects processing less than a kilobyte of data.