Approach

Engineering and web development. One way of thinking.

See the process in action

I am a web developer with a background in mechanical engineering and professional experience in technical environments, documentation, teaching, processes and working with people.

Engineering taught me to observe systems, work with constraints and look for clear solutions. That mindset remains present when I build web applications, interfaces, dashboards and platforms.

Integrated trajectory

  1. Mechanical engineering
  2. Processes and documentation
  3. Technical problem solving
  4. Web development
  5. Functional products

02 · Process

How I approach a problem

Before choosing a tool, I review the need, context and constraints. The process makes that judgement visible.

  1. 01 · Input
  2. 02 · Control
  3. 03 · Flow
  4. 04 · Transmission
  5. 05 · Inspection
  6. 06 · Return

01 · Input / receive

Understand the problem

I identify the need before choosing a tool. The goal is to understand what the solution needs to resolve and for whom.

02 · Control / decide

Review constraints and data

Before committing to a solution, I review scope, information and data sources, access, permissions, constraints and project limits.

03 · Flow / organize

Design a structure

I divide the system into understandable screens, components and flows so information can be reviewed and evolved.

04 · Transmission / transfer

Prototype and implement

I turn the structure into a functional, reviewable interface, connecting components and data according to the defined scope.

05 · Inspection / verify

Validate before closing

I verify behavior, record relevant decisions and iterate from findings, not from a feeling of closure.

06 · Return / evolve

Maintain and evolve

A solution can continue through maintenance, fixes and phased improvements when there is a clear new scope.

InputSourceFlowOutcome

03 · Capabilities

What I can implement

These capabilities complement one another: an interface, its data, visualization, integrations and subsequent review belong to the same work.

02

Backend and data

Connecting frontend, backend, APIs and data sources through documented services and reviewable flows.

Evidence: industrial platform in development and public API projects.

03

Dashboards and visualization

Interfaces for reading indicators, tables, charts and process states without losing clarity.

Evidence: industrial monitoring web platform, subject to confidentiality restrictions.

04

Audit and evolution

Reviewing structure, inconsistencies, navigation and accessibility to correct and evolve a site in a controlled way.

Evidence: the evolution of this portfolio.

05

Analytics and integrations

Web analytics, forms, conversion links and integrations when scope and data sources allow.

Evidence: Google Analytics in KYK Webinar and personal projects with public APIs.

06

Engineering, processes and documentation

Reading constraints, requirements, decisions and technical communication as a basis for building reviewable solutions.

Foundation: mechanical engineering, teaching, coordination and technical client-facing work.

Applied

Technologies with demonstrated use

HTML, CSS, JavaScript, React, REST APIs, Git, GitHub and Google Analytics.

In real projects under development

Current work

Node.js, Express, web backend, dashboards and frontend–backend integration.

Being strengthened

Applied learning

TypeScript, PostgreSQL, MongoDB, Firebase, Tailwind CSS, Python, Django and Docker.

04 · Supporting tool

AI inside the process

I use artificial intelligence tools to research, prototype, debug and review documentation. I define objectives and constraints, run tests and validate final decisions.

05 · Limits and collaboration

Scope before promises

For projects using new technologies or with greater complexity, I first define scope, risks, data sources and validation criteria before committing to a solution.

I am open to web development opportunities, remote work, technical collaboration and freelance projects with a defined scope.

06 · Next step

The way of thinking is clearer when you see the work.

Explore projects and services, or let’s talk about a specific need.