|
newton.saber wrote: Later my boss told me I had to fix The Genius Architect's code even though I had
already written code that worked and the GENIUS rewrote my code.
What?!?
(deployment of interrobang)
At which point you just reverted the architards checkin to the prior working version?
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Dan Neely wrote: reverted the architards checkin to the prior working version?
That's exactly what I wanted to do, but I wasn't allowed. It was completely political.
Basically, without examining anything my boss said, "His unworking code is better than your working code."
Now you could assume I'm an idiot and my code is complete crap. But, honestly, the code worked very well and was actually designed and I had unit tests, etc.
Here's the kicker...
The code was never put into production anyway, because the entire project went belly-up after they spent millions $$$ paying for contractors (such as the architect) who never could get the final product running. ugh!
|
|
|
|
|
Pawel Krakowiak wrote: I feel that whoever breaks stuff should be publicly shamed
That would include everyone at some point then. 
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Of course it would! I have never met a developer who never introduces any bugs. I am fully aware I'd be shamed on occasion as well.
|
|
|
|
|
Pawel Krakowiak wrote: I am fully aware I'd be shamed on occasion as well.
If you think that would help then I suggest bringing it up to your manager.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Quote: I have never met a developer who never introduces any bugs
You should go down to the job center, I'm sure you'll find a few developers down there who haven't introduced bugs in months.
|
|
|
|
|
What, there are unemployed software engineers?!
|
|
|
|
|
They know regex. That's a coding language, right?
|
|
|
|
|
I used to list HTML under known programming languages on my CV. 
|
|
|
|
|
Pawel Krakowiak wrote: ... web app ... modal dialog ...
Hopefully not using showModalDialog? That's been disabled in Chrome[^], and deprecated in Firefox[^].
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Sorry, but I'm with Pete on this one. Public shaming is never going to work out well.
|
|
|
|
|
Why not? I did not mean real shaming (there was a winking emoticon), rather something like described here[^]. It's a joke. 
|
|
|
|
|
Any developer introduces bugs. It is the direct consequence of writing code. There is no point in shaming, even playfully - just point it out and correct it, or ask the one who introduced it to fix it (maybe there was some good reason and you yourself break something trying to fix it).
One thing that must be clear is that any relevant change must be tagged in the comments and in the changelog, so that it is backtrackable. I work duo with a colleague, and when I change some established code I never remove it, just comment out the prevoius lines, insert my own and tag with "[NAMEOFTHEMODIFICATION] xx/mm/yyyy Denis: I did this because...". The same does he (ok, not really, but if it's not tagged it's him )
|
|
|
|
|
|
|
Pawel Krakowiak wrote: I feel that whoever breaks stuff should be publicly shamed
(for example in the CI server's website, but of course my client doesn't have
CI...) and responsible for fixing it.
Let's see. Two weeks ago I fixed a few security issues in C code written in 1994 by someone I don't know who worked for a company that exists no more. As much as I would like to find the original coder and make him fix the bug, somehow I feel that won't work.
|
|
|
|
|
Is this not the path of progress?
One person creates something useful; which the stakeholders want to expand functionality for. This then gets worked upon by new team members who will not have the same knowledge levels as the creator - they add new features, and also "inject" bugs. These bugs need to be worked upon - and unfortunately (or fortunately?) in this case, it is the creator himself assigned to fix them
Not just software, but automobiles, airplanes, bridges, etc. - would have had the same path towards their current state, isn't it?
|
|
|
|
|
Message Closed
modified 20-Oct-19 21:02pm.
|
|
|
|
|
Kamen Nik wrote: debugging and fixing bugs shouldn't be done by people who developed an application
It's good to be KING!! (See Mel Brook's History of the World Part I[^])
This terrible logic would seem to create sub-human RULERS who think everything they produce is perfect.
(In an exercise of self-control, I will not mention anything toilet-related here.)
Blithely they roll on.
Ignorance of our own failures is the most beautifully ugly thing. 
|
|
|
|
|
Pawel Krakowiak wrote: I feel that whoever breaks stuff should be publicly shamed
Impossible! Everyone breaks something once in a while and when everyone is publicly shamed there is no public to watch the shaming and thus no one is publicly shamed.
Now let me find that post where your colleague said the same about your code...
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
That's 'caused'.
There.
Now it's fixed.
|
|
|
|
|
I'm not a native English speaker, so I'd appreciate if you could elaborate. Perhaps the word choice is incorrect in the first place. Maybe one can't "cause" a bug. I guess I should have said "introduced".
|
|
|
|
|
Sorry Pawel, I was just joking about the slight spelling mistake in your heading. It was a bug. 'Caused' is a good word to use. And I see you fixed it!
|
|
|
|
|
<OldWarStory>
When I graduated from college, I went to work for the same company I'd worked for as an intern. My boss was pretty overbearing and judgmental. We wrote a data acquisition system for a customer, and were doing some on-site debugging. On the first day, I fixed an issue we found. A couple days later, the issue started happening again, and my boss starts yelling at me. I looked at the code, and my fix was gone. The original code had been restored. Come to find out, my boss didn't like how I'd done something else and restored an earlier version of the entire source file, without regard to any changes.
The remaining two days of the trip, and the 8-hour drive home, were spent in utter silence on my part. During the drive home he tried to half-way apologize, but the damage was done.
</OldWarStory>
Software Zen: delete this;
|
|
|
|
|
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.)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
