|
"I don't have coworkers."
|
|
|
|
|
What happened to "we don't have bugs"?
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
OriginalGriff wrote: "we don't have bugs"?
That's a synonymous for "we don't have users".
|
|
|
|
|
Nope, we just document the bugs and call 'em "features"! 
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
I just claim the bugs were caused by the Chaos Theory. If you ramble long enough about how it apparently applies people lose interest in complaining fairly quickly.
|
|
|
|
|
Although I work in a large business with many software devs and teams I tend to work solely on projects by myself.
|
|
|
|
|
It might not be a bug - it could be I misinterpreted it - or it might be a bug which makes his code work.
If I fix it, it could break his code.
I'd talk it over and work out a solution that doesn't break anyones code before I went ahead unilaterally.
Not that it happens here, obviously.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Oh, and of course this won't be an issue if it is related to a CListCtrl...
This said, which was the first bacon and listctrl post here  ...
Yes, we do it... once a bug is detected we try to find out what has originated it and then we try to solve it as a team.
|
|
|
|
|
I usually tell the author about the bug, and ask if he wants me to fix it or if he prefers to fix it by himself.
|
|
|
|
|
My upvote - I fully agree! In a team you should talk first and not silently fix someone else's code. If possible, the "owner" fixes, but if circumstances mandate/allow, anyone should be allowed to fix or even to rewrite.
Cheers
Andi
|
|
|
|
|
... signed in triplicate, sent in, sent back, queried, lost, found, subjected to public inquiry, lost again, and finally buried in soft peat for three months and recycled as firelighters.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
..of your wife? 
Don't mind those people who say you're not HOT. At least you know you're COOL.
I'm not afraid of falling, I'm afraid of the sudden stop at the end of the fall! - Richard Andrew x64
|
|
|
|
|
...of the Vogon Constructor Fleet!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Fate
thatrajaCode converters | Education Needed
No thanks, I am all stocked up. - Luc Pattyn
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is - Henry Minute
|
|
|
|
|
NO, I don't mess with anyone's bugs. I know that they know how will they fix it. But if my co-worker asked for help, I am willing to give it.
But sometimes, I tried removing someone else's bugs, if it will have a direct effect on my project.
Don't mind those people who say you're not HOT. At least you know you're COOL.
I'm not afraid of falling, I'm afraid of the sudden stop at the end of the fall! - Richard Andrew x64
|
|
|
|
|
Since this many years in Software development, I have encounter such situation many times.
Sometimes it inevitable not to work on someone else's code, I have seen situation where the fellow on whose code you're working has been assigned to another project. And it really bad feeling to clean someone else mess.
The more you get experience about how to deal with such situation its becomes manageable to evade this kind of situation and sometimes you need courage to say 'NO' and it works if you stay firm.
I believe, if the person who has previously work on the code is there then it should goes to that person only either way its really inefficient.
You can have all the tools in the world but if you don't genuinely believe in yourself, it's useless.
|
|
|
|
|
Bug finding and removal is not a easy task, because sometime we stuck at a point & we can't think the another way, And if someone other person help you, He can think the problem with different way...
I personally feel that. And I am not hesitating to help and to get help from my co-workers or friends...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
