Skip to content
Mark Janssen edited this page Jul 23, 2019 · 6 revisions

Every coder likes good code. This guide is here to answer the debate about what that is for those within the math and scientific crowd (not, notably, those of symbolic logic). You think you know how to code? Perhaps you've coded for 30+ years and figure you've got it figured out. Well, I'm here to shake the establishment out of its local minima to show you a new vista to take coding 1000 years into the future.

The personal computers and the Internet has taken programming and data processing out of the enterprise and out of academia. Data and its complexity are growing faster than anyone's code and faster than Computer Science.

Otherwise, this guide is language-neutral to give maximal degrees of freedom for experimentation. It does, therefore assume an iterative hardware architecture--the most readily available to schmoes and royality alike.

What makes good code? Efficiency, high-level Abstraction, low-level Readability, Correctness.

You think there's something else? No there is not. Cost to deliver is already wrapped into the equation because code that answers these four items is cheaper in the long run.

If you're interested in more, please read Hacking with the Tao and check out the. PositionOS project.

Mark Janssen, Gothenburg, Nebraska

Clone this wiki locally