The well-known situation. Go to your resort manager and said that an urgent need to correct an error in the program, or outline new features. Or it could be the customer. It does not matter. The starting point, you decide to please the manager, deciding his problem in a patch program. In the current situation is the easiest way: his problem can be solved quickly, to the delight of manager. Unfortunately, then do it all in the normal you probably will not be time. There will be new challenges.
After a while, as always, suddenly, at the most inopportune moment, reveal that this patch baffled another programmer had worked and no longer. He spends a lot of time to find and root out the patch. Worse, if the patch will mask the problem in one place, and another error that is not completely covered with a patch, will continue to ... You can be loud and obmaterit, but behind you obzovut ... Excuse does not work. What you end up with?. Price - patch your reputation.
dissecting the situation. Do managers have a situation that requires immediate correction of some errors. While this is a problem manager. It is puzzling you. While it is still a problem. You decide to quickly patch the code and solve its problems. He runs away contented. He decided to issue. But you yourself have created a problem at the cost to your reputation. Q: It is necessary to you? . To you had a good attitude from the authorities, as fast, the executive officer? .
As it was necessary to act in this case? . He, for sure, there are methods for solving organizational. You made a request and radically eliminate the problem, no patches. As a rule, in passing a few more bugs dig. Your reputation will emerge as a thoughtful, serious programmer.
Once again, consider this: the price - patch your reputation.
No comments:
Post a Comment