yegor256 podcast

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....

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/Qii3y...

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

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

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

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

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

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.

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

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 t...

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

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

The video is here: https://www.youtube.com/watch?v=ae6nFZn3auQ

"Where do you find inspiration for coding," I hear very often. The trick is simple: I try not to stay for too long with the same code base. I try to extract sub-module, libraries, or frameworks from the products I work with and make them standalone products. This is fun: making new products. The video is here: https://youtu.be/ygoWsvgXe1c

Very often our managers don't know exactly what we have to do. They don't have specific requirements, they don't know how to specify tasks for us. Is it bad? Many people complain and quit. I suggest the opposite strategy: you say and do what you think is important. Make your own requirements. The video is here: https://youtu.be/a_UEkcV9laA

This year we organize a competition for student researchers. If you are a student (MSc, BSc, PhD), you most certainly do some diploma work. When finished, publish your results at ACM/IEEE conference and send us a link. We may give you a reward. The video is here: https://youtu.be/53DCw1QyDRc

We all know how annoying are the recruiters who spam us instead of finding the right methods of approaching us carefully. Here is a quick summary of the advice I would give them all. Video is here: https://youtu.be/dlPk1AE2aQk

Every time I start a new book, an article, or a new software project, I spend a lot of time making sure it visually looks nice. Sometimes this process even takes longer than the writing itself. I'm kidding about this, but it's not so far from the truth. Visual representation of data/text is very important. The video is here: https://youtu.be/l4PhrB4AytY

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

Computer science is not so hard to do. If you are a professional software engineer, you can present your results in an academic way and publish them at one of those computer science conferences. You will get yourself a status of a researcher. This will only help you in your career. The video is here: https://youtu.be/ARwiHvTA4dc

When you deal with a weak and incompetent manager, who is not capable of finding a way to measure people's results objectively, you have to behave like an imposter. If you don't, somebody else will and the manager will think that this guy is the best guy in the team, no matter what are the actual achievements. Read the blog post: https://www.yegor256.com/2021/03/03/imposters-to-win.html The video...