|
That's when you've reached complete developer enlightenment. You now have a creative license to go crazy. Free tinfoil hats in the corner...
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: Free tinfoil hats
I am using something better this very moment: Tinfoil tape![^] But I'm not telling you what i use it for.
I need a perfect, to the point answer as I am not aware of this.
Please don't reply explaining what method overloading is
|
|
|
|
|
Niiiiice
Jeremy Falcon
|
|
|
|
|
Ok, I will tell you what I use it for.
I'm building a model[^] and before I can paint that thing, I first need to add all kinds of details like panels or rivets. The tape is great. You can sand it, easily and precisely cut it or engrave lines or other details into it.
I need a perfect, to the point answer as I am not aware of this.
Please don't reply explaining what method overloading is
|
|
|
|
|
And here I thought it was to protect us against the Xenu overlord from Scientology.
Jeremy Falcon
|
|
|
|
|
It will even protect you from your wife. Wrap her up as a tinfoil mummy.
To say it with another man's words: What the hell is an aluminum falcon!?[^]
I need a perfect, to the point answer as I am not aware of this.
Please don't reply explaining what method overloading is
|
|
|
|
|
That's the best part. The ultimate poof you have improved...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Marc Clifton wrote: At some point, I become that "other dev" when looking at my own code
Agreed. It doesn't take long either.
|
|
|
|
|
|
|
|
Yeah, it's a Kanye West song - he sang it at Glastonbury in 2015.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
It seems Kanye West wrote all the good songs. Ever. Even those were playing before 1977... Especially those were playing before 1977...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
You know, I'd noticed that same thing myself!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
After reading this thread[^] on PDF readers, I started thinking about a potential replacement for my current editor.
I've been using Foxit's PhantomPDF[^] for a couple of years, and have been happy with it. Prior to that I used Nitro's product for quite a few years, but had enough problems that I replaced it. My biggest need is to produce PDFs from other formats (like MS Word) although I do a fair amount of assembling other documents into a combined product.
What reasonably priced products are available? [Adobe prices itself out of my market.]
|
|
|
|
|
CutePDF[^] or some other PDF printer. Doesn't have PDF editing capability, but it allows you to save anything as PDF document via the print process.
|
|
|
|
|
At first glance, CutePDF has several editing tools and the price ($50 to $90 USD) isn't bad. I will investigate this further.
Thanks!
|
|
|
|
|
|
Free is great! I can't see paying for a reader, too many good ones available.
For editing? I'm ok with paying a reasonable amount.
|
|
|
|
|
|
So she added some new features, fixed it at the system level as needed, and changed the tests...
Those features passed the tests but broke down plugins were installed on live systems...
So a bug report filled and she expressed her will to fix it immediately (but set the severity of the bug from Critical to Low) - it took 5 days and need to be applied manually, as it will be part of the next release at the end of the month...
Her mistake was to change the tests and not to add to them a new rule, so I expressed my opinion, that let the same person write the code and the tests is not a good idea as it can be the source of the infamous 'it works on my machine' bug. I also expressed my opinion, that the person who has assigned (by boss or by chance) to a bug report, should not be the one who set the severity level, especially if it is the very same person who ruined the code in the first place...
So I got a lot of buzz and she got the glory (not clear of what)...
I feel a bit like a bad dream...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: So I got a lot of buzz and she got the glory (not clear of what)... You just earned some Code Monkey Points. Congratulations.
When you have done something, it works and someone who had nothing to do with it steps in and gets all the glory: Lots of CMPs.
When someone else has done something, it fails spectacularly, you had nothing to do with it and still get the blame: Lots of CMPs.
When those who actually did it still get some glory for nothing: Platinum CMPs for CM who got blamed.
Seriously: I hate office politics, and that usually is what is actually going on when such strange things happen. Be a little careful.
I need a perfect, to the point answer as I am not aware of this.
Please don't reply explaining what method overloading is
|
|
|
|
|
Sounds like you guys need something like a pre-commit code review cycle.
This space for rent
|
|
|
|
|
We have. Very ineffective...
I did a statistics last year - 83% of the bugs customers reported were there in our code and approved by QA to commit to the latest stable...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
So, the takeaway from this is that your existing processes aren't fit for purpose, and they need to be tightened up.
This space for rent
|
|
|
|