The most creative log ever
-
When I started working in my current position four years ago, I inherited a system full of bugs and was given the task to iron out all of the bugs. The first step i though would be to turn on the logger and try to find out where and when the crashes happen. I turned on the logger and after a few minutes... BIG MISTAKE! My system crashed. It took me 2 days to re-install everything, and turn on the logger again. and it happened again. The next time i was smarter, and ghosted my disk. I also finally found the correct source code version (which was hidden among multiple copies of various versions and test made by the person), and run it through a debugger. and then i found out this little beauty:
public void errorCatcher(string msg)
{
RegistryKey key = Registry.CurrentUser.OpenSubKey(KEY_NAME_START + @"\errors", true);
if (key != null)
{
key.SetValue(DateTime.Now.ToString(), msg);
key.Close();
}
}and every method in the system had the same reference in it's catch clause:
catch (Exception exception) { errorCatcher(exception.ToString()); return ""; }I took me two weeks to rewrite the whole thing, throw away 90% of the code, and roll out a bug free system. (I still keep the original code as proof, as no one believes me when i tell people about it.)
-
When I started working in my current position four years ago, I inherited a system full of bugs and was given the task to iron out all of the bugs. The first step i though would be to turn on the logger and try to find out where and when the crashes happen. I turned on the logger and after a few minutes... BIG MISTAKE! My system crashed. It took me 2 days to re-install everything, and turn on the logger again. and it happened again. The next time i was smarter, and ghosted my disk. I also finally found the correct source code version (which was hidden among multiple copies of various versions and test made by the person), and run it through a debugger. and then i found out this little beauty:
public void errorCatcher(string msg)
{
RegistryKey key = Registry.CurrentUser.OpenSubKey(KEY_NAME_START + @"\errors", true);
if (key != null)
{
key.SetValue(DateTime.Now.ToString(), msg);
key.Close();
}
}and every method in the system had the same reference in it's catch clause:
catch (Exception exception) { errorCatcher(exception.ToString()); return ""; }I took me two weeks to rewrite the whole thing, throw away 90% of the code, and roll out a bug free system. (I still keep the original code as proof, as no one believes me when i tell people about it.)
Elephant me! :wtf: A registry logger? And people wonder why it's getting harder and harder to access it... :sigh:
The only instant messaging I do involves my middle finger.
-
Elephant me! :wtf: A registry logger? And people wonder why it's getting harder and harder to access it... :sigh:
The only instant messaging I do involves my middle finger.
-
From that day on, whenever i need to get into this person code, i start pounding my head on the wall (literally) and swear. My boss then calls from the next office: "is it ###### code again?" X|
I take it the person in question has departed the company?
The only instant messaging I do involves my middle finger.
-
I take it the person in question has departed the company?
The only instant messaging I do involves my middle finger.
-
Guy Lavi wrote:
Obviously.
Because you aren't on remand awaiting a murder trial? :laugh:
The only instant messaging I do involves my middle finger.
-
Guy Lavi wrote:
Obviously.
Because you aren't on remand awaiting a murder trial? :laugh:
The only instant messaging I do involves my middle finger.
-
When I started working in my current position four years ago, I inherited a system full of bugs and was given the task to iron out all of the bugs. The first step i though would be to turn on the logger and try to find out where and when the crashes happen. I turned on the logger and after a few minutes... BIG MISTAKE! My system crashed. It took me 2 days to re-install everything, and turn on the logger again. and it happened again. The next time i was smarter, and ghosted my disk. I also finally found the correct source code version (which was hidden among multiple copies of various versions and test made by the person), and run it through a debugger. and then i found out this little beauty:
public void errorCatcher(string msg)
{
RegistryKey key = Registry.CurrentUser.OpenSubKey(KEY_NAME_START + @"\errors", true);
if (key != null)
{
key.SetValue(DateTime.Now.ToString(), msg);
key.Close();
}
}and every method in the system had the same reference in it's catch clause:
catch (Exception exception) { errorCatcher(exception.ToString()); return ""; }I took me two weeks to rewrite the whole thing, throw away 90% of the code, and roll out a bug free system. (I still keep the original code as proof, as no one believes me when i tell people about it.)
You made it up!!! It can't be. If it's true it can be easily will a gold medal. I can't understand why such a creative people was send on his way. Company's greatest lost...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
You made it up!!! It can't be. If it's true it can be easily will a gold medal. I can't understand why such a creative people was send on his way. Company's greatest lost...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
When I started working in my current position four years ago, I inherited a system full of bugs and was given the task to iron out all of the bugs. The first step i though would be to turn on the logger and try to find out where and when the crashes happen. I turned on the logger and after a few minutes... BIG MISTAKE! My system crashed. It took me 2 days to re-install everything, and turn on the logger again. and it happened again. The next time i was smarter, and ghosted my disk. I also finally found the correct source code version (which was hidden among multiple copies of various versions and test made by the person), and run it through a debugger. and then i found out this little beauty:
public void errorCatcher(string msg)
{
RegistryKey key = Registry.CurrentUser.OpenSubKey(KEY_NAME_START + @"\errors", true);
if (key != null)
{
key.SetValue(DateTime.Now.ToString(), msg);
key.Close();
}
}and every method in the system had the same reference in it's catch clause:
catch (Exception exception) { errorCatcher(exception.ToString()); return ""; }I took me two weeks to rewrite the whole thing, throw away 90% of the code, and roll out a bug free system. (I still keep the original code as proof, as no one believes me when i tell people about it.)
WTF?!?!? :wtf: :omg: :wtf: :omg: :~ :wtf: :wtf: :wtf: :omg: :omg: :wtf: X| X| X|
Keep Clam And Proofread -- √(-1) 23 ∑ π... And it was delicious.
-
Guy Lavi wrote:
Obviously.
Because you aren't on remand awaiting a murder trial? :laugh:
The only instant messaging I do involves my middle finger.
-
Elephant me! :wtf: A registry logger? And people wonder why it's getting harder and harder to access it... :sigh:
The only instant messaging I do involves my middle finger.
OriginalGriff wrote:
A registry logger?
I could top that, believe it or not, if it wasn't for the non disclosure agreement of one of my former employers.
My Android apps in Google Play; Oakmead Apps
-
When I started working in my current position four years ago, I inherited a system full of bugs and was given the task to iron out all of the bugs. The first step i though would be to turn on the logger and try to find out where and when the crashes happen. I turned on the logger and after a few minutes... BIG MISTAKE! My system crashed. It took me 2 days to re-install everything, and turn on the logger again. and it happened again. The next time i was smarter, and ghosted my disk. I also finally found the correct source code version (which was hidden among multiple copies of various versions and test made by the person), and run it through a debugger. and then i found out this little beauty:
public void errorCatcher(string msg)
{
RegistryKey key = Registry.CurrentUser.OpenSubKey(KEY_NAME_START + @"\errors", true);
if (key != null)
{
key.SetValue(DateTime.Now.ToString(), msg);
key.Close();
}
}and every method in the system had the same reference in it's catch clause:
catch (Exception exception) { errorCatcher(exception.ToString()); return ""; }I took me two weeks to rewrite the whole thing, throw away 90% of the code, and roll out a bug free system. (I still keep the original code as proof, as no one believes me when i tell people about it.)
I can imagine a few situations in which this could actually make sense. But of course, it is not meant to be permanently turned on, especially if a lot of exceptions are caught.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
-
I can imagine a few situations in which this could actually make sense. But of course, it is not meant to be permanently turned on, especially if a lot of exceptions are caught.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Do not feed the troll ! - Common proverb
