MAN this aggrivates me (programming)

[280Z28]

This is a crash:

The application has encountered an error and needs to close

This is an assert, NOT A "Crash"

assert( ptr != NULL || !"NULL argument not expected" );

Assertion Failed

This is an EXCEPTION, NOT an "Assert"

throw new ArgumentNullException( "chair" );

Unhandled Exception

Man I get this crap from other devs here who supposedly know what they're doing and then I go hunting for the problem they reported, but they keep reporting the wrong things.

They're sitting here behind me right now talking about adding more asserts to a C# project they're working on to catch some problem.

 

[movax]

ASSERT(_T("no clue about your post, please add more background info ><"));

 

[zman099]

tell them to go back to school. hehehehe just messing

 

[MonkeyShave]

Ask for screenshots of the failure and/or unedited log files.

Most people speak ambiguously. Unfortunately, neither you nor I can expect that to change.

Screenshots demonstrating a failure (hopefully accompanying a mostly-helpful set of steps to reproduce) don't lie, nor do original log files.

Consider adding your own handlers for unexpected exceptions and assertions (for example, replace the system-provided assert) which will record a stack trace and display module versions/build times.

 

[280Z28]

I can deal with this from users just fine. The problem is with devs that make these mistakes.

Newbies should say they encountered and "error" if they don't know what the specifics are. That's generic enough to tell me that it could be any of the above.