Skills and Expertise

This section reflects technologies I’ve used in real projects, not everything I’ve ever tried. I regularly explore new tools out of curiosity; some appear in the Learning section, which I started documenting only recently.

#TL;DR Summary

I focus on building friendly, intuitive interfaces. I am not afraid to challenge requirements or propose changes, but I always prioritize real business value and common sense.

#Frontend Stack

• Primary: TypeScript¹/JavaScript, React², HTML/CSS (SCSS, Less)
• Secondary/Legacy: Svelte, Angular, htmx, jQuery
• Supporting tools: Material UI³, Tailwind, Bootstrap, TanStack, Nx, Cypress, Jest, …

I keep a broad overview of the frontend ecosystem to choose the right tool for the team, not the latest trend. I generally prefer PWAs to React Native, though I plan to evolve some personal projects into native mobile apps.

I have a genuine appreciation for maintaining legacy applications from the “pre-modern” era. Greenfield projects are cute, but I’m the guy you call when the reality of legacy code hits and you need to improve usability without breaking business continuity.

#Back-End & Architecture

• Languages: Primarily Python and TypeScript/JS (Node.js⁴ - NestJS/Express.js), with strong experience in Java (Spring Boot, Maven)
• Foundations: Earlier work in Pascal, C/C++, and PHP

While I can deliver backend services, my focus is now frontend-oriented architecture—API design, integration, and meaningful error handling rather than backend-heavy development.

#Data & Persistence

I treat databases as replaceable components and focus on portable data models that work across relational, NoSQL, and cloud systems, avoiding vendor lock-in unless performance truly requires it.

While MongoDB is my go-to choice, I’m genuinely drawn to Redis—finding a project that utilizes it would definitely catch my eye more than a traditional PostgreSQL stack.

#Infrastructure & Deployment

• Scripting: Bash, Batch (.bat), OS-agnostic
• CI/CD: GitHub Actions, GitLab CI, Jenkins, TeamCity
• Tools: Docker, Nginx, Apache, basic AWS, Sonar Qube/Qodana or CodeQL

Not a DevOps specialist, but fully self-sufficient with pipelines and deployments—preferably as little as possible.

#Product & Domain Experience

I’m a frontend specialist with a full-stack background. Years of building systems end-to-end allow me to focus on usability, maintainability, and pragmatic technical decisions.

• Customer-facing products: Translating business needs into clear technical solutions
• Strategic UI engineering: Solving UX problems, not just changing visuals
• Industry 4.0: Deep experience with DAQ systems and industrial environments

#Team & Process Leadership

• Team leadership: Mentoring, onboarding, decision-making
• Process: Scrum⁵, Waterfall, lifecycle ownership
• Team stability: Reducing bus factor, improving knowledge sharing⁶
• Stakeholders: Roadmaps, consulting, execution

I aim for stable teams with shared ownership, no single points of failure, and code written for our future selves.

#Working Method

Approach for delivering elegant, maintainable code that adds lasting value.

• Pragmatic Architecture: Apply Clean Architecture and DDD to keep business logic separate from UI frameworks.
• State of Mind: Structure apps by 12-Factor App principles for consistent environments and predictable deployments.
• Quality over Hype: Select tools based on stability and performance, not trends.
• Technical Debt Management: Prevent debt via continuous refactoring and clear documentation.
• Modern Versioning: Use Git with Semantic Versioning, automated CI/CD, and changelog generation.
• Ethical Engineering: Follow the ACM Code of Ethics and support Open Source when possible.