Skip to content
View miguelacano's full-sized avatar

Block or report miguelacano

Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
miguelacano/README.md

Miguel A. Cano

Senior Frontend Engineer · React · TypeScript · Next.js · Micro-Frontends

I build production-grade frontend systems with a focus on architecture, component quality, and UX that earns trust. I came to engineering through a decade in digital strategy, which means I think about users, not just components.


What I'm Focused On

  • Building modern React / Next.js applications
  • Designing modular architectures (micro-frontends, SDKs, distributed systems)
  • Applying SOLID principles in frontend systems
  • AI-augmented development workflows (LLM agents, code generation, test automation)
  • Secure-by-default engineering (sandboxing, validation, OWASP-aware design)
  • Improving release confidence through shift-left testing and trunk-based development

Active Projects

Cantura

A studio management platform for private music teachers. Built around instrument-scoped access control, repertoire assignment and progress tracking, and a guardian-participatory notes system inspired by Suzuki pedagogy. Production-shaped architecture from the start: service layer authorization, strict invariants, and a data model designed around user flows.

Stack: Next.js · TypeScript · Prisma · PostgreSQL · Tailwind CSS

Appogia

A music practice intelligence platform for structured practice tracking, audio session capture, and feedback loops between teachers and students. Currently in the architectural phase, defining service boundaries, event logging patterns, and idempotent async processing in preparation for audio storage and AI-assisted performance analysis.

Stack: Next.js · TypeScript · PostgreSQL · S3-compatible storage · pnpm monorepo


Engineering Philosophy

I approach engineering as systems design.

  • Prefer composition over inheritance
  • Design APIs and components around clear contracts
  • Optimize for readability and long-term maintainability
  • Treat documentation as a first-class artifact
  • Use AI tools intentionally to accelerate quality, not replace judgment

Strong engineering is not just about shipping features. It's about building systems that scale in complexity without collapsing under it.


AI-First Workflow

I actively integrate AI tools into development workflows:

  • Repository indexing for architectural context
  • Agent-assisted test generation
  • Automated code review feedback loops
  • Security scanning integration
  • Structured planning with design documents and agent validation

AI is a force multiplier when paired with strong engineering fundamentals.


Connect

Pinned Loading

  1. cantura cantura Public

    TypeScript