How to become a bad programmer-php Tutorial

How to become a bad programmer

It is difficult to become a good developer. Let's talk about how to become a bad web developer! Learn only once If you want to implement a function and make the function work normally, is your method like this: It cannot be improved without being touched, thinking, or thinking. Why should I solve the problem? There is no need to fix the damaged part, right? The progress is slow, it doesn't matter, the code cannot be read, or copied and pasted from other parts of the program. it doesn't matter, even if it is from some websites that are invisible. As long as the problem can be solved, everything will be fine. According to this inference, our practice is: do not read books, do not read blogs or articles, do not accept others' opinions, and do not read network broadcasts. Why do you want to solve this problem? Obviously, your knowledge is the most matched, and it seems like you are not, so ...... You don't think you need to waste time at all-once you have mastered this knowledge, there is no need to study in depth! By the way, you do not need to learn new programming languages. Groovy? Clojure? Scala? Everyone is a lie! Look at the guys who only use COBOL: Aren't they still doing well! Do not study what you have learned Well, in any case, you have learned something. Search for a solution on StackOverflow and occasionally find that an article by Martin Fowler is quite appealing, or is too boring to shelve The Clean Coder. Do not study anything you have learned. Yes, you just need to read the rigid content blindly: do not verify the authenticity of the knowledge, or check whether it is suitable for your style! Learn everything only once! From different perspectives, and then think about some unique insights ...... Why? after the application solves the problem, you can easily go home and play the game. I will talk about it later. Do I have to know it? Do not accept others' opinions and guidance This is obvious, because ...... Are their words correct? You have learned how to solve this problem. It works well. That's not the case. Why do others question your encoding method? You do not have to learn other ways to solve the problem! Relying on the old man and the old man will hurt our self-consciousness. So, don't listen to those guys. You do not need to make your code readable. Think about it: why make the code readable? As if we still need to go back and see it? Your code is already very good and can work, so we don't need to touch it again. In addition, for a computer, it does not matter whether the code is readable or not, as long as it can run the program. Your code is not written to facilitate reading by other programmers. As a matter of fact, it is better that only you can understand it, so this job is not yours, isn't it? Do not write test Loser is required for testing. Testing is the tomb of a stupid person. Please believe that your code is perfect! You will never make mistakes-either due to a programming language defect or machine error. If the code can run on your machine, there is no reason not to run normally elsewhere and it will always run normally. In addition to writing code, do nothing else. Why do we need to analyze requirements, understand the business, write tests, and learn how to deploy data outside of your computer? Besides, it is no good for you to write code, right? Is it helpful to complete these tasks in addition to wasting time? Don't help others Don't Help Others: Let them find a solution. Maybe they will ask you how to solve the problems they encounter, but why do you have to bother yourself? It's done, right? What's more, the programmer cannot hear the advice of others like you: "Don't accept others' opinions and guidance." isn't that forgotten? Helping others not only takes time, but also makes you doubt your knowledge and capabilities. this is not the case. As a result, the snow in front of the door is more than the power of others. Conclusion With all the skills above, you can become a bad developer. Poor but comfortable developer. Thank you! Cheers! ... Did you say you don't want to be a bad developer? Okay, but first of all, I want to solemnly tell you that this road will definitely go very hard. please be prepared: The above tips on how to become a "bad developer" must be completely reversed. That's right. I mean everything. every line! Regular reflection and self-criticism: is this effective? Why? Why is it invalid? Is there any possibility of improvement? The process of thinking may be very big, but it will also make you continue to improve. Read The Clean Coder written by Robert C. Martin. This is not a sales promotion. If you are interested in becoming a real professional developer, rather than a bad developer, it is absolutely worthy of every penny you spend. Now, let's proceed to the target! Get free LAMP Brothers original php Tutorial CD/the elaborate PHP Essentials edition, details consulting official website Customer Service: http://www.lampbrother.net