The Weird and The Wonderful

I suppose there is the possibility that a potentially exception throwing routine simply must be called in a destructor, and that logging or otherwise reporting the exception is not acceptable because allocating the necessary resources is potentailly unsafe, in which case your colleagues code would be quite acceptable. One might find a similar argument in a C++ library with an extern "C" interface.

Reporting or logging errors isn't always an option. Sometimes you just have to use other methods. Besides, further compounding the problem by obfuscating the errors is a suspect solution. Did you push your changes?

Time to point out that this is C# code.

*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington

"Mind bleach! Send me mind bleach!" - Nagy Vilmos

CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

...you mean to tell me that C# won't run on my doorbell?

I'd like to go a bit further, as a rule of thumb everytime time you go into the more general exception (as in your case) you MUST quit the application, of course you can log it but it's mandatory to quit if your program stayed in a compromised situation, otherwise you are able to inform your users about the problem (which should be very specific or maybe catch a more specific exception and solve it).

Many programmers do what your colleague did because they think it's not professional to quit that abruptly, wrong!, it's not professional not to accept the problem.

Carlos Alberto

Hah! You think that's bad?! Some time ago, I inherited some code which had about 70 data classes, each containing three or four methods along the lines of:

C#

public override void CreateEntity()
{
   try
   {
      // blah, blah, blah...
      
      base._database.ExecuteNonQuery(storedProcCommandWrapper);
      
      int parameterValue = (int) storedProcCommandWrapper.GetParameterValue("@RETURN_VALUE");
      if (parameterValue == 0)
      {
         throw new Exception("Create failed.");
      }

      // blah, blah...
   }
   catch (Exception exception)
   {
      exception.Message.ToString(); // Why?!
      throw new Exception("Exception occured", exception); 
      // OK, let's not bother checking the spelling of the message either!
   }
}

Needless to say, all of the code which called these methods looked like:

C#

try
{
   customer.CreateEntity();
}
catch (Exception ex)
{
   MessageBox.Show(ex.Message);
}

No logging. No access to the inner exception. No way to diagnose why one button was displaying the really helpful "Exception occured" error every time the user clicked it. Dead | X|

"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer

If this is to teach him lesson then I agree with you, considering the fun. Big Grin | :-D

But for deployment, it may cause serious problem.

Once, as a prank, a guy put an ASP.NET error message as data in the database (with the HTML formatting). Then he told another developer to look into a problem where in a HTML table on of the cells would display the ASP error message.

$Shucks | :-\$

I could see him getting spoken to to correct his coding and you looking to explain to a new employer why you got sacked for sabataging the codebase.

FAIL.

Sorry to be a party pooper, but your evil intentions would not be fulfilled by that. You haven't overridden the GetType method. You've hidden it. And that means the compiler will only bind to the implementation if invoked on a reference of type TheClass. And it's unlikely anyone would call GetType on the thing if it's already declared to be TheClass (although the run-time type of course could be a descendant).

So, since GetType isn't virtual it'd still return "TheClass" and your colleague would go to the code and see that you've attempted to fool him. (If you guys have decent source control anyway.)

I do sympathize with your sentiments though. But frankly it is often the project managers who are at fault, because rather than foster a culture where mistakes are openly discussed, not for the purpose of punishment but for education, they tend to reward people who "are positive". In my experience that's often people who aren't competent enough to see the myriad things that are usually F-ed up in... well, any codebase I've come across.

Andrei Straut wrote:
Yes, I'm a devious SOB, but hey, if they don't care, why should I?

If you didnt, then you and that person do not have/make/create any difference. Its just like watching a crime happening and ignoring it than atleast reporting.

My cUr10U5 w0rlD

hahaha lol... clever idea Big Grin | :-D

============================================
The grass is always greener on the other side of the fence

So my boss is like a rabbit. He just loves his greens.

Unclear naming should stay unclear by commenting it (helper was never used, but that's beside the point).

VB

' A helper variable.
Dim helper As Boolean

Of course we could make clear comments in favor of properly naming our variables.

VB

' s is a SalesOrder
s.DoSomething()

p.DoSomethingElse ' PurchaseOrder

The obvious also needs extra explanation.

VB

i = nX + nY ' Add nX and nY

In case we ever want to compile our code into a beginners how-to-program book.

VB

' Assign the value to the variable
i = 10

We just can't have enough comments!

VB

' Refresh the screen
RefreshScreen

Keep an active log inside your code, you never know when you need it (SVN alone isn't good enough)... (date, initials, ticket number).
The fun thing about this is that when a fix is larger than a few code files it does not have to be commented.
If it is only a few code files chances are this piece of commentary is copied to each of them, sometimes in multiple places in the same file.

VB

' 2012-09-22 N Ticket # 666.
' The client wants this fix because... Bla, bla, bla...
CallSomeMethod

Some of this guys methods are commented line by line with these kinds of comments... WTF | :WTF:

I tried to talk to him about it, but he's convinced code is unreadable and can never be understood easily by just reading it. Comments are absolutely necessary if you, or another programmer, ever want to quickly make changes to the code. This is the same guy who thinks making a seperate class for almost every method (and randomly make it non-shared/non-static or shared/static) makes code more clear and readable (and single responsibility principle is a bonus!) and who just doesn't use access modifiers out of laziness or indifference...
Of course he is my boss and has eight years of experience where I have only two (how often I had to hear that) so when I disagree with him I'm rude and inexperienced.
I guess someday I'll laugh about it Unsure | :~

It's an OO world.

C#

public class Naerling : Lazy<Person>{
    public void DoWork(){ throw new NotImplementedException(); }
}

Naerling wrote:
Keep an active log inside your code

Ugh. I hate that. At my last job, they were all about that. Half a million lines of SQL, and none of it in version control (it was all nearly lost once, except I and another person had a personal backup).

Naerling wrote:
I guess someday I'll laugh about it

When the company collapses and you find a new job with reasonable code practices.

Thou mewling ill-breeding pignut!

AspDotNetDev wrote:
When the company collapses and you find a new job with reasonable code practices.

Nah, they've been good to me and though I disagree with their code practices (and I disagree on almost everything with the guy who writes these comments) I don't want them to collapse... The funny thing is that the guy who writes these comments taught me to code! Luckily I surpassed my 'master' in every way (after about a year) Smile | :)

Although he's still the better SQL Server guy.

It's an OO world.

C#

public class Naerling : Lazy<Person>{
    public void DoWork(){ throw new NotImplementedException(); }
}

Lack of decent version control is always a bad sign. Frown | :(

Just because the code works, it doesn't mean that it is good code.

(Really) Bad smell, think we should refactor!

I like to comment my code, but only where really necessary. I also use meaningful variable names and method names so that the code is largely self-commenting. It is rare to see someone who wants both pointless comments and meaningless names, fortunately. Wink | ;)

If those things are wrong there are likely other bad practices and I would think about looking for a better place to work.

Just because the code works, it doesn't mean that it is good code.

CIDev wrote:
there are likely other bad practices

I found the same piece of code something like five times (EXACTLY the same). And then other pieces of code five times too. I found slightly different code even more often (don't make a function with input parameters, copy paste the code and change a word or two).
I found functions that were called ChangeX(ByVal x As Integer) that also changes Y and Z, ChangeY(ByVal y As Integer) that also changes X and Z etc. Worst part is, this guy coded them and still called ChangeX, ChangeY and ChangeZ one after the other.
Worst has still to come... This guy is technical director and pretends to be quality insurer (he is, but doesn't really insure anything).
He has told me I should not code MessageBox.Show("Hello"), I should've done:
Dim prompt As String = "Hello"
MessageBox.Show(prompt)
because... I don't know... He really doesn't understand I guess! If he would've coded it he wouldn't even have typed 'As String' because that's only inconvenient.
I've even seen him use switch statements for booleans! Somehow this guy doesn't like If statements...
And this guy is 'by the book' (really, if he sees something he doesn't like he always has a book that defends his position, it's freaky!)...

It's an OO world.

C#

public class Naerling : Lazy<Person>{
    public void DoWork(){ throw new NotImplementedException(); }
}

Yeah, that does sound pretty scary. It is expecially bad that he is a technical director. Sigh | :sigh:

Just because the code works, it doesn't mean that it is good code.

At our place we have a few of the "senior" apprentices staying with us in the dev team for a year. When I say "senior", they're about 19 in human years, but look about 8. I got to mentor one for a few weeks and threw him in at the deep end by giving him a MOSS WebPart to develop. For the most part, he's done an OK job and seems to be getting the hang of things, but still comes out with stuff like this:

C#

int status = (int)(Status)Enum.Parse(typeof(Status), _statusBy.ToString());
this.dataSource.SelectParameters.Add("status", status.ToString());

Given that Status is an enum with integer values, this would actually suffice:

C#

this.dataSource.SelectParameters.Add("status", ((int)_statusBy).ToString());

Bless.

At least the kid theoretically understood what he wanted to accomplish. I'm guessing that you showing him the "correct" way will result in them learning as opposed to doing it over and over again. (Silver lining)

I wasn't, now I am, then I won't be anymore.

A 19 year old producing a working but slightly inelegant solution isn't really a horror. I hope he takes your tips on board and learns the little tricks like this.

That is far better than some of the garbage I have seen well-aged developers who have been with the company for years do. From them, I'd expect something more like this:

C#

if (Page.IsPostBack == false)
{
    int status = -1;
    if (_statusBy == Status.FirstStatus)
    {
        status = 0;
    }
    if (_statusBy == Status.SecondStatus)
    {
        status = 1;
    }
    if (_statusBy == Status.ThirdStatus)
    {
        status = 2;
    }
    litStatus.Text = status.ToString();
}
string strCmdMySqlCmd = "SELECT * FROM myTable WHERE mtStatus = " + litStatus.Text + " AND mtRecordNumber = " + Request.QueryString["PleaseInjectSomeSql"];
myDataSource.SelectCommand = strCmdMySqlCmd;

Count yourself lucky to have such a bright apprentice.

Thou mewling ill-breeding pignut!

AspDotNetDev wrote:
That is far better than some of the garbage I have seen well-aged developers who have been with the company for years do

Don't get me started, I'll be here all night and it's a friday.

AspDotNetDev wrote:
Count yourself lucky to have such a bright apprentice.

I do, don't get me wrong - I was just surprised that despite his ability to understand and get on with things fairly autonomously he still does some slightly daft stuff. For a measure of how bright he is, he already hates MOSS development, and that after only a couple of weeks. Clever lad.

jim lahey wrote:
despite his ability to understand and get on with things fairly autonomously he still does some slightly daft stuff

Don't we all do that from time to time? Smile | :)

It's an OO world.

C#

public class Naerling : Lazy<Person>{
    public void DoWork(){ throw new NotImplementedException(); }
}