The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
So you go to the centre of the Catholic church at Easter and are astonished at the crowds
Mind you we did the same in Vietnam wanted to visit the mausoleum on their national day, the queues were kilometers long. Weird thing was the 5 star hotel concierge did not know if the place was going to be open or he was just pissing around with the tourist.
Never underestimate the power of human stupidity -
I'm old. I know stuff - JSOP
As someone who has been to Rome many times, over the last several decades, I F***ing hated it, the last time I went there, a few years ago.
I wanted to find a T-shirt printing place that could emblazon T-shirts for me with "Do I look like the kind of moron who wants a F***ing selfie stick?" on the front, and "I Probably know the Vatican better than you do, you F***ing uneducated, half-trained foreigner!" on the back.
Vedi Roma e muori -- da vergogna.
I wanna be a eunuchs developer! Pass me a bread knife!
I bit the bullet and installed the FxCop Analyzer on my own pet home projects...
First I ended up with thousands of warnings
Plenty of them useless....
Well then I embraced the global warning suppression...
It is good, but annoyingly create a GlobaSuppression.cs, it is annoying because I would have edited the error.ruleset file instead, which would be better I guess (more prominent), and sometimes it can be tedious to find the annoying rule one want to suppress in the treeview manually...
after that it did find some vaguely less than desirable code. Yeah!
(Remark, I mean just that, not quite a bug, but less than desirable, like incorrect exception constructor or using string.ToLowerInvariant() which is problematic, advised to use ToUpperInvariant(), or use a TaskScheduler explicitely, or use Array.Empty<T>() instead of new T)
except it is sometimes quite tedious to review 87 warnings in 4 years old code while I got other things to do... (particularly as I am, for once, "productive"... I do not need one more excuse to procrastinate on the feature that defied me for almost 2 years so far... )
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
And static analyzers serve no better purpose now except, unlike lint, companies charge for them.
Hypothetically they might be valid if a company was only using junior programmers, or perhaps had more than a couple and the senior developers refused to review code. But in that case then it is a management problem not a technology one.
In a recent case a static analyzer required re-engineering a simple factory pattern that was using a switch statement. The re-engineered effort passed review (not by me) that was done by creating a dictionary which instantiated all of the classes controlled by the factory...every single time. Passed the static analyzer though.
In a recent case a static analyzer required re-engineering a simple factory pattern that was using a switch statement. The re-engineered effort passed review (not by me) that was done by creating a dictionary which instantiated all of the classes controlled by the factory...every single time.
That sounds like a candidate for the Weird and Wonderful. But my main comment: F*** that!
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004