Every morning I record a short video about software development. Subscribe and stay tuned!

Mornings!

In order to do the project right, you need the right person, right? Wrong! This type of thinking doesn't help at all and only leads to failures. It's the management that needs to be "right," not its people. Watch this morning video about this problem: https://www.youtube.com/watch?v=SSZnloEHeOk

M29: Instead of finding the right architect, find a way to manage the architect right

The average salary of american workers is growing 1% every year, while the paygap between similar jobs is decreasing. What do I think about this trend? Does it sound like people are getting more every year and it's good? Not at all. This trend is completely against what Zerocracy is fighting for: unequal pay for unequal contribution. We want to work with free people, who get what they deserve because of their work, not because of their place in the company. Meritocracy is yet another name for the movement we are leading now in the industry of software development.

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

M30: Pay equality and smaller pay gap mean only one thing: the management is weak

Do you know what micromanagement is? It's when your manager is telling you exactly what you have to do right now in order to achieve the results he or she wants. The micromanager doesn't trust you and that's why wants and needs to control every step you make. It's annoying and unproductive, but it's inevitable unless you have small tasks and a transparent and unambiguous system of rewards and punishment.

The full video is here: https://youtu.be/0Jte_LGR5Zk

M32: Micromanagement happens when tasks are big and motivation is not explicit

Proper management is very rare, happens only in some companies. Others are treating people like office slaves, expecting them to do stay in the office instead of delivering results. What do you do when you happen to be hired by such a company? How do you change it? How can you improve your team and motivate your management to shift to better management practices, like microtasking, paying by result, etc? You can't! And you shouldn't even try. 

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

M33: No don't need to be loyal to your employers, use them for your own good!

I know so many testers who think that they are QA engineers. They are so wrong that I decided to record a video about that. Testing is about breaking the software and finding bugs. QA is about watching the entire software development process and improving its quality indicators. They are two absolutely different activities.

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

M34: Testing and Quality Assurance (QA) are two entirely different things!

Technical debt is a huge problem, when it is, well ... huge. What usually happens is this: we start a project, we work on its "prototype," we wait until it is fully ready, and then we start thinking about unit tests, continuous integration, and build automation. But it is too late because the product already is too big. The problem is that we hold the product in the prototype mode for too long. I believe that two weeks is the maximum a prototype should take. After that, it's a normal product, not a proof-of-concept anymore.

The video is here: https://youtu.be/4MP3xXGrpCY

M88: If you are working on a prototype for longer than two weeks, you are doing it wrong

Software developer at Huawei, founder of Zerocracy, author of Elegant Objects, creator of Zold

M88: If you are working on a prototype for longer than two weeks, you are doing it wrong

@yegor256