Engineering beyond the obvious.
8+ years of building software, designing systems, solving difficult problems, and continuing to explore what comes next.
Architecture. Intelligence. Security. Systems. Engineering.
Eight years changed how I build.
Not a portfolio of finished work.
An evolving record of engineering.
Early engineering is often about making software work.
Experience changes the question.
The work becomes less about producing more code and more about understanding the system around it — its constraints, its failure modes, its users, its future, and the decisions that will eventually become someone else's problem.
Over 8+ years, my work has evolved across full-stack engineering, architecture, distributed systems, security, cloud infrastructure, developer tooling, and emerging AI systems.
Ethern Myth is where that work is collected, explored, and continued.
Every significant architectural decision should have a reason. Good engineering makes intent visible.
A system should remain understandable after its original author has left it.
Identity, trust boundaries, and failure behaviour belong in the architecture from the beginning.
The best engineering creates leverage beyond the code itself — better tooling, architecture, and systems.
The disciplines behind the work.
The work moves across disciplines, but the underlying questions remain consistent: how should systems be designed, secured, operated, understood, and evolved?
Systems & Architecture
Designing software as a system of boundaries, responsibilities, contracts, and operational realities.
- ―Distributed systems & domain-driven architecture
- ―API architecture, contracts, and data boundaries
- ―Full-stack platforms and service orchestration
- ―Data architecture and immutable record integrity
Intelligence & AI
Exploring how local models, agents, and AI-assisted systems change the boundaries of software engineering.
- ―Local LLM inference & deterministic tool execution
- ―Autonomous coding agents & safety boundaries
- ―AI developer tooling & workflow leverage
- ―Model evaluation, latency, and capability analysis
Reliability & Security
Building systems that remain understandable, observable, secure, and predictable beyond the happy path.
- ―Identity architecture, token revocation, and key rotation
- ―Security boundaries and defense against emerging threats
- ―Cloud infrastructure, CI/CD, and automated keep-alive systems
- ―Observability, failure analysis, and operational clarity
What has been built.
These are not demonstrations assembled to fill a portfolio. They are systems, experiments, tools, and architectural explorations built to answer real engineering questions.
Web Applications & Platforms
Live systems, web applications, and decoupled platforms.
M Util Box
Small tools. Large leverage.
Cross-platform developer utility workstation combining unified clipboard history, JSON inspection, and rapid payload transformations into a high-leverage environment.
K-Awake
Keeping systems awake.
Automated uptime monitoring and keep-alive orchestration daemon designed to keep serverless microservices warm, resilient, and responsive.
Secure Session Vault
Authentication is infrastructure.
Encrypted session storage and credential synchronization hub exploring token revocation, key rotation, and reliable identity boundaries.
C-Recipe
Resilient discovery at scale.
High-performance culinary discovery engine and recipe sharing system built for offline resilience and fast mobile queries.
Just Art Store
Decoupled domain boundaries.
Self-hosted decoupled commerce platform exploring domain separation, high-throughput checkout flows, and specialized digital asset delivery.
Engineering Tools & Systems
AI agents, local inference tooling, security libraries, and distributed infrastructure.
EM Ollama Agent
Controlled intelligence, running locally.
A security-conscious local AI coding agent exploring what autonomous software engineering can look like when inference, execution, and system access remain under deliberate control.
“The interesting question is not whether an agent can execute commands. It is whether an agent can be given meaningful capability without losing control of the system around it.”
Clinical Core
Systems where correctness matters.
A cloud-oriented clinical system exploring immutable records, identity separation, domain boundaries, and reliable handling of sensitive workflows.
“Clinical systems demand explicit ownership, traceability, correctness, and architecture that remains understandable under pressure.”
Polyglot Systems
Different technologies. One system.
An architectural exploration combining a Go gateway, .NET domain services, and a Next.js interface to investigate boundaries between infrastructure, domain logic, and user experience.
“Technology choice becomes interesting when it serves an architectural boundary rather than a résumé. The question is where each technology creates leverage.”
Local LLM Compare
Understanding intelligence through comparison.
An interactive environment for comparing locally available language models and exploring the practical differences between inference behaviour, capability, latency, and model characteristics.
“AI engineering requires more than calling a model. It requires understanding what the model does, how it behaves, and where it fails.”
JWT Service Package
Authentication is infrastructure.
A reusable authentication service exploring refresh-token management, token revocation, key rotation, and the operational concerns surrounding modern JWT-based identity systems.
“Authentication should not become a collection of scattered decisions inside application code. Identity deserves a boundary and explicit lifecycle management.”
M Util Box (Core Engine)
Small tools. Large leverage.
A cross-platform developer utility workstation combining clipboard history, JSON inspection, payload transformation, and everyday engineering utilities into a single environment.
“Engineering productivity is often improved by eliminating small sources of friction. Good tools disappear into the workflow because they make the workflow better.”
K-Awake (Daemon)
Keeping systems awake.
An automated uptime and HTTP keep-alive system exploring scheduled execution, service availability, serverless behaviour, and lightweight reliability automation.
“Reliability is rarely one large feature. It is the accumulation of small decisions that keep a system behaving predictably.”