Equational

A common theme in all my software developments is recognizing that true state is continuous, relational, and non-local. Therefore this blog's "tongue-in-cheek" title referring to the Flatland: A Romance of Many Dimensions novella. Building upon this geometric analogy, classical software is very similar to what we humans perceive as "flat normality", that is a Euclidean geometry. Continuity in a Euclidean geometry are dualities (e.g. volume integral vs surface integral). In classical software, continuity is also expressed as dualities (e.g. commit-request vs commit-commit phases in a DB). But what if your geometry is not "flat", not Euclidean? Then maybe your continuity has more than two parts! In physics, for example, three mode continuity exist to express flow or topological continuity. What about in software? And how do we even define "non-Euclidean" software designs?  To express what is a non-Euclidean" software design, we need menti...

I have designed and led designs of Domain Specific Languages (DSLs) in high-demand industries from semiconductor physics and algorithmic trading to distributed ledgers and industrial security. The systems that depend on the DSLs have powered industry-standard CAD tools, secured critical infrastructure, and driven core technologies acquired by global leaders. A key early lesson: mathematically clean domain invariants guarantee simplicity, safety, and scalability. Below is a selection of these projects. Whether you are an organization seeking strategic architectural guidance, or an engineer looking to master advanced language design in my upcoming workshop, this portfolio illustrates the  power of a well-engineered DSL. Design Rule Checker (DRC) Domain and Context:  Validating and finalizing integrated circuits masks in microelectronics (my first role). DSL: The DSL specifies 2d mask operations. Input is given set of masks (e.g. made by CAD automation or human layout ...

PMDL (Physical Model Description Language) is a modeling language I designed for circuit and semiconductor devices. I implemented it as part of my PhD at the ETHZ  (see Litsios, J., 1996. A modeling language for mixed circuit and semiconductor device simulation, Hartung-Gorre).  It was built as a subset of the C programming language to remain simple and familiar, meaning it retains basic C syntax but does not support pointers or full hierarchical models. I had Gemini summarize the language specs below. The reason I bring it up is that the language vertex , edge , face , and element specifiers are actually tying the language semantics to the  k -simplices of a 3D spatial manifold ! And that is a pretty useful thing to know, and something I will bring up again in this blog. FYI: Dessis, which I developed during my PhD and was later acquired by Synopsys to become the number one TCAD device simulator, was my PhD's principal activity. My DSL development compiled to code run i...