Written by working developers

About

We're four working developers. We build and maintain real products across the web, backend, cloud, and AI stack, and we started ProdStories to write down what actually happens along the way.

Most of what we learned didn't come from tutorials. It came from production bugs, bad architecture decisions, tools that looked great in a demo and failed in a real repo, and the fixes that finally held. That knowledge usually stays in private chats and old commits. We want to put it where other developers can find it.

Yaroslav Makovskyi

Yaroslav Makovskyi

NextJS / NestJS Developer

Full-stack developer currently residing in Germany with 2 years of hands-on experience building scalable web applications using NextJS and NestJS.

Presently dedicating my time to personal engineering projects and self-directed creation out of a genuine passion for coding.

When away from the screen, you'll likely find me out for a long walk, enjoying a good local beer, or soaking in the atmosphere at Oktoberfest.

Yuliia Svitlychna

Yuliia Svitlychna

Frontend Engineer (React / NextJS)

I'm a frontend engineer who works mostly in React and Next.js. I like apps that are pleasant to look at, and I know that good looks come from the structure underneath: clear component boundaries, predictable state, and styles that don't fall apart on the third redesign.

My daily tools are TypeScript, TSX and SCSS. When a feature needs an API endpoint or a schema change, I write it myself. I've shipped backend code in NestJS with PostgreSQL, so I can take on full-stack work when a project needs it.

I've also brought the same approach to WordPress projects: typed code, component thinking, and modern layout in an ecosystem that doesn't always encourage it.

Sometimes I use Claude Code, but carefully. I read what the agent writes before it gets merged, and I'm skeptical of anything that looks right but hasn't been tested. On ProdStories I write about frontend architecture, modern CSS and layout, Next.js in production, and where AI coding agents actually help a frontend developer and where they only make more work.

Away from the screen, I do beadwork: small patterns built one bead at a time, which turns out to be not that different from layout. I also have a lot of cats, and every one of them believes my bead box is a toy box.

Yevhen Omelianenko

Yevhen Omelianenko

Node.js / Python & AI Engineer

I started as a web developer and gradually moved deeper into AI. My background is in Computer Science and Technology, which I studied at Zaporizhzhia National Technical University.

For the last two years I've worked on a wide range of projects built with NestJS and Next.js. Different clients, different domains, different codebases. That variety taught me to get productive in an unfamiliar project quickly, and to notice which patterns hold up across all of them.

Most of my attention now goes to AI, and I work with it from two sides. As a user, I code with Claude Code and Codex daily and keep testing where each one helps and where it gets in the way. As a builder, I write my own agents in Python and ship them into real projects, which is a very different job from prompting an agent someone else built.

Serhii Zubkov

Serhii Zubkov

Node.js / Python & AI Engineer

I studied physics, but I've spent my whole career writing software. I started freelancing in 2012 and worked on many different projects for many different clients. In 2020 I moved to Node.js, and it has been my main backend platform since then.

Today I maintain real production projects built with NestJS and NextJS, running on PostgreSQL, Redis, and RabbitMQ. On ProdStories I write about what that work actually looks like: the architecture decisions, the queues and caches that misbehave, and the fixes that held up in production.

In 2024 I started working seriously with AI and machine learning. My background helps here: I studied at the Faculty of Physics at Zaporizhzhia National University from 2005 to 2011, and the math from those years is finally paying off. I'm now learning Python, LangChain, and LangGraph, and exploring machine learning, data engineering, and computer vision.

I write about this part as a learner, not an expert. You'll see what I tried, what I misunderstood, and what finally worked, so you can skip the dead ends I already hit.