devur

Generated by AI — may be complete nonsense.

I’ll be here if you want to build a service that automatically generates unique social media posts and visual assets from new e-commerce product listings

  • Open idea

Code for real work.

Five years ago I came into IT with a stubborn drive to build things that actually work and change something for the better. Solutions emerge from code that makes life easier. That’s the magic.

A short take on approach and stack — below.

I'm 24 years old, my path so far

  1. 2015

    Seems like...

    A computer isn’t only for entertainment. Awkward CMS tinkering introduced me to HTML, CSS, and PHP.

  2. 2016

    First blood

    Layout, content management, and even dabbling in graphics.

  3. 2017–2019

    Born for something?

    Finding myself and grappling with the absurdity of it all.

  4. 2019

    Do what you’re good at.

    Brutal try-hard; by year’s end my mindset crossed the threshold into engineering.

  5. 2020

    Project work

    First “product” experience. Lots of services, integrations, and learning from mistakes.

  6. 2021

    Full-time employee

    More time thinking than coding. More services, more integrations, more mistakes.

  7. 2022

    Single Responsibility

    Owning backend end-to-end for products. Heavy focus on infrastructure and architecture.

  8. 2024

    Solid snake

    Problem-solving crystallizes. The Laravel ecosystem makes sense.

  9. 2025

    REVOLT!

    Time to touch new tech. Learning NestJS and TypeScript. A real need to level up frontend.

  10. 2026

    Swiss army knife

    New projects on a new stack. R&D in spare time. To some extent… yes, that one.

Stack

  • Gitsince 2018
  • Linuxsince 2019
  • Laravelsince 2020
  • MariaDBsince 2020
  • Nginxsince 2020
  • PHPsince 2020
  • REST APIsince 2020
  • SQLsince 2020
  • PostgreSQLsince 2023
  • Caddysince 2024
  • NestJSsince 2025
  • Nuxtsince 2025
  • tRPCsince 2025
  • TypeScriptsince 2025

Approach

Engineering clarity. A way not to drown in your own code six months later. If a system can be simplified without hurting logic — I simplify it.

Straightforwardness. I’m comfortable in small teams focused on shipping. I value time and dislike performative busyness.

Predictability. My job is to build a clear, scalable backend that doesn’t need me on call 24/7 after launch.

About me

I’m a night owl. Not for show — it’s natural rhythm: when the world goes quiet, it’s easier to find flow and focus on hard logic.

I often spend free time on R&D side projects — a sandbox where I can fail, try “dubious” ideas, and learn new tech out of curiosity.

When I need to switch off — Chinese fantasy worlds. Systematic. Logical. A world that works in the reader’s head.

Let’s talk

If this resonates and you need someone who knows how to build systems — reach out and we’ll discuss the work.

Telegram