🌍 UAE - Dubai | 🤖 Progenitor of Adaptive Systems | 👽 Aficionado of transhumanist philosophy | 🛩️ Extreme sports athlete

• 🏁 HEX Grid Tessellator - Generate hexagonal grid images. Useful for transparency masks.
• 📡 Pinger - Like ping, ...but prettier, ...with CSV file exports.
• 📖 Year Planner - Generate a printable Year Planner .docx or .pdf, optimized for duplex printing.
• 🖨️ 3D Printing Models - Parametric 3D Printing models. Including Thingiverse - Parametric Hinge
• 🌉 Bridge Builder 2000 - A parabolic tied-arch bridge design program.

• 🎲 ECS Game Engine (Java Version) - ECS (Entity Component System) Game Engine - Java version.
• 🎲 ECS Game Engine (Original C++ Version) - General-purpose ECS (Entity Component System) Game Engine.
• 📐 Parametric Function Solutions - Parametric solutions for cubic polynomials and trigonometric functions.
• 🤖 OpenAI GPT Reference App (Procedural) - Template for writing procedural OpenAI GPT API applications.
• 🤖 OpenAI GPT Reference App (OOP) - Python template for writing object-oriented OpenAI GPT API applications.
• 🧠 Recurrent Neural Network (RNN) - RNN training algorithm experiments.
• 🧠 Neural Network (ANN/MLP) - Multi-layer perceptron experiments.

• ❄️ Fractal Renderer (DOS) Configurable Mandelbrot fractal geometry renderer.
• 🌐 M3DE - 3D graphics engine for mode 13h demo coding. Targeting 386 and 486 machines from the 90s.
• 🌈 GFX-13 (v2, C) - Mode 13h 2D graphics library for old-school demo coding, written in C and inline assembly.
• 🌈 GFX-13 (v1, ASM) - Mode 13h 2D graphics library for old-school demo coding, written in x86 assembler.
• 🔵 Vector Balls - Vector ball demo, with parallel starfield renderer, and palette fade-in and fade-out.
• 〰️ Polynomial Curve Fitting Library - A polynomial curve fitting library.
• 📄 INI File Library (DOS, Win 3.1, Win 95/98) - Read and write INI files.

• 🌐 3D Cube Demo - Interactive 3D cube demo, for the Commodore VIC-20 and Commodore 64.
• ⌨️ Code Probe (C64) - Machine language monitor for the unexpanded Commodore 64..
• ⌨️ Code Probe (VIC-20) - Machine language monitor for the VIC-20 + VIC-1211A Super Expander.

• 🐍 Common Python Library - Common Python library repository. Deprecated, but kept around for spare parts.
• 🍵 Common Java Library - Common Java library repository. Deprecated, but also kept around for spare parts.
• ⚙️ Common C++ Library - Common C++ library repository. Deprecated. More spare parts.
• 🔪 Common C# Library - Common C# library repository. Deprecated. If only I could sell these spare parts.
• 📊 Common MATLAB Library - Common MATLAB library repository. Deprecated. Spare parts R us.

• LinkedIn
• X
• GitHub

Applications should ship with a UI (GUI, TUI, or CLI) that lets business users tune business-configurable features in production.

• For the sake of an example, if a business user is using a hypothetical system that pays disbursements out of a general ledger account, then the general ledger account number should be changeable from the UI by a business user with appropriate permissions, in real time.
• Governance can be enforced by building an authorization step into the UI so an appropriately permissioned authorizer can authorize edits made by other users, also from the UI, and also in real time.
• However, it should absolutely not be the case, that the business team are expected to log a work request to change a general ledger account number in an upcoming sprint.

The high level principle here, is that business users should be empowered to deliver value to customers in real time, with no delays. Governance and security requirements should not be used as an excuse to impede the flow of value to a customer. But instead, built into the work flow that delivers value to the customer, from the front end, in real time.

Bezos made is famous, but the idea is timeless. The UI is a client of the API, with no privileged backdoor.

• Anything a user can do through the UI must also be possible via the API. Both surfaces ship together and are regression-tested together. This promotes both automation opportunities and human usability at the same time.
• Every API should be designed with the blind presumption that it will be productized and exposed to external consumers. Even if you don't plan to expose your API externally, design it as though you are, anyway.

The high level principle is that the UI is a client of the API; the API is the system of record for behavior, and the UI gets no backdoor.

Applications should emit well-structured events and telemetry from day one, with simple, generic, reporting features available out the box, from the front end.

• While more sophisticated reporting solutions may be developed later, if an application operates on a set of business-significant tables, the business team should have a simple way to quickly see and extract the data from the application's UI, without having to constantly request extracts from the development or data analytics teams, or worse, wait months, or years, for a dedicated reporting solution.
• Data entities should include both internal unique machine-readable names, as well as non-unique human-readable display names. So that you don't end up with cryptic, highly abbreviated, or weird looking entity names being surfaced to application user interfaces or reports.

The high level principle is that data models should be designed so that OLTP/OLAP is optimized for reportability from the start, not as a retrofit.

If your system integrates with other systems, don't wait for integration testing. Build a lightweight simulator developers can run locally.

• It doesn't need to cover everything, just the interfaces you depend on. I once watched a team hack together a physical ATM simulator on a plank of wood, card reader and all. Ugly, but invaluable.
• To manage simulated vs real world drift and divergence, pin your simulators to reality with contract/conformance tests (recorded traffic, consumer-driven contracts), model the failure modes (latency, errors, malformed responses) not just the happy path.

The high level principle here, is that simulators can significantly enhance both development and testing, by supplementing, not replacing, real integration testing.

💭