Skip to content
View FicLel's full-sized avatar
:shipit:
Working From Home
:shipit:
Working From Home

Highlights

  • Pro

Organizations

@KebabWarriors

Block or report FicLel

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

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

Report abuse
FicLel/README.md

Victor Martínez

Software Engineer · Backend & Distributed Systems

Santander, Spain
Node.js · TypeScript · DDD · Event-Driven Architecture · Cloud Systems


Engineering Profile

I design, modernize, and scale backend systems that support high-load environments and evolving business domains.

My work centers on:

  • Migrating legacy architectures into structured domain-driven systems
  • Improving performance and operational reliability
  • Enforcing architectural standards across teams
  • Designing distributed systems aligned with long-term scalability

I operate across architecture strategy, hands-on backend engineering, and DevOps-aware system design.


🏗 Architecture & System Design

flowchart LR
    Domain --> Application
    Application --> Infrastructure
    Infrastructure --> Cloud
Loading

Architectural Foundations

Domain Modeling

  • Domain-Driven Design (DDD)
  • Bounded Context definition
  • Aggregates & Repository patterns
  • Ubiquitous Language enforcement

Structural Architecture

  • Hexagonal Architecture
  • Clean Architecture principles
  • Dependency inversion
  • Infrastructure isolation

Distributed Systems

  • Event-Driven Architecture
  • Asynchronous processing
  • Microservices decomposition
  • Failure-aware boundaries

Engineering Standards

  • Test-Driven Development
  • Architectural code reviews
  • Standardization across teams
  • Legacy refactoring strategies

🔬 System Design Approach

1. Model the domain before writing infrastructure.
2. Protect the core with clear boundaries.
3. Keep external dependencies replaceable.
4. Design assuming failure.
5. Optimize after correctness and clarity.

🧰 Technical Stack

Backend Data Cloud DevOps Frontend
Node.js PostgreSQL Azure Docker React
NestJS MSSQL AWS Jenkins Vue
Elixir MongoDB Lambda GitLab CI Next.js
C# DynamoDB CDK CI/CD

🧠 Engineering Philosophy

Architecture is a business decision.
Performance problems are usually design problems.
Systems must scale without increasing operational stress.
Maintainability is a long-term competitive advantage.


🎯 Current Technical Focus

  • Event-driven system design
  • Resilient distributed architectures
  • Production observability
  • Legacy modernization at scale
  • High-performance backend services

📩 victorleal190@gmail.com
🔗 LinkedIn: Go Here

Pinned Loading

  1. musical-notes-organizer musical-notes-organizer Public

    Jupyter Notebook

  2. BlockChainExampleCoin BlockChainExampleCoin Public

    Proyecto en Python para explicar el funcionamiento de Blockchain

    Python

  3. cypher-algorithms-example cypher-algorithms-example Public

    C# 1 1

  4. schedule-service schedule-service Public

    TypeScript