|
I've lived most of my life in south central Pennsylvania, and dippy eggs is a term I've herd often.
|
|
|
|
|
We have giga build farm here.
I found a scenario were some base class can be setup incorrectly that is hard to detect (basically some code to detect faulty redo code). I can't commit it because when I try.. it "causes" many bugs (detect lot of broken code all along, but no one knew), so I have to fix "my bugs" first, by delving in tons of code I have clue about to fix them (those other guy's faulty redo code)... this is all so painful....
I try to gather some interest on slack.. but no one is really excited by a bug finder apparently... I need to up my communication skills! 
modified 19-Aug-22 3:20am.
|
|
|
|
|
Super Lloyd wrote: but no one is really excited by a bug finder apparently...
Oh man, how good I can relate to that...
I am a very very good tester, because the weirdest / most awkward situations / side effects of code always happen to me (even when I don't want them).
At a previous job, the guys programing the overarching library were always with faces saying "oh, no... not once again" everytime I got into their office and headed to their desks.
Once I even got a "why do you always come to bother us?" from a guy there... I had to bite my tongue to not answer "because you are mediocre and I always suffer the consequences of your crappy code"
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.
|
|
|
|
|
Don't shoot the messengers, we said! 
|
|
|
|
|
Is this your job to rally the team to fix their bugs, or the Dev Lead's job? (or are you the lead dev and/or manager?)
My point is you may not need to convince a team, just one person.
cheers
Chris Maunder
|
|
|
|
|
Running all the test on the farm is rather difficult.. one has to use special tools and argument which still confuses me and easily take half an hour each.. I guess spending a few days (weeks?) just running through each and all test manually, and then warn their associated team, daunts me... And apparently it's what's needed to be the Cassandra of undo units..
It is a work I came up with all by myself. I realized, looking at some of our team's test that undo unit were badly written in a subtle way. I found a way to detect such mistake.. and now I am trying to commit this bad code detector that affect everyone on our 10,000 man year codebase...
|
|
|
|
|
all I can offer is: Good luck
cheers
Chris Maunder
|
|
|
|
|
Quote: so I have to fix "my bugs" first, by delving in tons of code I have clue about to fix them
Are you saying your programming skills are poor for that particular task? maybe you should make a post in the 'seeking help' forums.
|
|
|
|
|
you clearly never had to fix tons of bug in a 10,000 man years codebase you have no clue about...
|
|
|
|
|
No I didn`t. A question does come up though, how did the software get in such a bad shape? I suspect the code was in a working state (the software was being used by the users) at the moment when you took over (one would think the software would not function at all with the source plagued by tons of bugs)
|
|
|
|
|
The bug I make very clear with my code is when one undo a couple of times then redo once, they cant redo no more.... Kind of easy to overlook...
In fact it seems since I am here this kind of bug comes up every now and then in a never ending episodic fashion... Each of them being hard to track. My code make it easier to uncover them.
|
|
|
|
|
What you are probably saying is that the path to failure to keep over patching an old codebase to keep it 'alive'. But that`s a guess, you`re using impossible English for me so I`m not 100% sure about the meaning of your expression of thoughts.
modified 20-Aug-22 16:30pm.
|
|
|
|
|
So you create a redo2 with the correction. Port all of your dependent code to redo2.
Deprecate redo.
They will have to fix their own code as it creates new warnings.
|
|
|
|
|
Have a really great day @Marc-Clifton
![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) ![Jig | [Dance]](https://www.codeproject.com/script/Forums/Images/jig.gif) ![Badger | [badger,badger,badger,badger...]](https://www.codeproject.com/script/Forums/Images/badger.gif)
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
|
Happy birthday.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
|
(chiming in) Happy birthday Marc!! Have plenty more, they are good for you.
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
Thank you, and yes they are!
|
|
|
|
|
|
|
Happy birthday young man!
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
Thank you! 60 years young!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
![Java | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif)
whichever you prefer 
