|
You have my deepest sympathies.
Some years back, my department was afflicted with a manager who thought he could and should "fix the inefficiencies" in other people's code. The responsibility for dealing with problems he created invariably wound up on those hapless "other people's" desks...mine included. The ill will he generated that way was thick enough to be carved into entrée portions and served with hollandaise sauce.
Needless to say, the manager was never taken to task by his superiors for his arrogant interference in things he knew next to nothing about. However, the problem went away when he met an untimely demise: run over by an SUV, right in our very own parking lot. And they say there's no justice in this world!
(This message is programming you in ways you cannot detect. Be afraid.)
|
|
|
|
|
Well this is a matter of the tension between 'get her done' and teaching. The solution my currant company has come up with is using a web based code review system. When I get someone else bug, I fix it, but then I make sure they are on the code review so they can see the fix. If they are someone I know well, I will talk with them about what and why I did it. This allows me to get her done for the business while still making it a teaching opportunity.
Mind you, if the other developer does not care, I totally agree with the other poster that said you need to take that to your manager, that IS why they are there
|
|
|
|
|
Maybe you can take this negative and turn it into a positive. A true team really doesn't need a manager or to be publicly shamed, they're able to communicate among themselves and tackle issues together. Play dumb and ask the guy that wrote the code to help you. Point out the error and ask for his input. Get an understanding of what he did and hopefully he gets an understanding of what you did.
|
|
|
|
|
When it comes to breaking builds, our culture is that the one who broke it is quick to at least say they investigate it, lest their inbox fills up with "friendly reminders" from all the others.
As for bugs: We tend to use "You were the last to touch it!", the the age-old unwritten rule that has governed many a playground over the millennia.
I'm not necessarily for shaming someone who trips and falls (as others have said, we all do from time to time), but if that someone then refuses to fix their mess, or tries to get away from fixing it, that's a whole different ballgame.
|
|
|
|
|
Happy me. Found another bug caused by the same developer during the same changes, but in a different place. I fixed the last bug...
|
|
|
|
|
Be happy.
I frequently get entire half-finished apps that need to be resuscitated; trying to figure out what works properly; what doesn't; what's missing.
At least you know what it's "supposed" to do.
|
|
|
|
|
There are several ways to look at this
Maybe you are the best person to fix the bug and prevent it from happening again.
Maybe you did a bad job. No supporting documentation, no comments etc..., basically no knowledge transfer which is often the case.
Ego meshed in with the code.
...
...
Regards,
Ousmane
|
|
|
|
|
This used to be roughly half of what I would do on a regular basis. My nickname used to be "the cleaner", as in the guy who cleans up the bodies to make it look like nothing ever happened. The better you get at coding, the more you are called in to "fix it". Think of it as a vote of confidence in your abilities to get the job done.
|
|
|
|
|
Maybe your team could do with code reviews and release testing? IE get script buy-off by the team, promote to test server, have the test team run regression and new functionality tests, get test buy-off, move to production.
PS Since you didn't name names, I don't see a problem with complaining about co-workers. It might even shame the developer into doing better in the future if (s)he reads about it here. If you have good code tracking, people should know who did it anyway. However, it makes sense to assign it to you, the modifier proved incompetent and since you built it, you are more likely to fix it properly.
|
|
|
|
|
I am not sure about what is correct/incorrect in this particular case. But, I feel you should get recognized for that work you did; either writing some new code or fixing bugs created by others.
Here's a story. You might already know it.
There was a farmer who had a horse and a goat…..One day, the horse became ill and he called the veterinarian, who said: - Well, your horse has a virus. He must take this medicine for three days. I’ll come back on the 3rd day and if he’s not better, we’re going to have to put him down.
Nearby, the goat listened closely to their conversation. The next day, they gave him the medicine and left. The goat approached the horse and said: - Be strong, my friend.
Get up or else they’re going to put you to sleep!
On the second day, they gave him the medicine and left. The goat came back and said:
- Come on buddy, get up or else you’re going to die! Come on, I’ll help you get up.
Let’s go! One, two, three…
On the third day, they came to give him the medicine and the vet said:
- Unfortunately, we’re going to have to put him down tomorrow. Otherwise, the virus might spread and infect the other horses. After they left, the goat approached the horse and said:
- Listen pal, it’s now or never! Get up, come on! Have courage! Come on! Get up! Get up!
That’s it, slowly! Great! Come on, one, two, three… Good, good. Now faster, come on…… Fantastic! Run, run more! Yes! Yay! Yes! You did it, you’re a champion!!!
All of a sudden, the owner came back, saw the horse running in the field and began shouting:
- It’s a miracle! My horse is cured. We must have a grand** **party. Let’s kill the goat!!!!*
***
The Lesson:* this often happens in the workplace & life in general . Nobody truly knows which employee or people actually deserves the merit of success & are in fact contributing towards success , or who’s actually contributing the necessary support to make things happen. Be grateful.
Remember………
*** LEARNING TO LIVE WITHOUT RECOGNITION IS A SKILL!!!! ***
|
|
|
|
|
Thanks for the story.
|
|
|
|
|
|
Quote: This wasn’t his first brush with the law.
arf! arf!
|
|
|
|
|
You can make puns for this subject all to easely.
|
|
|
|
|
Your reply leaves a bad taste on my palate.
|
|
|
|
|
I take it you are not good at canvasing people
»»» <small>Loading Signature</small> «««
· · · <small>Please Wait</small> · · ·
![Badger | [badger,badger,badger,badger...]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/badger.gif)
|
|
|
|
|
Not really, oil just chalk this up to experience.
|
|
|
|
|
So neither drawn to art then? Well I think you need more experience, if you get my picture...
»»» <small>Loading Signature</small> «««
· · · <small>Please Wait</small> · · ·
|
|
|
|
|
I can manage without necessities, but I can't live without my luxuries.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
So, here's something annoying on Wikipedia:
http://en.wikipedia.org/wiki/Kilobyte[^]
Apparently, for some time now they've been recalibrating the kilobyte to be 1000 bytes. 1024 is a 'Kibibyte', a word I have never heard spoken my whole life. It also sounds stupid.
1TB on a hard disc is 10^12 bytes, not 2^40 (almost 10% smaller). And 65,536 bytes on a Mac shows at 66KB. That's just perverse. I hate Apple even more now.
How many of you knew about this outrage? And if you did why didn't you stop it?!
Regards,
Rob Philpott.
|
|
|
|
|
I knew about it, tried to stop it, and failed. Wikipedia has been aggressively marketing this weird "ibi" thing for years now.
I'm even sort of OK with that, what really annoys me is that some actual people are being infected by that bad habit.
A kilobyte is 1024 bytes, anyone who claims differently is trying to scam you.
|
|
|
|
|
harold aptroot wrote: A kilobyte is 1024 bytes, anyone who claims differently is trying to scam you.
Well said! And apart from 1000 being a useless number in computation theory, this introduces ambiguity to the KB. You now need to know whether its a real KB or the airhead version.
Regards,
Rob Philpott.
|
|
|
|
|
Rob Philpott wrote: You now need to know whether its a real KB
I thought KB were the window's updates   
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
It existed and there has been a debate over it for years (like almost everything in the Computer World) over usage of KB and KiB. Normally ego-maniac kids tend to correct KB with KiB in non inherent articles to prove their manliness.
IMHO this has been used to the HW productors advantage in order to boast performance they don't have, since a GB is smaller than a GiB by 7.2% (there is a progression of 2.4% for every !0^3 step).
I guess Mac recalibrated to give a better idea to the user of how much space he is actually using - think of games of 25 GB vs 25 GiB (= 27 GB).
|
|
|
|
|
I ma not sure Wikipedia is the best source when it comes to naming standards.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
