name: Melvin Issac
role: Software Engineer
focus:
- Business software
- Full-stack platforms
- Desktop applications
- SaaS architecture
- Mobile workflows
- Applied AI
approach:
- Solve real problems
- Model the domain carefully
- Automate quality checks
- Build for maintainability |
|
|
A mobile-first roadside assistance marketplace connecting customers with nearby mechanics for on-site repairs and towing. Product capabilities
Architecture
|
A Windows-first, offline-first ERP designed for paint dealers and inventory-heavy retail businesses. Product capabilities
Architecture
|
|
A multi-tenant SaaS platform for healthcare-job discovery, extraction, candidate workflows and review operations. Product capabilities
Architecture
|
A role-based platform connecting administrators, staff, teachers and parents. Product capabilities
Architecture
|
|
Responsive ordering experiences for bakeries and independent cake businesses. Product capabilities
Architecture
|
A market-structure analysis engine for detecting and validating price-action events. Analytical capabilities
Architecture
|
| Area | Technologies and practices |
|---|---|
| Languages | TypeScript, JavaScript, Python, SQL, HTML, CSS |
| Frontend | React, Next.js, Vite, Tailwind CSS, shadcn/ui |
| Backend | Node.js, NestJS, Fastify, FastAPI, REST APIs |
| Desktop | Electron, Windows-first packaging, offline-first workflows |
| Mobile | Expo, React Native, Flutter |
| Data | PostgreSQL, PostGIS, SQLite, Redis |
| Data access | Prisma, SQLAlchemy, Alembic |
| Testing | Vitest, Testing Library, Pytest, focused and full-suite verification |
| Delivery | GitHub Actions, Docker, CI/CD, packaged-runtime checks |
| Architecture | RBAC, tenant isolation, audit logging, modular monoliths, idempotency |
| AI workflow | Codex, Graphify, Obsidian, structured engineering context |
|
I use AI as an engineering multiplier, not as a substitute for engineering judgment. flowchart TD
A[Product problem] --> B[Requirements and constraints]
B --> C[Architecture and domain model]
C --> D[AI-assisted implementation]
D --> E[Focused verification]
E --> F[Full test suite]
F --> G[Review and documentation]
G --> H[Commit, PR and release]
Workflow principles
|
|
Language cards reflect repository composition, not proficiency. Public statistic services can occasionally be rate-limited.
| Track | Current direction |
|---|---|
| Product engineering | Converting validated business problems into maintainable software products |
| Architecture | Modular systems, domain boundaries, secure multi-tenancy and offline-first design |
| Backend depth | Reliable APIs, PostgreSQL, Redis, queues, idempotency and event-driven concepts |
| Frontend depth | Complex state, data fetching, role-aware UX and responsive product interfaces |
| Quality | Stronger integration testing, CI reliability and production verification |
| Computer science | Data structures, algorithms and deeper problem-solving fluency |
| AI engineering | Agent workflows, retrieval, automation and context-aware development systems |
| Company building | Building reusable products and a sustainable software business |
|
Understand the domain Software becomes useful when the real workflow is understood. |
Make state explicit Permissions, transitions and ownership should be visible in the design. |
Verify continuously Tests, CI and runtime checks reduce assumptions before release. |
Build for change Good architecture makes the next feature safer, not merely possible. |
The common thread is architecture: networks, music and software all depend on relationships, timing, structure and controlled complexity. |
I am interested in conversations around:
|