Yegor Bugayenko Famous Quotes
Reading Yegor Bugayenko quotes, download and share images of famous quotes by Yegor Bugayenko. Righ click to see or save pictures of Yegor Bugayenko quotes that you can use as your wallpaper for free.
It's impossible to change the management system without changing the managers who built it. The management is the product of people who created it.
The higher the price of information in a software team, the less effective the team is.
Fixing the system without fixing people that work in it would be a huge trauma for them; they will do everything they can to prevent it from happening.
We, newbies and young programmers, don't like chaos because it makes us dependent on experts. We have to beg for information and feel bad
Every conflict must produce a win-win outcome and must never be resolved through a compromise, which makes both sides suffer in some way. Even forcing one side to do what the other side wants is better than a compromise.
Automated testing is a safety net that protects the program from its programmers
I would compare a project with a country, which is either properly regulated by the laws or enslaved by a dictator whom everybody is supposed to love. What modern management is doing in most companies is the latter scenario. They expect us to love the customer and work just because of that. There are no laws, no discipline, no regulations, and no principle, because, like every dictator, they simply are not competent enough in creating them. Dictators just capture the power and rule by the force: it's much easier than building a system of laws, which will work by itself. The management in software projects also can't create a proper management system, since they simply don't have enough knowledge for that. Instead, they expect our love. Isn't it obvious that rather soon that love turns into hate and we quit or the project collapses?
Quality must be enforced, otherwise it won't happen. We programmers must be required to write tests, otherwise we won't do it.
Just by making the architect role explicit, a team can effectively resolve many technical conflicts.
Punishment demotivates when it comes from people rather than a system of well-defined rules
We must not blame programmers for their bugs. They belong to them only until the code is merged to the repository. After that, all bugs are ours!
To make technical decisions, a result-oriented team needs a strong architect and a decision making process, not meetings.
