yegor256 podcast
Yegor Bugayenko
Software developer at Huawei, founder of Zerocracy, author of Elegant Objects, creator of Zold
Episodes
Mentioned books
Mar 17, 2021 • 56min
Shift-M/46: Fair Management with Pim De Morree
Our special guest is Pim de Morree from https://corporate-rebels.com/
More about Pim: https://corporate-rebels.com/rebel/pim
Twitter: https://twitter.com/pim_de_morree
LinkedIn: https://www.linkedin.com/in/pimdemorree/
The video is here: https://youtu.be/VXbi5TXMsrY
Mar 1, 2021 • 8min
M164: Fixed-Price contracts are much worse than Time&Material
If you outsource part of your software development project to a third-party, you may think that the best type of contract to sign is Fixed-Price: you set the scope, they promise the time and price, they deliver, you check the quality, and you pay. It sounds right, but in reality, it'll be a disaster. Instead, always sign Time&Material contracts: you tell them how much resources you need, they give you a quote per hour, you manage them, they work for you, you pay every month. This is much more effective.
The video is here: https://youtu.be/xUALewcix44
Feb 17, 2021 • 9min
M163: If you as a manager don't punish wrong-doing, the team will punish you
It's your job as a manager in a software team — to identify wrong behavior and find ways to punish it. The best manager, of course, will configure the management system so that it will enforce the punishment. Average managers use guilt and emotions as tools for that. Bad managers are scared to even think about punishment.
The video is here: https://youtu.be/2lyz-CRGBwk
Feb 11, 2021 • 4min
M161: When punishment is justified in a software team?
Most of us are so scared now of the word "punishment" that all types of mistakes made by programmers remain unnoticed, very often. I believe, there are many types of mistakes that have to be punished. Everybody will win: the project, the people, and our customers.
The video is here: https://youtu.be/zJ_PqlMcYcE
Feb 9, 2021 • 4min
M161: It's not the competition that destroys a team, but unfair rules
Many of us believe that competition is not something a software team may need. Moreover, competition may destroy a team killing morale and promoting conflicts. This may happen, but not because the competition is a bad idea, but due to the misconfiguration of its rules.
The video is here: https://youtu.be/TyHCjKOFsBo
Feb 6, 2021 • 1h 5min
Shift-M/45: Risk Management with David Hillson, the Risk Doctor
The video is here: https://www.youtube.com/watch?v=L2vUKqEgdys
Feb 1, 2021 • 6min
M160: Traditional top-down planning doesn't work, try better alternative
Traditionally, you tell your team what needs to be done and then force them (or motivate) to do it. You basically try to make your plans their plans. It works sometimes in some industries, but doesn't work with us programmers: we are too spoiled and lazy. I suggest a better planning principle: you let your people decide how many awards they are going to earn and then build your plans on top of their selfish desires.
The video is here: https://youtu.be/vaFPNdNaOAY
Jan 28, 2021 • 7min
M159: If your objective is to keep the team intact, competition is not for you
Competition in a team works only if are ready to lose some part of your team, and very soon. If you don't want that to happen and your main objective is to keep the team intact and alive — competition will only do you a bad favor.
Jan 22, 2021 • 1h 14min
N3: Cyberpunk, русские хакеры, Твиттер и Трамп, цензура и ИИ, и Биткоин
Video is here: https://youtu.be/nenmlYhNM50
Jan 14, 2021 • 9min
M157: We must measure productivity, but using the right metrics only
Measuring the productivity of programmers to many of us seems like a dangerous process, which leads to a lack of value delivered. This is true, but only if you use the wrong metrics to do your measurements. Use the right ones and everything will be fine.
Video is here: https://www.youtube.com/watch?v=yZcNHZ_FJco
