From idea to production without putting your business at risk your business
I design and build software that works in production: secure, maintainable, and ready to scale.
Clear objectives, small releases, and decisions you can defend.
No smoke, no invented metrics.
- Focus
- Product + engineering
- For
- Startups and small businesses
- How I work
- Iteration + feedback
- Built at
- CodeByMe
Selected work
Cases with context, decisions, and architecture. The original problem, the trade-offs we made, and what actually shipped to production (with verifiable results when it applies).
Problem: many technical portfolios fail to convert. Solution: business-focused narrative + technical proof to speed up hiring or project decisions.
Stack
- React 18
- TypeScript
- Vite
- Tailwind CSS
- Framer Motion
- Three.js
Architecture
Decoupled React + TypeScript SPA with minimal state and reusable sections.
Optimized loading and on-demand 3D to preserve performance.
Product view
- Decision-oriented messaging
- Real cases with context
- Architecture explained without hype
- Flow designed for contact
- Animations that support content
Evidence
- Bilingual content managed from /admin
- Strict typing and active linting
- Reusable section-based components
- Contact flow that actually delivers messages
Case study: CodeByMe (this site) →
Problem: desktop ELAN/TextGrid slows distributed teams. Solution: collaborative web editor with full interoperability and scalable annotation.
Stack
- TypeScript
- Next.js 15 + React 19
- PostgreSQL + Prisma
- pg-boss
- S3 / Cloudflare R2
- Whisper
- Auth.js v5
- Stripe
- Docker + Dokploy
Architecture
Modular Next.js monolith with a separate queue worker on PostgreSQL.
Audio stored in S3/R2 with signed URLs and a versioned export API.
Product view
- Layered editor with tiers and undo/redo
- Whisper-assisted transcription
- Import/export: EAF, TextGrid, RTTM
- Bulk ingestion via ZIP
- Workspaces with roles and templates
- Read-only sharing via token
- i18n: ES, EN, PT
Evidence
- Documentation for positioning, GTM, and runbook
- Export validated in 6 formats
- QA with Vitest + Playwright
- Prisma schema with ~30 models
- Production deploy: Docker Compose + Dokploy (VPS)
Case study: Cliptic — Collaborative audio annotation →
Problem: remittance flows are often opaque and slow. Solution: platform with clear pricing, end-to-end traceability, and operations ready for scale.
Stack
- Next.js (App Router + Server Actions)
- React
- TypeScript
- Supabase (PostgreSQL, Auth)
- Tailwind CSS
- Framer Motion
- Lucide React
- Vercel / Sentry
Architecture
Next.js + Supabase split into landing, transactional flow, and operations modules.
External integrations and cron jobs for traceability at scale.
Product view
- Real-time calculation with clear breakdown
- Cash or card delivery (MLC/CUP)
- Nationwide coverage in Cuba
- User portal with history and beneficiaries
- Centralized operations dashboard
- RBAC and secure authentication
- Cron-based automation
Evidence
- Conversion-oriented landing page
- Optimized 4-step flow
- Role-based operations dashboard
- SEO with JSON-LD
- Typed, reusable code
Case study: VeltroPay — Remittances to Cuba without friction →
Problem: local traffic often does not convert to bookings. Solution: platform that combines local SEO, booking engine, and daily operations in one panel.
Stack
- Astro
- React
- TypeScript
- Supabase (PostgreSQL, Auth)
- Tailwind CSS
- Nodemailer
Architecture
Astro + React for performance with a Supabase backend.
Notification/email APIs and modular architecture with code-splitting.
Product view
- Two-step booking engine with capacity control
- Unified panel: bookings, floor, CRM, menu, and events
- Post-booking automation (confirmations and reminders)
- Newsletter with anti-duplication control and rate limiting
- Local SEO with structured data and indexable content
Evidence
- Stack validated in production
- Dashboard with deferred loading
- Secure APIs with rate limiting and validations
- Active automations (cron, email, notifications)
- Configurable slot-based booking model
Case study: Restaurant platform — bookings and CRM →
Quality without posturing
You won’t find invented Lighthouse scores or random load graphs here. You will find explicit criteria you can challenge in a technical interview or a commercial proposal.
Accessibility with intention
Readable contrast, visible focus, and live regions where it matters (for example, the terminal). Without confusing motion with usability.
Performance with intention
3D canvas only as atmosphere; it pauses when out of view. Images and bundles are reviewed before adding visual wow.
Honest copy
No invented metrics and no promises you can’t verify. What’s published should be defensible in an interview or a proposal.
Maintainability
Content data separated from components, explicit types, and changes documented in OpenSpec when the scope warrants it.