Latest
Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Anti-Communism Week: Remembering the Writers Communism SilencedVesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own FaultGrow a PairYou’re Broke Because You Want to BeIt’s Called Work for a Reason!No Time for TactShut Up, Stop Whining, and Get a LifeWilliam Bessette: AI Enablement and Child Welfare TechnologyFree Book Planning Tools

Decision Making

Featuring Alexander Zhidkov on Leaders and Their Stories with Richard Lowe

Chapters

  • 0:00  Meet Alexander Zhidkov
  • 0:56  From the Soviet Union to Western Australia
  • 1:36  Punch Cards to AI
  • 2:48  Treating AI Like an Employee
  • 4:06  From Chatbots to Dark Factories
  • 5:25  Tell AI the Problem, Not the Steps
  • 6:39  Three or Four Clients a Year
  • 6:56  Small Business or Big Corporation
  • 8:16  Autonomy, Mastery, Purpose
  • 9:04  Ghostwriting as a Purpose
  • 10:02  Why We Love Sharing Knowledge
  • 12:23  Rubber Duck Debugging
  • 12:48  Results Are Driven by Luck
  • 16:31  Colossus: The Forbin Project
  • 17:50  Planning Matters, Plans Don’t
  • 19:06  Ancient Wisdom Says the Same
  • 20:33  Let People Fail
  • 22:41  The Risk of Ruin
  • 23:47  Sandboxing AI Agents
  • 25:10  Failure Is a Choice
  • 26:14  Leaving Corporate
  • 26:30  Prioritize and Limit Work in Progress
  • 27:36  Stop Starting, Start Finishing
  • 27:55  Wrapping Up

How do you make good decisions when results depend on luck?

TL;DR: What This Conversation Establishes

  • Alexander Zhidkov is a software developer and team lead, born in the Soviet Union and living in Western Australia, who now manages AI agents
  • The best way to use AI is to tell it the problem you have, not the steps to take
  • Results are driven largely by luck, so judge yourself on effort and preparation, not outcomes
  • Planning is important but plans are not: keep planning and keep adapting
  • Leaders should let people fail safely, sandbox the risk, avoid the risk of ruin, and finish one thing before starting the next

What You’ll Learn

  • How developers are moving from chatbots to supervising AI agents
  • Why telling AI your problem beats telling it what to do
  • Why tying your self-worth to results is a mistake
  • How to let a team experiment without risking ruin
  • How limiting work in progress helps you finish more

Referenced in this episode

Alexander Zhidkov on LinkedIn, the best way to get in touch with him.

Colossus: The Forbin Project, the 1970 film about an AI that takes over the world, reviewed by Richard.

The Birth of the Augmented Human, Richard Lowe’s book on what goes right when you use AI properly.

Richard Lowe: Good day, I’m Richard Lowe, and this is the Leaders and Their Stories podcast. I’m here with Alex, and he’s going to talk about all kinds of cool stuff, business-related stuff, and anything else we can think of.

So, Alex, why don’t you give us a short introduction as to who you are and what you do?

Alexander Zhidkov: Hi, Richard. Thank you. I’m a software developer, and I’ve been a software developer for many years now. I progressed through my career, and I was leading a team and managing people. And now, like a lot of software developers, we are managing AI agents.

That’s the shortest story I can tell.

Richard Lowe: Well, you can go longer if you want. It’s cool.

Alexander Zhidkov: No, that’s okay. I was born in Russia, actually the Soviet Union, born and raised there. I migrated to Australia about 20 years ago. I live in Western Australia, and it’s a beautiful place, and I love it. Not many people know about it, but it’s just incredible.

It’s quite a remote place, isolated, very nice, very quiet. I’m enjoying my life so far and keep working with software.

Richard Lowe: I began my career as a software developer also, only it was probably further back than you. I began on punch cards and paper tape, writing assembly language, and later BASIC and C and C++ and Fortran. So, the dark ages.

How do software developers keep up with constant change?

Alexander Zhidkov: That’s right, and that’s the challenge. It never stops. The change keeps coming. We’re always getting new languages, new patterns, new things to learn. It’s a continuous learning process, and it’s interesting and exciting, but it’s also quite challenging. You never settle in and keep doing what you’re doing.

You have to learn and you have to look forward.

And there’s a huge change happening now with AI. Lots of people are having trouble and complaining, but that’s what it is, and that’s what we signed up for as software developers.

How should you use AI as a digital assistant?

Richard Lowe: Well, I look at AI like this. You use it as a digital assistant.

You use it to help you out and do the things you think are dull or boring or that you don’t know how to do as well, and you do the brainy stuff, the stuff that makes more sense for a human being to do.

I use Claude a lot. Somebody broke into my website, so I told Claude I wanted a routine for WordPress that scans my system for everything possible where somebody could break in. It did that in about five minutes, I gave it parameters, and voila, program written, all done.

And it was pretty good.

Then I kept making it bigger and bigger. Search the config files, search the disk, search here, search there. Check the ports and check the network. It got wild, but it was all stuff people could break in on.

Then it would give me suggestions, and some were good and some were bad.

So it was kind of cool to be able to tell it, I want to do this, and then lead it like a software developer and treat it as an employee. It was my employee, basically, doing my coding.

What are dark factories in AI software development?

Alexander Zhidkov: That’s right. That’s what’s happening. And people are at different levels, obviously. We all started with chatbots: you ask a question and you get an answer. Then you go deeper and give it tasks, and you supervise it like a junior developer.

You’re always looking over their shoulder at what they’re doing, pushing them, and then they get better and you let them go a little bit on their own.

That’s the progression I see. At the cutting edge, AI is pretty much what they now call dark factories, doing all the work. You don’t tell it what to do. You tell it what problem you have.

Richard Lowe: Right.

Alexander Zhidkov: Not going into details and checking all the time, keeping it on a short leash. It is very capable at the moment of completing whatever task a person on a computer can do, which is exciting, but also kind of scary.

Should you tell AI what to do or what problem to solve?

Richard Lowe: Well, you hit the nail on the head. The way to use AI is to tell it what problem you’re having, as opposed to telling it what to do.

So the problem I’m having, let’s say, is I want to promote my books, and I’m having difficulty doing that because I’m an introvert. So help me do that.

One time it gave me a plan that I had to go out and do myself, and I said, no, no, no, I’m an introvert. Dude, listen to me. It said okay, made me some robots to do some things, and said just do this and this and this.

It was stuff I wouldn’t have thought of, but it was pretty plain Jane.

So I said, I want to really dive into the promotion and make it promote much better and much more. I don’t want to promote the way everybody else is promoting.

I kept doing that, back and forth and back and forth, and finally I had a plan, which I’m implementing now. And it’s not the same plan everybody else has.

Everybody does promotion. They have to, or they wither. If you don’t promote, you don’t get anywhere. You know that as a consultant. You have to promote. Fortunately for me, I charge enough that I don’t need more than three or four clients a year, and I’m doing great.

I don’t know how people survive having to get hundreds of clients a year when they’re tiny clients. I don’t do that.

Is it better to work for small businesses or large corporations?

Alexander Zhidkov: Yeah, that’s unfortunate, actually. I enjoy working with small and medium businesses, where there’s less bureaucracy and you can make a change easily. But that’s the problem: they don’t have much money. It’s much easier working for large corporations, where you can’t do much, but you get paid very well.

They have lots of money, and they don’t care as much as a small or medium business.

So I’m trying to combine doing what I love and enjoy, but you obviously have to look after yourself, maintain your lifestyle and get paid.

Richard Lowe: Getting paid is pretty crucial these days. I usually choose smaller businesses, because the larger ones tend to have the bureaucracy I can’t deal with. I don’t want to spend half my life dealing with bureaucracies.

I want to spend my life delivering the products I said I’m going to deliver.

What are autonomy, mastery and purpose at work?

Alexander Zhidkov: Yep, that’s it. That’s what the book says: autonomy, mastery, purpose, right? That’s what gives us satisfaction. You have to feel like you can make a change, you can make a decision, you have autonomy.

In a big company you have to get approvals, and there’s not much autonomy, so it’s not as enjoyable. And it’s nice to have a purpose, doing something that is actually helpful to people.

Richard Lowe: That’s absolutely true. That’s what I find. I like helping people deliver their message to their audience so it’s well understood. That’s what I do, and it’s a lot of fun.

Somebody comes to me and says they don’t know how to get their message out, and I make it so they do get their message out in book form.

And the pride they have when it’s done is pretty interesting to be around, because it’s their book. Even though I wrote it, it’s their book. It’s their ideas, their life, their stories, their everything. I’m not just making stuff up.

I do 20 hours of interviews sometimes, 30 hours on some books.

It’s fascinating, the process of getting that into a format they actually like, in their voice and their style. I like it. It’s fun. You mentioned purpose: I found that’s my purpose.

And it’s a much cleaner purpose, I think, than just working for somebody and turning this widget into that widget.

Why do people enjoy sharing what they know?

Alexander Zhidkov: That’s right, absolutely. It’s interesting how much people enjoy books and creating books. I think we have a desire to share knowledge, and I really enjoy sharing mine. Maybe not many people want to know it, and teaching is another skill.

But it’s interesting that we have the desire to share knowledge, even though, if you think logically, it’s more valuable to get knowledge from someone. Getting is what pays off, but we enjoy giving more.

Richard Lowe: Well, the giving is very valuable. The process of putting together a book or a blog series or whatever you’re doing makes you get your thoughts cohesive and your story working, and you might have to do research to figure out how you really did that.

It’s a different process than you’d think. You’re not just sitting down and writing a book.

Even if you do it on your own or with a ghostwriter, you’re sitting down and figuring out: how did I learn that? How did I recover from that mistake? And you’re passing that along to other people. To me, that’s really valuable.

I had a client who just wrote a book to help young people, kids in their teens, get through life. He’s building a whole thing around that because he wants to help people.

Well, the first thing he had to do was tell that knowledge in a way other people could understand. He had a lot of knowledge, but could he pass it along? That took us some time.

What is rubber duck debugging?

Alexander Zhidkov: Yeah, that’s what I find as well. Talking to people and explaining your ideas sharpens them. It’s valuable for me to keep iterating on what I’m thinking and explain it to someone, because then they poke a hole in it. They show you where you’re wrong, and that’s very valuable.

In software development we have the idea of rubber duck debugging, where you explain a problem to a toy, and in the process of explaining it, the solution comes to you. But you have to get it out. Otherwise you’re stuck.

Are results driven more by effort or by luck?

Alexander Zhidkov: Talking about books, I wanted to write a book, but I find it challenging to put words on the page. I had interesting ideas about decision-making. I got very interested in decision-making and how we make good decisions, and I think it’s the most important skill people can have.

And it’s not taught anywhere, not in school, not in university.

In my career I got good results and bad results, and people are always talking about results. In a job interview, we all say, oh, I’m results-oriented, I want to achieve results. But I find that to be a terrible idea, because results are driven by luck.

There’s so much luck in our lives. Our input is a tiny amount that we can actually control.

Even this conversation: we say we organized it, it’s all up to us. But we’re lucky we have electricity. We’re lucky we have the internet and all this technology, and that it all works. We’re lucky we were born in countries where we can speak English.

There is so much luck. What we can do is quite limited, but it’s also very important.

If you don’t put in good effort, you might get lucky, but you might not. You can increase your probability of being lucky. That’s my approach to life. All I can do is my best, but the results are driven by luck.

If I put in my best effort and get the result I was aiming for, I’ve still only done my best. There’s nothing more I can do, and I should be happy with that effort.

What matters is the effort you put in and your preparation, how much you learn and prepare. The result itself, you have to distance yourself from. Otherwise you’ll feel pain when you’ve done your best and just got unlucky, and you’ll feel down, which you shouldn’t.

On the other hand, you might not have done your best and just got lucky in the draw, and people are proud of themselves: oh, I’m so great, I achieved this and that, which is purely due to luck. Those are the ideas I find interesting.

They’re not quite mainstream, I think, but they help me a lot.

Richard Lowe: Interesting, yeah. Have you ever seen the movie Colossus: The Forbin Project?

Alexander Zhidkov: No, I don’t think so.

Richard Lowe: It’s way before The Terminator. It’s about this guy, Forbin, who creates an AI under the Rocky Mountains, the size of the Rocky Mountains. The AI takes over the U.S. military, teams up with the Russian version, and they take over the world.

The interesting thing is they build this AI with vacuum tubes and stuff like that.

It’s fun to watch because it’s so dated: vacuum tubes and reel-to-reel tapes and force fields. That was in the 1970s, and it’s fun watching from a 21st-century viewpoint a movie that kind of predicts things, but kind of not.

It’s fascinating to watch some of these old movies and see where they thought we would be. Sometimes they’re close. This one was close in some ways and way off in others.

Why is planning important if plans always change?

Alexander Zhidkov: Yeah, it’s just unpredictable, but you still have to try. Another thing I like saying is that planning is important, but plans are not. It’s good to keep preparing for the future and planning what you’re going to do and what’s going to happen.

But when you actually get there, the future wrecks the plan pretty much instantly.

So you don’t stick to your plan. You need to keep adjusting and adapting to a changing environment. That’s another idea I wanted to put in a book. People say stick to the plan. No, don’t stick to the plan.

Keep planning, but keep being flexible and adapting to the future.

Richard Lowe: Who was it? Somebody said you need to plan, but plans only last until the battle starts, and then the plans just disappear. I’m paraphrasing a bit.

Alexander Zhidkov: I think Mike Tyson said everybody has a plan until they get punched in the face, something like that.

Richard Lowe: This was a general. I think it was Eisenhower, maybe.

Alexander Zhidkov: When I got this idea and started digging into it, it all comes from ancient philosophies: Chinese wisdom, the Stoics, the Buddhists. They all keep talking about the same ideas. They’re just hard to grasp, I guess because they’re so simple.

Sometimes it takes going through life and actually experiencing things before you say, oh yeah, these people were right.

Richard Lowe: Yeah. I look back on my life and realize that when I was younger, in my teens and maybe even in my 30s, there were bricks that were smarter than me. I did so many stupid things. But I think you just have to go through that.

You have to go through the stupids.

Now I watch today’s younger people making their own stupid mistakes, not the same mistakes, and you just have to let them.

Sometimes you want to help them so they don’t hurt themselves, and then you just have to stand back and let them fall sometimes, because that’s the best way to learn.

How should leaders let team members fail safely?

Alexander Zhidkov: That’s right. And that’s a good principle for team leadership as well. When you get junior developers or junior team members on board, you have to give them the ability to fail. You have to allow them to run experiments. When you run an experiment, you cannot really fail.

It might have a positive or negative outcome, but you learn. You run an experiment to get the learning outcome, and you can’t fail at that.

As a team lead, I find the most important thing is to create an environment where people can run those experiments. It’s a safe environment for them to contribute and do their best, but there are also safeguards that keep them from crashing the whole thing.

That’s one of the challenges of leadership, I find.

Richard Lowe: Yeah. If I were to name things going wrong with the current generation, it’s that parents don’t want to let their children fail, and they have to let them fail. My parents let me fail all the time. Sometimes it hurt, physically, mentally, whatever.

But I learned from every one of those failures. Every single one. The one where I rode a bicycle off the roof into the pool: I learned, don’t do that.

Alexander Zhidkov: It hurt.

Richard Lowe: My parents didn’t let me do that. They would have been horrified. But I learned something from it. That’s just the way it is.

Now, I do agree that people need to be allowed to make mistakes, but you’ve got to make sure the mistakes they make aren’t going to affect the wider organization.

What is the risk of ruin?

Alexander Zhidkov: Yeah, that’s the idea of the risk of ruin. You always have a risk of ruin. You need to be able to fail, but not go beyond the point of recovery.

You’re always going up and down, up and down, but when you’re going down, it’s very important not to go under the water where you can’t recover. That’s the principle of managing the risk of ruin.

Richard Lowe: Yeah, exactly. What you want to do is set up those people in a silo almost, the people you manage, so they can fail, but not so the jet engines fall off the plane while it’s going across the ocean.

Alexander Zhidkov: That’s it. That’s right.

Richard Lowe: Maybe it fails in the simulator, but you don’t want it to fail in real life, because people are involved.

How do you sandbox AI agents to limit the damage they can do?

Alexander Zhidkov: Yeah, and it’s the same if you talk about AI agents. You put them in what they call a sandbox environment. You limit their exposure. So when they go off and do something wrong, the blast radius is contained, and the damage they can do is minimized.

Richard Lowe: Well, you just hit it on the head, and it’s a good analogy. Let’s say you were training somebody to defuse bombs. You don’t want that person to die defusing a bomb, because then they’re never going to learn anything again.

You want them to learn to defuse it, maybe make a few mistakes on fake bombs, and by the time they get into the field, they’ve got a good grasp of what’s good and what’s not.

Alexander Zhidkov: That’s how you build expertise.

Richard Lowe: Yeah. In the real world, failure sometimes is not an option. Like a rocket ship with people. It’s not an option.

Is failure always a choice?

Alexander Zhidkov: The way I think about failure is that it’s always a choice. You choose to fail. If you’re trying to do something and you keep trying, you always say, I haven’t achieved that yet. Yet is very important.

Richard Lowe: Right. That’s true.

Alexander Zhidkov: If you try this way and that way and you keep trying, you haven’t failed yet. But at some point you say, okay, I’m going to stop trying. I’m not going to do it anymore. So failure is always a choice you make.

Richard Lowe: And I’m not going to do it anymore is a perfectly valid outcome. Absolutely. Because maybe what you’re doing is beating your head on the wall. Maybe you’re in the wrong career. Maybe you’re doing the wrong thing. Maybe you don’t need to be a demolition expert.

Maybe following in your father’s footsteps is not the right thing to do.

But you might have to do a little experimenting and bash your head on the wall a few times to figure that out.

I spent lots of time in a technical career until 14 years ago, when I decided I’m done with that, I’m not going to work for corporate anymore, and started freelancing. That’s the best thing I ever did.

How do you prioritize when you can’t do everything?

Alexander Zhidkov: Good for you. You’re right, absolutely. We have limited resources, and you need to manage them. Your lifetime is limited. You can’t do everything; you have to choose. As a leader, it’s important to prioritize, and as a person as well. There are so many things you could do.

It’s a good skill to prioritize well: what’s the most important thing I can do right now?

Richard Lowe: Mm-hmm.

Alexander Zhidkov: That’s one challenge. Another is what we call limiting work in progress. Don’t jump around and do a million things. Don’t multitask. Have your to-do list with all the work you think you could do, prioritize it top down, start from the top, take one item and deliver it.

That’s how you move forward.

Otherwise you get distracted jumping from one thing to another and never finish anything. Another good saying I like is: Stop starting, start finishing.

Richard Lowe: That’s important.

Alexander Zhidkov: Finishing is way more important. So prioritize and execute.

Richard Lowe: Yep, yep. Well, we’ve been talking for a while, and I think it’s time to wind up. Do you have any last things you want to say to our audience?

Alexander Zhidkov: I enjoyed the conversation, and thank you for inviting me. If people want to get in touch with me, LinkedIn is the best way. Thanks for the good chat.

Richard Lowe: My pleasure. You have a great day. This has been the Leaders and Their Stories podcast. I’m Richard Lowe with The Writing King. I have two or three of these a week, so keep checking and you’ll find more here.

Quotable moments

You don’t tell it what to do. You tell it what problem you have. — Alexander Zhidkov
Share on X
Results are driven by luck. Our input is a tiny amount that we can actually control. — Alexander Zhidkov
Share on X
Planning is important, but plans are not. — Alexander Zhidkov
Share on X
When you run an experiment, you cannot really fail. It might have a positive or negative outcome, but you learn. — Alexander Zhidkov
Share on X
Failure is always a choice you make. — Alexander Zhidkov
Share on X
Stop starting, start finishing. — Alexander Zhidkov
Share on X

From the author
The Birth of the Augmented Human by Richard Lowe

The Birth of the Augmented Human
The Death of Thinking mapped the problem. This one maps the other path: the practices that keep your own thinking sharp when you work with AI, and what they build over time.

Frequently Asked Questions

Who is Alexander Zhidkov?
Alexander Zhidkov is a software developer who has led development teams and now, like many developers, manages AI agents. He was born and raised in the Soviet Union and moved to Western Australia about 20 years ago. He is interested in decision-making and wants to write a book about it. He can be reached on LinkedIn.
Why does Alexander Zhidkov say results are driven by luck?
Alexander Zhidkov points out how much of any result depends on things nobody controls, from electricity and the internet working to where a person was born. The part a person controls is effort and preparation. He judges himself on doing his best, because good effort raises the odds of a good result without guaranteeing it, and taking credit or blame for luck leads to pride or needless pain.
What is the risk of ruin?
The risk of ruin is the chance of a loss so large you cannot recover from it. Alexander Zhidkov applies it to teams and AI agents: let people and agents experiment and fail, but limit the blast radius with safeguards or a sandbox so a failure never goes past the point of recovery.
What does limiting work in progress mean?
Limiting work in progress means not multitasking or jumping between a million things. Alexander Zhidkov keeps a to-do list, prioritizes it top down, takes one item from the top and delivers it before starting the next. His summary: stop starting, start finishing.

Your story could be a book

Every leader I interview has a book in them. If you’ve spent a career learning what works, let’s talk about turning it into the book that outlasts the work.

Discuss your bookMore interviews

About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment