I build software with a database-first, security-first mindset. My background is strongest in database thinking, system structure, and practical debugging, and I am actively expanding into Python, backend engineering, AI system architecture, and full-stack product development.
I like building in layers: backend β database β frontend β integration β validation. I care about clean boundaries, provider-neutral design, production readiness, and systems that are understandable enough to maintain under pressure.
Current direction: building AI-enabled products that combine orchestration, memory, local/API model providers, voice, avatars, and strong database foundations.
|
A provider-neutral AI persona system focused on chat, memory, identity, voice foundations, and future avatar/lip-sync capabilities. Stack direction: FastAPI, PostgreSQL, SQLAlchemy, Alembic, pgvector, provider interfaces, local/API model support, STT/TTS boundaries, and eventually realtime UX. |
Exploring modular AI systems where orchestration stays separate from model providers. Core idea: LangGraph + llama.cpp/Ollama/vLLM + LiteLLM + PostgreSQL can be a strong framework foundation, while still keeping the system model-agnostic and replaceable. |
|
Working with CRM-style applications, backend services, deployment concerns, and low-resource server environments. |
Interested in practical business systems, budgeting tools, dashboards, and structured workflows that make teams more organized. |
- Security first: build with professional boundaries from the beginning.
- Database first: understand the data model before rushing into UI.
- Layered delivery: validate each layer before stacking more complexity on top.
- Provider-neutral AI: avoid locking architecture to one model vendor.
- Practical debugging: prefer command-line validation, clear logs, and small controlled changes.
- Maintainable code: readable structure, helper functions, less repetition, and explicit assumptions.
User Experience
β
βΌ
Frontend / Client
β
βΌ
Backend API Layer
β
βββ Product Logic
βββ AI Orchestration
βββ Provider Interfaces
βββ Security / Validation
β
βΌ
Database + Memory Layer
β
βββ PostgreSQL
βββ Relational data
βββ Vector search
βββ Audit-friendly structure
β
βΌ
Model Providers
βββ API models
βββ Local models
βββ Future replaceable providers
I learn best by building real systems step by step. I prefer small, testable progress over vague big rewrites. My favorite workflow is: define the boundary, implement the smallest solid layer, test it, document it, then move up.
One sentence version: I build practical, database-grounded systems with a security-first mindset and an eye toward AI-powered products.