The Principals of 'Pataphysical Programming

Based on the prose examples the article gives (the chess/lunch story and the crucifixion/bike race story), it looks like a truly 'pataphysical system wouldn't need IO at all. Instead, you'd have a program of some sort, that was simultaneously doing 'pataphysical computation and mundane computation. In the story of Jesus and the bike race, the narrative never shifts between the story of racing up the hill and the story of Jesus being killed on a cross, the story is both at the same time throughout. By analogy, I suspect the article would like us to consider what kind of system we'd need to construct in order to, I suppose, be a story about a bike race (or something else equally removed from programmer's usual domain) and an application to serve web pages at the same time.

Of course, given 'pataphysic's status as "the science of imaginary solutions" I won't be holding my breath for a 'pataprogrammatical Rails-killer anytime soon, but it's a fun idea.

If you start your own company, you can give yourself any title you like.

edit: That doesn't mean people will refer to you as such, or respect you, but that's a different issue altogether.

On topic, a Chief Philosopher probably would serve a role between product manager and evangelist.

Principal principles.

http://www.wsu.edu/~brians/errors/principal.html