TECHNICAL MAP

My SKILLS

The technologies, criteria and systems I use to build maintainable, fast and scalable digital products.

real notes, visible priorities

Honest positioning

The stack is not a medal collection

I do not present this stack as a collection of trophies. I present it as a working system: technologies I know how to connect to build real products.

connected technologies, not trading cards

Judgment

Technology with intent

Every tool should explain a decision: speed, maintainability, architecture, content, security or automation.

Delivery

Quality from the start

SEO, performance, accessibility and deployment are not final layers; they shape how the solution is planned.

Evolution

Visible learning

The portfolio separates what is applied, what I am consolidating and what I am still expanding to avoid inflated signals.

Real classification

Capabilities without invented percentages

I prefer usage context over numeric bars. A technology's maturity depends on where it has been applied and which problem it solves.

Applied in projects

Technologies already connected across product, content, architecture, technical quality or delivery.
  • JavaScript client interaction and logic
  • TypeScript interfaces and contracts
  • React applied components
  • Astro portfolio and i18n
  • C# backend and rules
  • .NET APIs and architecture
  • PostgreSQL product data
  • Docker reproducible environment
  • GitHub Actions CI and delivery
  • Railway staging and deployment
  • Tailwind visual systems
  • SEO indexable structure
  • Accessibility reviewable interaction

In consolidation

Pieces with real practice that I keep strengthening with more operational and product judgment.
  • Python useful automation
  • Whisper applied transcription
  • MySQL complementary data

Actively expanding

Complementary technologies I keep visible without presenting them as closed expertise.
  • PHP previous context
  • Java complementary base

IN WORK EXPERIENCE

Technologies and tools used in real professional context.
  • Vue professional frontend
  • Astro sites and content
  • SEO real optimization
  • Claude Code development assistance
  • BMAD agents agent orchestration
  • Codex technical editor support

Layered map

Capabilities that connect

The page separates work areas, but the real intent is connecting them: interface, data, backend, deployment, SEO and automation.

Current distribution

Relative weight of my technical areas

An editorial reading of the profile's current focus: not scientific precision, but a clear view of where my technical work carries more weight right now.
  1. Frontend interfaces, components, visual experience
    28%
  2. Backend APIs, logic, architecture
    24%
  3. SEO / Performance visibility, semantics, optimization
    16%
  4. DevOps / Deployment deployment, CI/CD, environments
    12%
  5. Automation flows, integrations, efficiency
    10%
  6. Applied AI assistants, productivity, processes
    10%

Frontend

Interfaces do not live in one file.

I treat the interface as a system: components, states, real responsive behavior, readable content and details that hold up as it grows.

components, state, responsive and semantics
  • React
  • Astro
  • TypeScript
  • JavaScript
  • Tailwind
  • Maintainable components
  • Semantic HTML
  • Responsive states
  • Accessible interaction

Backend

Logic needs architecture too.

Backend work is a product boundary: APIs, validation, authentication, models, responsibilities and rules that should survive the frontend.

contracts before screens
  • ASP.NET Core
  • C#
  • API design
  • JWT
  • Validation
  • Clear contracts
  • Layer separation
  • Server-side rules
  • Security by default

Data

Data shapes the product.

A clean interface needs intentional data: understandable entities, clear relationships and queries that do not block growth.

the database also tells a story
  • PostgreSQL
  • MySQL
  • Modeling
  • Queries
  • Persistence
  • Readable models
  • Clear relationships
  • Prepared data
  • Traceability

DevOps / Deployment

Working locally is not enough.

Delivery needs reproducibility, environment variables, CI, prepared staging and a minimum operational reading.

delivery as part of the product
  • Docker
  • GitHub Actions
  • Railway
  • Env variables
  • CI
  • Reproducible build
  • Prepared staging
  • Secrets outside frontend
  • Delivery automation

SEO / Performance / Accessibility

A website should be understood by machines too.

Technical quality connects metadata, semantic structure, mobile-first speed, visible focus and content that can be indexed and reviewed.

quality before the checklist
  • Technical SEO
  • Performance
  • Accessibility
  • Structured data
  • Responsive
  • Hreflang
  • Sitemap
  • Focus states
  • Mobile-first loading

Automation / Applied AI

Less manual work, more workflow.

Automation and applied AI make sense when they reduce real friction: intake, transcription, routing, notifications and operational handoff.

automating without selling magic
  • Automation
  • Applied AI
  • Python
  • Whisper
  • Workflows
  • Clear flows
  • Structured payloads
  • Handoff
  • Measurable assistance

Applied process

From design to a production system

The stack matters because of how it moves across phases: a visual idea becomes connected to data, backend, deployment and useful automation.

Connected evidence

Where this stack is applied

Projects work as application examples, not as a closed list or a place for invented metrics.

Project

KORUS

in progress

Flagship case for connecting React, modular backend work, PostgreSQL, Docker, CI and product judgment.

  • React
  • .NET
  • PostgreSQL
  • Docker
  • GitHub Actions
  • architecture

Project

JustWriteIt

in progress

Productivity tool where writing, transcription, TypeScript, Python and Whisper come together.

  • TypeScript
  • Python
  • Whisper
  • Applied AI
  • productivity

Project

Portfolio

current

Editorial system with Astro, i18n, SEO, performance, accessibility, motion and content architecture.

  • Astro
  • SEO
  • Motion
  • i18n
  • Accessibility
  • responsive design

Project

Link Shortener App

possible project

Compact surface for demonstrating API work, data, validation, security, analytics and redirects.

  • API
  • Security
  • Analytics
  • Redirects
  • validation

Next page

Review projects or open a conversation

To check the stack in context, the natural next step is jumping to projects, reading the profile or opening contact.