[issue 17] golang's one-year experience in developing Meitu

one side ： Talk about the project http and rpc The difference between ？ map Internal implementation , Why concurrency is not safe ？ Where is it reflected ？ What happens when memory escapes ？ Chat gc, What is tricolor ？gc What about the process? ？ When to trigger gc Well ？ If a=5, b=a , c = &a ,gc After starting ,a,b,c What color is it ？ Why? ？ How do you know the size of an image before downloading it ？ Two sides ： Talk about the project , How to design , What patterns are used ？ Is there any room for optimization ？ How to optimize ？ How to achieve a rpc frame ？ What to pay attention to ？ Let's have a quiz . On three sides ： Talk about the project Talk about design patterns ？ What interesting design patterns do you see in the source code ？ The time complexity of breadth first search ？ How to optimize the ？ Why? ？ Dictate it. Line it up , Time complexity , How to optimize the ？ How do you usually learn ？HR: A little bit of pressure ... But in general, good answers are OK When I was alone , I suddenly want to show off that I have seen the source code and installed a comparison , As a result, the pressure on this side is the greatest , Noodles are also the worst ... Fortunately, I didn't care about the interview ... Finally, I heard that Meitu had to report to apply for overtime , I have never seen such a good thing . Directly connected to Meitu's offer I won't continue the interview . In service , Verify it , Meto really doesn't work overtime , basic 965, It's really good in Shenzhen