part developer PL / SQL - 2nd Some tips
Monday, November 2, 2009
Netflix To Router Settings
Do not be afraid to ask for help 
The software is written by humans, and therefore, it is important to recognize that human psychology plays an important role in software development. An example is the following.
Joe, an old developer with a team of six, has a problem with your code. Reviewing it for hours, increasing their frustration and can not find where the bug. Can not think of even thinking about asking for help to their peers because none of them has the experience of it. Finally, his head does not give you more and ends up "giving up". Sighing, he lifted his phone and dials an extension: "Sandra, could you come and give a look to my code?" I have a problem which can not find where it can be. " Sandra goes for his place and a quick Joe revised code says what it should have been obvious for a long time. Hooray! The code works, and Joe thanks him, but actually feels sorry inside. Thoughts like "How come I did not see before?" and "If I had spent five minutes doing my tests I had found" go through the mind of Joe. It is understandable but also very stupid. The point here is that they often fail to see our problems because estamos muy metidos en nuestro propio código. Algunas veces todo lo que necesitamos es una nueva perspectiva, la visión relativamente objetiva de alguien sin nada en juego. No tiene nada que ver con la antigüedad, pericia o competencia.
Steven recomienda fuertemente establecer dentro de la organización los siguientes lineamientos:
Retribuye admisiones de ignorancia
Ocultar lo que no sabes acerca de una aplicación o su código es muy peligroso. Desarrolla una cultura de preguntas y peticiones de ayuda.
Pide ayuda
Si no puedes encontrar la causa de un bug en 30 minutos, pide ayuda inmediata. Puedes incluso idear un "sistema amigo", de tal manera que everyone has someone assigned to the group who is expected
prompted support. Do not let yourself (or others in your group) spend hours hitting you against the wall in a fruitless search for answers.
process establishes a code review by a fellow
Let no rise to production code without having read and criticized (in a positive and constructive manner) by one or more developers in your team
Joe, an old developer with a team of six, has a problem with your code. Reviewing it for hours, increasing their frustration and can not find where the bug. Can not think of even thinking about asking for help to their peers because none of them has the experience of it. Finally, his head does not give you more and ends up "giving up". Sighing, he lifted his phone and dials an extension: "Sandra, could you come and give a look to my code?" I have a problem which can not find where it can be. " Sandra goes for his place and a quick Joe revised code says what it should have been obvious for a long time. Hooray! The code works, and Joe thanks him, but actually feels sorry inside. Thoughts like "How come I did not see before?" and "If I had spent five minutes doing my tests I had found" go through the mind of Joe. It is understandable but also very stupid. The point here is that they often fail to see our problems because estamos muy metidos en nuestro propio código. Algunas veces todo lo que necesitamos es una nueva perspectiva, la visión relativamente objetiva de alguien sin nada en juego. No tiene nada que ver con la antigüedad, pericia o competencia.
Steven recomienda fuertemente establecer dentro de la organización los siguientes lineamientos:
Retribuye admisiones de ignorancia
Ocultar lo que no sabes acerca de una aplicación o su código es muy peligroso. Desarrolla una cultura de preguntas y peticiones de ayuda.
Pide ayuda
Si no puedes encontrar la causa de un bug en 30 minutos, pide ayuda inmediata. Puedes incluso idear un "sistema amigo", de tal manera que everyone has someone assigned to the group who is expected
prompted support. Do not let yourself (or others in your group) spend hours hitting you against the wall in a fruitless search for answers.
process establishes a code review by a fellow
Let no rise to production code without having read and criticized (in a positive and constructive manner) by one or more developers in your team
Subscribe to:
Posts (Atom)