Good Programmer PHP Programmer Interview Don't be eager for quick success but focus on future development.

As soon as I say something like this, people will make a lot of comments and criticize: You are wrong, wrong, completely wrong. Good programmers need to have communication skills, and they need to have the ability to work with others. You're not the only one on the team! In fact, people will say: it's better to compromise on the technical requirements so that you can find people who are better suited to the corporate culture.
　You might as well say this more appropriately: If I can’t find someone who is technically good and can adapt to the corporate culture, I will wait until I find him.
We rarely have companies that dare to have such luxury. Maybe Google can do this. Even companies like Google have always been in a state of "desperate to recruit programmers". If you decide to wait, I can foresee that you will have to wait a long time for each programmer to be hired, and the business will collapse due to lack of programmers, which is imminent.
　So, which one is better?
　Let's consider the average or inferior programmers who are nice and work hard. Their programs are poorly written - their programs simply don't work the way they want them to, and even if they do, they're bad programs that are difficult to maintain. They struggle to explore basic functions, let alone solve complex problems. But they are able to keep up with the team, and the project progress is updated every day. You can see that they are struggling in their seats every day. All is well and your manager will be happy because the team appears to be moving forward smoothly.
When the release date has to be pushed back, and the product is too buggy to be used, people will lament that the software is inherently difficult to make, so more affable mediocre programmers will be thrown in to fix the problems. I think everyone knows the outcome of the matter.
　For programmers, there are not many things that can be solved with kindness. A friendly mediocre programmer can become a business analyst, a technical salesperson, or some other position that utilizes his affability and his little technical knowledge. They will be very satisfied with this kind of work, but this is all tea party work, not finding effective ways to make good software.
Another option is to find a programmer. He can make good programs, but maybe he is not good at getting along with others, or he is always late, or something else. He can develop software that works as designed, and he can abstract a complex problem into a simple one. The software is easy to use and maintainable, and you can modify it as required at any time.
　The world is real and there are so many ways for us to screw up, but at least we have a chance. People can make a good impression. Teams can be built well. The employees work long hours for you, which is nice. A lot of business didn't work as planned, but it still worked, not bad. But no great software will be implemented by mediocre programmers. .
　The proof is in the code. that's it.

The above introduces the PHP programmer interview for good programmers. Avoid being eager for quick success and pay more attention to future development. It includes content about good programmers. I hope it will be helpful to friends who are interested in PHP tutorials.