I used to work at one place, they usually reacted to any problem that the hardware or users were Absence of not using the flaw completely I had adopted philosophy that it is my fault as long as I can prove it right before that job (and yet 99 out of 100 right).
One of the last "ineffective" problems I had was an abundance of valuable time in the database. After a few months of research, I still had the theory but none of them could prove to be true. One of my developers has suggested changing the network (every router, switch, access point) but no one can give evidence that the network was the cause; However, according to my manager (no development / IT experience) was not "obvious reason", so he handled the problem. A warning and fog creek plug: It can not be accounted for the fact that the fogbugs work through the error report completely and on the same SQL Server as the rest of the data. A couple, months after no expiration, my manager claimed that they had set an end date ("Look, no time-out!") I had to stop holding a rock and said "Look, there is no tiger!" But I asked how they knew that they did this, for which I did not get any answers. The timetable returned two months later (more in number).
How I work in this situation is very beautiful content, but I'm curious that so many crowds have a better / collaborator you know that implementing a solution (or very sure) ) Is wrong and will probably ruin thousands of dollars?
Let them go, but continue to seek the real cause at the same time.
One thousand dollars is spent well if it prevents me from going against that kind of thinking (which is meaningless).
Comments
Post a Comment