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

AreaCore Focus & Expertise
FrontendReact, TypeScript/JS, CSS/SCSS, Next.JS, Vite/Webpack
BackendNodeJS, Python, BunnyJS, Java (Spring, Maven), REST/GraphQL/gRPC
ProductStrategic Engineering, Pragmatic Architecture, Industry 4.0
DevOps & TeamMentorship, CI/CD, Docker, Agile Leadership

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.

Detailed Tech Stack

Frontend Ecosystem

I keep a broad overview of the frontend ecosystem to choose the right tool for the team, not the latest trend.

  • Languages: TypeScript1/JavaScript, HTML5/CSS3 (SCSS, Less)
  • Libraries: React2, Redux, Zustand, Jotai, TanStack, NextJS
  • UI & Styling: Material UI3, Tailwind, @mui, Bootstrap, Responsive Design
  • Secondary/Legacy: Svelte, Angular, htmx, jQuery
  • Tooling: Nx, Cypress, npm/yarn/pnpm, Vite/Webpack, Jest, Figma, Accessibility, Prototyping

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 & Data Architecture

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

  • Primary Languages: Python and TypeScript/JS (Node.js4 - NestJS/Express.js, BunnyJS)
  • Enterprise Java: Spring Boot, Maven, WildFly/JBoss
  • Communication: REST APIs, GraphQL, gRPC
  • Persistence: SQL, MongoDB (go-to choice), Redis, portable data modeling

Infrastructure & Deployment

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

  • CI/CD: GitHub Actions, GitLab CI, Jenkins, TeamCity
  • Containerization: Docker, Nginx, Apache
  • Security & Quality: Sonar Qube/Qodana, CodeQL
  • Cloud & Scripting: Basic AWS, Bash, Batch (.bat)

Product & Leadership

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.

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

Team & Process

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

  • Leadership: Mentoring, onboarding, reducing “bus factor” 5.
  • Process: Scrum6, Waterfall, lifecycle ownership, roadmaps.

Working Method & Ethics

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

  1. On really huge projects it can be a little painful to use it due to a slow transpilation process, but in version 7.0 it will be the transpiler rewritten in Go. It will be MUCH faster. ↩︎

  2. With the advent of the React Compiler, I now consider manual memoization (useMemo/useCallback) an obsolete architectural overhead. ↩︎

  3. Material UI is a great library, but any deviation from the Material Design manifesto leads to inconsistency and is relatively costly. ↩︎

  4. I still believe JavaScript belongs where God intended: on the client side. NPM supply chain attacks only reinforce my caution. ↩︎

  5. Based on documentation, Post-mortems, Pair programming, and Code Reviews. ↩︎

  6. I use Scrum to align teams, then trim it down once things are running smoothly. No point in ceremonies that cost more time than they save. ↩︎