Oleksandr Korotun

[ Press K to open command palette ]

Bringing complex user interfaces to life

Frontend JavaScript developer focused on scalable architecture, polished UI, and real business impact

Current Stack

  • TypeScript
    01
    TypeScript

    Superior type safety for large-scale apps

  • React
    02
    React

    Component-driven UI development

  • Next.js
    03
    Next.js

    The React framework for production

  • Tailwind CSS
    04
    Tailwind CSS

    Utility-first styling system

  • Framer
    05
    Framer Motion

    Declarative animation library

  • GraphQL
    06
    GraphQL

    Relational data querying

Projects

A selection of work I've built and collaborated on

  • 001

    NOISM Academy

    Production course platform for selling video programs online. I owned the frontend architecture, payment integration, CMS modeling, and authentication flows while adapting to evolving business requirements over time.

    • TypeScript
    • React
    • Next.js
    • Tailwind CSS
    • Framer Motion
    • Stripe
    • GraphQL
    • Hygraph CMS
    • Zustand
    • Nodemailer
    • Vimeo SDK
    • FFMpeg
  • 002

    NOISM Hairculture

    Multilingual business website built for a growing beauty brand. Focused on SEO, structured content, typography, and scalable frontend architecture while collaborating closely with non-technical stakeholders.

    • TypeScript
    • React
    • Next.js
    • Tailwind CSS
    • Material Tailwind
    • Framer Motion
    • Firebase
    • Resend
    • React Email
  • 003

    Forecast Storm

    Modern weather dashboard built with latest Next.js stack. Focused on clean architecture, data fetching strategies, PWA capabilities, and polished UI implementation and terminal user interface for standalone cli installation.

    • TypeScript
    • React
    • Next.js
    • Tailwind CSS
    • Weather API
    • Geo API
    • Astro API
    • Shell Script
    • CLI
    • Terminal UI

How I Build Things

I usually start by understanding the business goal and constraints, not just the feature request. Most of my work has been on evolving products, so I’m used to building with change in mind rather than aiming for a “perfect” first version.

On the technical side, I prefer simple, maintainable solutions:

  • 01
    Clear Boundaries

    Modular components that do one thing well and are easy to replace.

  • 02
    Predictable State

    Managing data flow so the UI is a direct, reliable reflection of the logic.

  • 03
    Scalable Styling

    CSS systems that allow for rapid UI iteration without technical debt.

Pragmatic Iteration

04

I’m comfortable refactoring existing codebases — improving them when necessary while avoiding over-engineering. My path is usually: Ship the simplest viable path today, and improve later as requirements clarify.