Architecture grounded in implementation
System boundaries, contracts, data structures, interfaces and operational constraints are designed by an architect who remains directly involved in code, packaging and release.
Senior engineering profile · Windhoek, Namibia
Llewellyn van der Merwe
Director | Senior Architectural Engineer of Intelligent Software and Systems
A senior, hands-on software and systems architect whose work combines direct implementation with company leadership, client responsibility, infrastructure, operations, release ownership, security, open-source stewardship, teaching, and applied intelligent systems.
- Engineering
- Since 2008
- Public evidence
- 109 canonical repositories
- Operating range
- Architecture → production
C++ · Pythonnative engine + publication pipeline
PHP · TypeScriptgenerators + intelligent interfaces
Executive profile
One architectural view, from intent to operation.
I design and implement systems across the full engineering lifecycle: from domain modelling, architecture and data contracts through code generation, integration, validation, delivery, production operation, maintenance and responsible AI-assisted engineering.
Platforms and ecosystem thinking
Long-running generators, reusable-code registries, deterministic pipelines and deployment tools turn difficult engineering decisions into repeatable systems.
Production ownership
Linux infrastructure, containers, networking, access control, incident response, delivery and continuity inform decisions from the beginning.
Sustained stewardship
Public history shows platforms maintained across CMS generations, language boundaries, changing dependencies and long operational lifecycles.
Since 2008software engineeringarchitecture and hands-on delivery across public and confidential systems
Since 2010Linux and production operationscontinuous operational responsibility supporting engineering judgement
109canonical public repositoriesde-duplicated lineages; forks and mirrored histories excluded
12source-reviewed flagship recordsordered by current CV and case-study significance
Repository metrics are dated, scoped evidence snapshots. They are not summed into vanity totals and are never presented as a substitute for engineering context.
Capability map
Capability is shown through application.
Filter the map by engineering layer. Each capability names how it has been applied and links directly to project evidence or the documented professional record.
Architecture
Software & systems architecture
Designing coherent systems across domain models, interfaces, generators, runtime boundaries, delivery, and maintenance.
Application and evidence
JCB’s compiler-oriented platform, the complete GetBible engineering estate, reusable Power registries, OctoJoom, and container release systems maintained across long operational lifecycles.
Architecture
PHP & Joomla engineering
Deep framework, extension, compiler, package, migration, and production experience across Joomla generations.
Application and evidence
Joomla Component Builder, Sermon Distributor, client platforms, official volunteer teams, maintenance work, and framework strategy.
Intelligent systems
Python pipelines & tooling
Deterministic transformation, validation, release orchestration, data integrity, and engineering automation.
Application and evidence
Python work includes the fail-closed GetBible v3 builder, the released Librarian and MCP services, desktop tooling, study-data generation, and the Hymn Booklet Generator’s measured print-production pipeline.
Architecture
C & C++ systems work
Long-standing C and C++ capability spanning application design, CLI tooling, ABI governance, deterministic native output, cross-platform builds, and conformance testing.
Application and evidence
Public C++ evidence includes Game of Life and Go Fish from 2020. Current work advances that record through GetBibleSWORD’s C++20 engine, stable C ABI, and the native Zend/PHP extension.
Intelligent systems
JavaScript & TypeScript
Typed integration layers, protocol servers, web interfaces, API clients, and constrained automation.
Application and evidence
Joomla MCP exposes a typed, source-catalogued tool surface with guarded writes; GetBible adds a hardened Telegram application, a TypeScript web client, and JavaScript Scripture embedding.
Architecture
API design & integration
Designing stable machine interfaces, route catalogues, serialization contracts, validation, and compatibility boundaries.
Application and evidence
Versioned static API publication, C ABI design, Python and PHP libraries, Joomla Web Services, MCP contracts, web clients, and long-lived professional integrations.
Delivery
Bash, Linux & automation
Product-scale Shell engineering, operational scripting, repeatable environments, server administration, release tooling, and fail-closed delivery workflows.
Application and evidence
OctoJoom, the wider Octoleo tool family, JoomEngine’s deterministic image pipeline, GetBible API v2, server backup tooling, and current Incus/OpenCode environments provide direct public evidence.
Delivery
Containers, CI/CD & releases
Multi-architecture images, reproducible builds, gated publication, package release, and production-aware delivery.
Application and evidence
JoomEngine’s generated image matrix, OctoJoom’s deployment control, official Joomla images, cross-architecture native releases, package publication, and reproducible Incus environments.
Delivery
Security & incident response
Operational hardening, credential boundaries, guarded changes, recovery, auditing, and maintainable controls.
Application and evidence
Production server responsibility, Vaultwarden-backed operations, explicit MCP write guards, and isolated development environments.
Architecture
Data transformation & migration
Schema-aware transformation, import/export workflows, integrity checks, version migration, and deterministic publication.
Application and evidence
JCB schema and extension generation, GetBible module extraction, static API building, and institutional document/database systems.
Architecture
Developer tooling
Tools that encode architecture, reduce drift, and make correct work repeatable across teams and projects.
Application and evidence
JCB, Super Powers, Octoleo’s Shell utilities, GetBible builders and libraries, native extraction tooling, MCP integration, and reproducible engineering environments.
Intelligent systems
AI & MCP integration
Connecting reasoning systems to real engineering environments through typed, constrained, auditable interfaces.
Application and evidence
Joomla MCP and OpenCode platform work combine protocol tooling with credential, network, write, and environment boundaries.
Stewardship
Open-source leadership
Architecture, release stewardship, maintenance, contributor support, and responsibility for systems used beyond one organization.
Application and evidence
Long-term JCB stewardship, official Joomla service, Joomla Docker work, and direct responsibility for the public GetBible, JoomEngine, Octoleo, and TrueChristian engineering estates.
Stewardship
Documentation & communication
Making complex systems legible through specifications, reference material, implementation notes, talks, and teaching.
Application and evidence
Project documentation, Joomla community service, conference sessions, mentoring, and technical training.
Flagship project evidence
Substantial systems, not isolated keywords.
Twelve source-reviewed records define the current case-study order. The first six are shown here; every flagship brief exposes purpose, interfaces, decisions, delivery constraints, validation, evidence limits, and direct public source.
Long-running maintained platform
Generator platform · long-term stewardship
Joomla Component Builder
A compiler-oriented development platform for generating native Joomla components, plugins, modules, and supporting code across multiple Joomla generations.
Public package · production certification gated
TypeScript · intelligent systems integration
Joomla MCP
A TypeScript MCP server that maps a source-catalogued Joomla Web Services surface into structured tools with guarded write operations.
Maintained public platform
Shell · Docker · cross-platform operations
OctoJoom
A substantial Bash control plane for deploying and managing Dockerized Joomla and OpenSSH development environments across Linux, macOS, and Windows.
Current source-reviewed build system
Shell · deterministic image production
JoomEngine container release engine
The official Shell-based Docker image build system for Joomla Component Builder, generating build matrices, manifests, tags, and published images from upstream release evidence.
Source-reviewed production library
Python library · reference resolution · Unicode search
GetBible Librarian
A Python library for Bible-reference resolution, Scripture retrieval and Unicode-aware search, with bounded behaviour, verified caching, PyPI distribution and separate Query and Search service integration.
Official Joomla maintenance evidence
Official images · release operations
Joomla Docker
Official Joomla container image work covering repeatable builds, image variants, multi-architecture publication, and upstream delivery constraints.
Browse all 12 flagship briefs and supporting records
Joomla Component BuilderGenerator platform · long-term stewardshipJoomla MCPTypeScript · intelligent systems integrationOctoJoomShell · Docker · cross-platform operationsJoomEngine container release engineShell · deterministic image productionGetBible LibrarianPython library · reference resolution · Unicode searchJoomla DockerOfficial images · release operationsGetBible Robot and Mini AppPython · Telegram Mini App · public-service operationsGetBible Sword PHP ExtensionC · C++ · PHP extension · native ABIGetBible Scripture Application LayerModern PHP · immutable domain objects · concurrency controlsOpenCode PlatformIncus · reproducible engineering environmentsColibri Local-AI InfrastructureBash · CPU/NVMe inference · systemd lifecycleGetBible v3 publication pipelinePython · deterministic data engineeringC++ public engineering lineageC++ · CMake · native system evolutionGetBible engineering ecosystemNative engine · APIs · libraries · applicationsGetBible FlutterDart · cross-platform native applicationGetBibleSWORDC++20 · native extraction boundaryHymn Booklet GeneratorPython · document engineering · printJCB Super PowersReusable architecture · dependency registryJoomla project serviceOpen-source leadership · infrastructure · strategyLong-running professional systemsClient platforms · operations · continuityOctoleo Shell automation estateShell · repository and infrastructure toolingTrueChristian publication systemsShell · Python · Joomla publishing
Canonical public engineering record
The evidence is an ecosystem, not a shortlist.
109 attributable, de-duplicated public repository lineages are organised by engineering significance. Forks, mirrors and generated delivery are not allowed to inflate the record.
JCB & JoomEngine20 canonical repositories
Compiler-oriented Joomla development, reusable-code registries, packages, documentation and distribution.
Joomla MCP1 canonical repositoriesTyped, bounded and auditable Joomla administration for modern agent and intelligent-system workflows.
OctoLeo13 canonical repositoriesBash-centred deployment, container, repository, release, networking and operator automation.
GetBible24 canonical repositoriesNative integration, Python services, modern PHP, deterministic pipelines and public application surfaces.
Official Joomla Docker1 canonical repositoriesIndependent official-project evidence of container compatibility, maintenance and production distribution.
Applied AI platforms2 canonical repositoriesHardened agent environments and practical local-inference infrastructure with explicit operational boundaries.
Explore all public evidence
Search the complete record by ecosystem, tier, technology and professional significance. Every entry links directly to public source.
Approved engineering profile
The whole system, in one view.
The profile graphic is also the site’s design grammar: layered architecture, explicit interfaces, evidence at the edge, and production responsibility at the base.
Open the exhaustive professional record Engineering method
A system is only complete when it can evolve.
The recurring pattern across generator, data, native, infrastructure, and AI work is a set of explicit contracts connecting judgement to repeatable execution.
Model
Clarify the domain, invariants, data, ownership, and failure boundaries.
Encode
Turn decisions into types, schemas, generators, protocols, and reusable components.
Deliver
Build, validate, package, deploy, observe, recover, and document.
Evolve
Maintain compatibility, migrate safely, absorb feedback, and reduce future drift.
Professional trajectory
Sustained responsibility, not isolated snapshots.
Engineering began in 2008. Official Joomla volunteer service began in 2016. The distinction matters, and the timeline preserves it.
1996–1999
Commercial foundation
Early work in software, visual communication and business operations established a practical foundation for independent delivery.
1998–present
Mission, public teaching and service
A long-running commitment to preparation, public communication, counselling, publishing and community responsibility.
2008–present
Software engineering
Progression from web and interface work into PHP/Joomla application architecture, reusable developer tooling, generators, APIs, data systems, containers, native integration and intelligent platforms.
2010–present
Linux systems administration and production operations
Continuous responsibility for servers, hosting, access control, firewalls, backups, deployment, monitoring, continuity and incident response.
2013–present
Founder and Director, Vast Development Method
Company leadership, architecture, commercial delivery, institutional programmes, infrastructure, release ownership and long-term maintenance.
2014/15–present
Joomla Component Builder and JoomEngine
Architecture and stewardship of a compiler-oriented Joomla development platform and its surrounding reusable-code, package, documentation and delivery ecosystems.
2016–present
Official Joomla volunteer service
Architecture and strategy, production, operations, testing, mentoring, directory leadership, Docker maintenance, security-related service and Afrikaans localisation.
2016–present
Long-term institutional delivery
Sustained engagements through Vast Development Method, including pharmaceutical distribution and continuing operational responsibility.
2017–present
Regional institutional systems
Senior engineering and continuing support for East African Community contexts, with confidential implementation details intentionally withheld.
2019–present
EU–EAC MARKUP programme delivery
Application and web delivery through Vast Development Method in a multi-stakeholder programme context.
Current
Applied AI, MCP and intelligent systems
Joomla MCP, hardened agent environments, local CPU/NVMe inference, deterministic data pipelines and guarded automation extend an established engineering base.
Professional context
Company leadership and long-term delivery.
Client and institutional work is delivered through Vast Development Method. Named engagements are professional programmes and relationships—not a list of unrelated employers.
2013–present
Founder, Director, Senior Architect and hands-on engineerVast Development Method
Company leadership, public engineering, commercial and institutional delivery, infrastructure, operations, release ownership, security and technical direction.
2016–present
Long-term engineering and operational responsibilityNamPharm
Application delivery, continuity, maintenance and operational responsibility within a pharmaceutical-distribution context. Private systems and implementation details remain confidential.
2017–present
Institutional systems and continuing supportEast African Community
Senior delivery and sustained operational responsibility for a regional intergovernmental context, described at outcome level to protect private infrastructure.
2019–present
Programme delivery and maintenanceEU–EAC MARKUP
Application and web engineering through Vast Development Method in a multi-stakeholder programme context.
Selected engagements
Architecture, delivery and supportGIZ and broader consulting portfolio
Development and social-impact engineering alongside shorter and medium-duration consulting engagements. Client technologies and internal workflows remain confidential.
Technology domains
Languages connected to shipped systems.
No proficiency bars and no arbitrary scores. Each language is shown with the engineering context in which it is applied and a route to supporting evidence.
PHP
Framework, compiler, Joomla, native-extension, package, API and long-lived production systems
C++
Native extraction, stable interfaces, cross-architecture delivery and formal foundations
C
Stable C ABI design and Zend/PHP extension engineering over pinned native dependencies
Python
Libraries, asynchronous services, deterministic data pipelines, Unicode search and operational tooling
Bash
Product-scale Linux automation, deployments, repository workflows, model operations, builds and recovery
TypeScript
MCP servers, typed tools, browser systems and guarded agent workflows
JavaScript
Joomla interfaces, Telegram Mini Apps, browser systems and integration layers
SQL
Relational data modelling, schema evolution, migrations and application data
Docker
Official images, deterministic build matrices, service composition and hardened agent environments
Linux
Production operations, service lifecycle, networking, security, continuity and performance boundaries
Teaching, mentoring and service
Technical leadership includes making systems understandable.
Knowledge transfer is a deliberate part of the engineering practice: establish the underlying model, reduce unnecessary complexity and help another person understand the system well enough to work independently.
Knowledge transfer
- Formal and technical lectures on Joomla engineering, algorithms, design patterns, architecture and intelligent-system practice.
- Conference and community sessions with practical, source-backed implementation detail.
- Internship supervision and one-to-one developer mentoring.
- Architecture coaching covering decomposition, interfaces, operational boundaries, secure delivery and technical communication.
Mission and long-form communication
Faith, mission and service have been a long-term foundation since 1998, including full-time mission work from 2000, the establishment of a Windhoek church in 2004 and elder service from 2026.
The combined supplied archive and public playlist record approximately 831 distinct sermons and 689 hours of long-form teaching across eight years, reflecting sustained preparation and public communication.
Leadership, documentation & service
Technical influence is also maintenance, explanation, and trust.
The professional record includes open-source direction, infrastructure responsibility, testing, mentoring, documentation, conference teaching, and long-running client relationships. These are engineering responsibilities, not an afterthought to code.
Review the public service record- Official Joomla service across architecture and strategy, production, operations, testing, Google Summer of Code, Joomla Extensions Directory, web infrastructure, Docker maintenance, security-related work and Afrikaans localisation.
- Long-term architecture and stewardship of Joomla Component Builder and its reusable-code, package, documentation and distribution ecosystems.
- Public speaking and technical sessions in Marbella, at JoomlaDay USA and the Anabaptist Code Blocks Summit, with a scheduled Joomla World Conference 2026 session.
- Formal and technical lectures, internship supervision, one-to-one mentoring and developer coaching in architecture, Linux, design patterns and responsible AI-assisted engineering.
- Open-source documentation, review, maintenance and operator-facing guidance across multi-language systems.
- Mission, church leadership, long-form teaching and publishing systems sustained over decades.
Engineering conversation
Complex system, difficult migration, or platform decision?
Start with the objective, constraints, and evidence. The useful conversation is about the system that needs to exist—and how it will remain dependable after launch.