[test development methodology] experience of test development platform PK - choice

 The author once worked in a large factory , See the inside gitlab There are several pages of test platforms on , I saw some redme,  I found that the function design is very good , The code looks at it casually , I found it very neat and clever , But why is it placed in gitlab Falling ash ？



 This scene , It's like I'm in an ancient battlefield that has long ended , Looking at the mess everywhere . Fall to the ground , There are many well-equipped generals .  



 At this moment, I understand a truth ： Two people compete , The one who wins in the end , Not necessarily the best equipped , The strongest body . Most of the time , The person who wins just has higher skills and routines .  



** And so on to the test platform pk in , The one who wins is not necessarily the one who writes the code well , It is not necessarily the one with clever architecture design , Most of the time , It's just that the routine of platform developers is higher .**



 This routine , It's not just code technology , Instead, we should open the pattern , It's more thinking at a higher level .  



 For example, today's point ： Choose 



 Develop a platform , Especially without a product manager , No personnel in need , No, ui Design , There is no operation and maintenance support , Not many people cooperate . But to create a platform to solve the pain point alone , This is our destiny .

 under these circumstances , You need to face great risks and uncontrollability . Many times, we have to face choices , For example, in the process of function development , You suddenly find flaws in the design , At this time, refactoring can make the upper limit of this function higher and more perfect , But there is not enough time . What should you do now ？ Then think about , Leaders seem to be anxious to go online , Still not in a hurry , Leaders hate defects ？



 At this time, you will think ： If we first realize on-time launch according to the original design , Then refactor when you are free ？ That's too much trouble , At that time, the reconstruction cost is too high , Once the line is roast , Users will be lost , Damage your image .  

 And if we overturn the current design , Do it again immediately ？ It's likely that you won't be able to go online on time , If other competitors grab the pit first , Then your platform will be capped ： Repeat the wheel  . Then be ruthlessly beheaded by the leader .  

 Another example , During the development process, you found a function that can be optimized to do better , But this is a function that is not used frequently , If the optimization without cost , Then it's definitely not worth it .  

  

 Another example , A design , very nice, But there are likely to be multiple risks and malignancies bug, I don't have time to modify it now bug, There is no time to take risks . At this time, you choose this excellent design , Or give up ？  



.....  



 Countless choices , Can you choose the right , Is the key to your success .  



 Just like you are an entrepreneur , You suddenly find a need in society , You need to develop a app To capture the market , At this time, your competitors may also find these , Also secretly developing .  

 What are you going to do ？ Is to seize the market faster , Guide users to get used to , Set industry standards , Improve user viscosity , Add moat . Or give up speed , Focus on quality , Let the opponent take the lead , And then attack others later ？ No matter what , The risks are high , This is also a choice .



 The choice is right , Not necessarily heaven , Because there are many choices, big and small, waiting for you , Can you see from a high perspective , map out a strategy , It's hard to say that we will win a thousand miles .  

 But the choice was wrong , That must be hell , It is estimated that it will be hard to turn over in the future .  



 A lot of times , It's not necessarily a good thing to concentrate on writing code , You should look up more and see the surrounding environment , Then weigh the pros and cons , In the multiple choices after the platform development process , How to choose .  

 this , Is the real wisdom ！  



 There's a good saying ： Premature optimization is the root of all evils .  

 But there is also a good saying ： spirit of craftsman , The pursuit of excellence .  



 In the whole process of platform development , You are experiencing and commanding a battle , Well written code, that's just your small-scale tactical victory , But if strategy doesn't work , Then the end is still lost .  



 This situation, whether in large or small companies , Are widespread . Many platforms are rising stars , Obviously better , But it is always unable to establish projects and promote them , The reason lies in the strategic failure . Because you ignore all levels in the company , All departments , The psychology and position of people in all positions .  



 In such as ： Optimize , Fluency , Security , risk ,bug, Maintenance cost , Operating costs , Ease of use , Efficiency , Function realization , Speed   Wait, after these elements conflict , How do you choose ？  



 Will there be a book that will tell you how to choose ？ It's impossible to have .  



 Because there is never the right answer , At different times , Different locations , Different companies , Different colleagues , Different leaders and different you , On different test platforms , The answers will not be the same , Even many times there is no correct answer , Or the right answer .  



 And the only way to ensure that you make the right choice , Just practice more , Experience more , Then realize the rules .  

 But unfortunately , Not everyone has enough experience to upgrade .



 These things , The best way is to work with an experienced master , Watch your words and expressions every day , in the course of time , Absorb experience , Stand on the shoulder of the master .