yegor256 podcast

Andy Hunt is a writer of books on software development, co-author of "The Pragmatic Programmer," one of the 17 original authors of the Agile Manifesto, and a founder of "The Pragmatic Bookshelf" publishing agency. The video is here: https://youtu.be/zebqDkVfY-g

Chief Technical Officer (CTO) is usually the highest technical position, where usually is a person who doesn't really remember how to write software code. A better setup would be with a CTO who codes every day and delegates management to Project Managers. Video is here: https://youtu.be/b_w85hL2o04

Developing a software product and maintaining it are two different activities, even though both are very important. Developers and maintainers are people of different types and if you want to keep your best developers in the project, don't allow them to become maintainers. The video is here: https://youtu.be/_BbgpugwpEI

Some of us think that the functionality of a product comes first, while the build pipeline (testing, coverage control, static analysis, style checking, deployment) goes next. Moreover, some of us believe that functionality is the foundation of a house, while the build is more like a decoration. I strongly disagree. Video is here: https://youtu.be/TcD6jJKaLcg

Video is here: https://youtu.be/NLNVkvnrr3Q

When you are young and hungry for attention, you make open source products. They give you appreciation and recognition faster than anything else. When you grow up and become known for the products you created earlier, you lose interest in open source and give space to next-generation attention seekers. Thus, let's appreciate their work to keep new products coming. The video is here: https://youtu.be/eyx69afklkY

What do you do with those who don't deliver almost anything except promises? Do you try to motivate them, discipline, organize, find better tasks for them? I suggest a better strategy: just ignore them. This is how you will save your time and energy for those who deserve your attention. This is how you help your team achieve better results. The video is here: https://youtu.be/KvwEKA4Owuc

Many programmers love to use pre-commit hooks to run the build and test the code before it gets to the repository. I believe it's a bad idea for two reasons.

Most of us believe that it's impossible to measure the productivity of programmers, researchers, software experts, and other "talents". I believe it's possible. Here is a simple framework, which has experimentally proven its effectiveness. Try it out in your team. The blog post is here: https://www.yegor256.com/2021/10/12/calibrated-achievement-points.html The video is here: https://youtu.be/Qii3yrQJdHs

Video is here: https://youtu.be/9bRCNcMox4g