Lab Director at Huawei, founder of Zerocracy, author of Elegant Objects, creator of Zold
M137: Don't ask your programmers to estimate, tell them how much you have
Asking your programmers to estimate how much time or money a software product would cost is a mistake. They don't know and can't now. They can spend all your money and still deliver an incomplete product. Because the product is never complete. Instead, tell them how much you have. They will do their best to deliver the most they can within the limitations.
The video is here: https://youtu.be/lgScAwsYWCc
M136: Any software product has an unlimited number of bugs
No matter how big or good is your software, it has an unlimited number of bugs, especially if we remember that maintainability bugs also are very important for the overall quality of a product.
This is my talk at TestCon: https://www.youtube.com/watch?v=aYXuK2do6FA
The blog post you may want to read: https://www.yegor256.com/2017/05/23/unlimited-number-of-bugs.html
The video is here: https://youtu.be/ZdHCrsQsoMI
M135: Don't ask for approval, educate them so that they make the decision themselves
If and when you want to convince your management to approve your idea, don't go there directly with a cold proposal asking for an answer. Instead, make a series of educational presentations, in order to help them understand the idea and agree with it. Then, they will come back to you and ask you to implement it. They may even forget who was the author. But the goal will be achieved.
The video is here: https://youtu.be/9ym5u4en0Tc
M134: Don't blame the situation for the mess in the code, it's only your fault
If the code is messy and dirty, blaming the situation is not correct. No matter what were the restrictions (both time, scope, and cost), your responsibility as a programmer is to deliver the code up to the quality expectations of the project. If you can't do that, you should inform the project beforehand. But don't blame the customer later.
The video is here: https://youtu.be/WKX8CUPuYvo
M132: Your pet projects are the best contribution to your resume
No matter how many big companies you worked for, your future employer will still pay more attention to your personal projects, especially open source. Well, provided the employer is savvy enough. Your personal code is much more valuable than the big name of some Facebook you have in your CV. They are just job places, but your code is something you managed to created. So, don't waste time and start your own pet projects now.
The video is here: https://youtu.be/_ga2tP3wZbI
M131: Be aware of conflict-of-interest concerns when you open source while being employed
When you work for a company and at the same time do open source development, you most certainly have a conflict of interest. The open-source is mostly for your own benefit, while the company expects you to give all your results to it. How will answer the questions when they ask you when your product is popular?
The video is here: https://youtu.be/TW4uxuiHjCw