One could not have possibly made a more impossible to deal with steaming pile of fetid GUI generating code.
Pfft, you haven't seen my old GUI code. It read in from an XML-like text file, where a typo in most places would cause the program to crash. Each GUI element was encapsulated, encased in lead, then buried in cement; with hacky backdoors to access functionality I forgot I needed back when I originally created it, encapsulated it, encased it in lead, and buried it in cement. Also, it put the elements in containers which were similarly encapsulated, encased in lead, and buried in cement. The containers had the elements in a list, accessible by an id value; to access an element, you gave it the GUI element's id value and any other necessary information, and it would run the function to do what you wanted. Problem was, these id values were automatically assigned based on where in the XML-like text file the GUI elements were placed; the only way to figure out the id was to manually count how many elements came before it in the file.
It's true. Just ask any programmer. Most programs run on Black Magic, rather than anything logical.
Indeed it is. We sacrifice time, get code 'done,' then come back the next day, having forgotten all the details of what we had done during the sacrificed time of the previous day. We then either continue doing what we think needs doing (which typically involves re-making something we already implemented, usually in an inferior manner), or look at the code we wrote the day before. The latter results in 1 of 2 possibilities: A. Wondering how the hell it's all working like it should. B. Wondering what the hell we were thinking when we wrote this code which obviously won't work and does absolutely nothing which could possibly be construed as, or tied into, anything useful.
Author
Topic: Things that made you RRRRRRAAAAGGGGEEEE today: Trust-o-nomics Edition (Read 3776696 times)