Alex Korotkykh

@alexkor.bsky.social

CTO @ getpliant.com

Two runners broke the two-hour marathon barrier in London today. Genuinely impressive. But objectively, my 6-hour marathon is three times the effort. I’m still waiting for my press conference.

"You shouldn't use AI for coding, it can produce insecure, unscalable, unreliable code." You shouldn't cut vegetables with a knife — it can cut your finger. You shouldn't use a lightbulb — electricity can kill you.

Everyone's debating whether AI gets too powerful, too biased, or too regulated. The scenario I find most plausible for actually slowing it down isn't getting nearly enough airtime. Economics.

I’m from Ukraine but have lived in Germany for 12 years. I can’t call myself German yet, but I’m not fully Ukrainian either. Last time I was in Ukraine I ordered an Uber. The driver accepted, then called me immediately:

Software engineers who think their job is to write code are like civil engineers who think their job is to draw blueprints. The blueprint is not the bridge. The bridge has to stand up. Handle load. Survive weather. Be maintained by people who weren't there when it was designed.

Writing code is the part of the job most engineers actually love. It gives flow, clarity, a sense of accomplishment. Everything else — meetings, tickets, coordination — we tolerate for it. Now it’s the part getting automated. What’s left is everything we liked the least.

There’s a state where you’re not doing the work — not because you’re tired, just… not doing it — but you also can’t relax because it’s still hanging over you. Feels like a race condition. Only way out is through. Hate it.

Harry Potter movies were, at best, mid — and a poor substitute for what are actually incredible books. I’m tired of pretending otherwise. Hoping the new adaptation finally does justice to the books.

Fun fact about Pliant #3: Most startups can’t afford to “do tech right” at the beginning. Time to first release usually wins over everything else. In our case, external dependencies — vendors, licensing, legal work — bought engineering something rare: time. We used it.

Premortems are one of the most underrated reliability rituals. Instead of analyzing a failure after it happens, you gather the team beforehand and ask: “Imagine this project failed — what went wrong?” It’s much easier to spot risks before launch than to explain them after.

Fun fact about Pliant #2: All of our tech teams follow the same naming pattern: two words starting with the same letter — an adjective and a noun. We started with Fancy Features and Mighty Machines as placeholders until we came up with something better. Seven teams later, we didn’t

Fun fact about Pliant #1: In December 2020, when we issued our first card as a B2B payment card provider, the very first transaction was buying a giant plush pink unicorn 🦄 Priorities were clear from day one.