yegor256 podcast

Latest Episodes:

M179: Calibrated Achievement Points (CAP) to measure R&D productivity Oct 18, 2021

Show notes

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

N10: GitHub от Мишустина, iPhone 13, Умные очки, и Линус Торвальдс Sep 29, 2021

Show notes

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

M178: Try to focus your team on artifacts and their delivery status Sep 27, 2021

Show notes

Proper management is not something any team can afford. Here is a simplified framework, which gives you enough control over project affairs and at the same time doesn't bother the team too much. I called it SIMBA since it's a Simplified Management By Artifacts. The blog post is here: https://www.yegor256.com/2021/09/09/simba.html The video is here: https://youtu.be/939ntzufGB0

M177: Auto-formatters do more harm than good for programmers Sep 13, 2021

Show notes

Using auto-formatters to make your code look nice is a bad idea. Mostly because they won't teach you anything about code quality. Instead, always format your code manually. This is how you learn a lot about quality and good programming practices. The video is here: https://youtu.be/NoBE-WNIVVs

Shift-M/49: Greg Young about Software Design Sep 09, 2021

Show notes

The video is here: https://youtu.be/JER03qMCmIk

N9: Codex, Приватность, Дипфейки, Windows 365, Удаленка Sep 04, 2021

Show notes

Видео здесь: https://www.youtube.com/watch?v=weriC7HBuJo

M176: Often digital discussions don't work because there is no decision making process defined Aug 30, 2021

Show notes

Very often, as far as I can tell, programmers are not willing to participate in digital discussions (tickets, chats, boards) because they are afraid of bullying: their decisions may and will be criticized without any predefined rules. The solution is simple: make sure your team has a structured process of decision making, with explicit roles and permissions.

Shift-M/48: Jeff Atwood about knowledge management in software teams Aug 23, 2021

Show notes

Jeff Atwood is an American software developer, author, blogger, and entrepreneur. He writes the computer programming blog Coding Horror. He co-founded the computer programming question-and-answer website Stack Overflow and co-founded Stack Exchange, which extends Stack Overflow's question-and-answer model to subjects other than programming. Jeff's blog: https://www.codinghorror.com

M175: When the customer asks you to convince them, just don't Aug 13, 2021

Show notes

Say you are an architect, and your customer or a product owner asks you to explain your technical decisions, you may immediately jump into explanations. Don't do that. There must be a clearly drawn line between your territory of responsibility and authority and theirs. They define requirements for the product you develop, you make technical decisions according to the requirements. You don't need to explain anything. The video is here: https://youtu.be/WapJducA2NY

M174: Your personal goals go first, team and project goals next Aug 10, 2021

Show notes

Your personal goals must be much more important for you than your project and your team's ones. Of course, the team will try to make you sell your soul to them, but you must not forget about your long-term objectives. The video is here: https://youtu.be/rR4UFPvAulI

Our TOPPODCAST Picks

Follow Us

Stay Connected

Related Podcasts

Links

Stay Connected