Tina is always easy to let me ruin, and she has more than once, pointed out the mistakes in my program, some belong to the code-level bug, and some is the design problem. In front of her, I always tried to live since the experience of experience, because I can always find out the mistakes in her childish code, smelling potential errors. But I often get the gray face, a rookie can also make a lot of dumb, and it is really possible to explain the problem. Recently, hot weather is easy to let people move, but she is a lady, otherwise I am afraid that I really will speak. Of course, I have not yet made this mistake in the mistakes, but also keep a little big "humble" temperament, prove that I am still half a big tack - a technology is hard but it is still harder. Great.
When calm down and started carefully, I found that many problems can be attributed to a more essential issue. In the process of implementing design decisions and subsequent code, there are many traces of grass rate. There is no repeated scrutiny, so that this system lacks self-circular skills in many places, some features are even self-contradictory. I strange why myself made such a mistake, perhaps it is too desalcation of this task (I have a little disdain to the ASP project), maybe I have not fully understood the demand.
But when I said, I can move, because I believe that Tina and I have not really completely understand all the needs in this task. We always think that at least there should be a prototype that can be evaluated, and some problems can clarify and demand will gradually become clear. I think this should be correct, this method is especially suitable for rapid development of small systems.
However, my necade and self-righteousness is that I still pay for the price, although I don't affect the overall situation, but at least let me lose it as a lot of self-sufficiency. The problem is that when the prototype is formed, I am lacking for it. Because there is not enough ideological preparation, in a system lack of unified conventions, under the premise of the rules, I started with the past experience, and these changes have introduced new conventions and rules. Unlike the previous agreement and rules, this is the initiator of those issues, and I am the roots of my face, but all this is "smart" Tina to grasp.
Regarding the rules and agreement of the system, I remember that Frederick Brooks involved in the "Surgery Team" in his "The Mythical Man-Month" book, but there was a chaotic due to the system Multiple experts from equivalents of the same dominant force. From the effect, I seem to play a multi-person role, "experts" in different different styles.
Prototype forms a grass rate design prototype formation after formation = my gray face in front of Tina
This is the formula I summed up from this incident.
