Muebles JYN Control
Internal system to run furniture business operations: projects, clients, progress logs, payments, files, and key dates.
- Next.js
- React
- Tailwind CSS
- Prisma
I build scalable and secure web applications for real business needs
Full Stack Software Engineer focused on backend systems, APIs, cloud delivery, and security-aware engineering.
Real-world projects across web applications, internal systems, and e-commerce with focus on architecture, scalability, and security.
Internal system to run furniture business operations: projects, clients, progress logs, payments, files, and key dates.
Bilingual corporate website with a manageable product catalog and private admin panel for categories and items.
Single-page static website designed to showcase services and portfolio while converting visits into WhatsApp bookings.
Furniture online store with public shopping experience, customer account area, and admin panel for orders, payments, products, and inventory.
Web app to track work days, calculate payments including overtime, manage project templates, and export reports.
Engineering Notes
Technical notes on Full Stack development, backend architecture, and applied security in real projects.
View all articlesA fast site isn't a technical whim: it reduces friction and builds trust.
Read articleI design and implement complete web applications with frontend, backend, and database, prioritizing maintainability and long-term evolution.
I build backend services with validation, role-based access, clear business rules, and reliable third-party integrations.
I work with modular architecture, clean coding standards, CI/CD workflows, and technical decisions that reduce long-term debt.
I integrate validation, access control, session handling, and OWASP-aligned secure defaults into core product flows.
Principle
Good design decisions reduce long-term technical debt.
Risk avoided
Jumping straight into code often creates coupling, scope drift, and expensive refactors.
Execution approach
I define domain boundaries, data flow, integration contracts, and stack decisions before implementation starts.
Expected outcome
More stable systems, faster iteration cycles, and safer feature growth over time.
Principle
Critical logic should live in the server layer, not UI assumptions.
Risk avoided
Without strict validation and contracts, inconsistency appears across clients, services, and data stores.
Execution approach
I centralize business rules in services/use-cases, validate payloads, and protect actions with role-aware authorization.
Expected outcome
Reliable flows, fewer production defects, and better technical traceability.
Principle
Security works best when embedded in design and implementation.
Risk avoided
If security is postponed, controls are expensive to retrofit and risks remain hidden longer.
Execution approach
I apply input validation, access control, secure session handling, baseline hardening, and risk review in key flows.
Expected outcome
More robust systems, reduced attack surface, and stronger operational confidence.
I review context, business goals, constraints, and risks before selecting architecture or tools.
I define architecture, stack, scope, and delivery roadmap based on impact, complexity, and operational priorities.
I implement by modules with quality gates, validations, and secure-by-default principles, delivering usable increments.
I deliver documentation, operational recommendations, and a clear next-step plan to scale safely.