@ubersoldat said:
Would have been funnier if you were a Java shop :)
Was waiting, nay hoping for that other shoe to drop...
a shame for that would have been HAAAlarious
@ubersoldat said:
Would have been funnier if you were a Java shop :)
Was waiting, nay hoping for that other shoe to drop...
a shame for that would have been HAAAlarious
Ahh the Web.Config file. Glorious!. How do you read this wonderful thing?
XmlDocument x = new XmlDocument(); x.Load(HttpContext.Current.Request.PhysicalApplicationPath + "web.config"); XmlNode node = x.SelectSingleNode("/configuration/system.web/authentication/forms"); if (node != null && node.Attributes["timeout"] != null && !String.IsNullOrEmpty(node.Attributes["timeout"].Value)) _sessionTimeout = Convert.ToInt32(node.Attributes["timeout"].Value);
How would you make an element "blink" with JavaScript and jQuery?
Some of you might say http://api.jquery.com/animate/
others might say.....
window.setTimeout(function(){ $("#AttestationNag").css('background',''); window.setTimeout(function(){ $("#AttestationNag").css('background','#EFC1CE'); window.setTimeout(function(){ $("#AttestationNag").css('background', ''); window.setTimeout(function(){ $("#AttestationNag").css('background', '#EFC1CE'); window.setTimeout(function() { $("#AttestationNag").css('background', ''); window.setTimeout(function() { $("#AttestationNag").css('background', '#EFC1CE'); window.setTimeout(function() { $("#AttestationNag").css('background', ''); window.setTimeout(function(){ $("#AttestationNag").css('background', '#EFC1CE'); window.setTimeout(function() { $("#AttestationNag").css('background', ''); window.setTimeout(function() { $("#AttestationNag").css('background', '#EFC1CE'); window.setTimeout(function() { $("#AttestationNag").css('background', ''); }, 400); }, 400); }, 400); }, 400); }, 400); }, 400); }, 400); }, 400); },400); },400); },400);
I've been battling this guy at work for 3 months now trying to get data in a logical manner rather than this jumbled, piece of crap. This data is used to render a UI. It should be pretty straight forward. Heres the input type, heres the label to apply to the input and heres the value if one already exists. Simple right?
Today I'm told that one of the properties of the data used to determine what type of field to render is causing issues with the validation logic.
Me: "Ok, so then how about we add a new property to the data and the UI can just read that and then the validation logic can use the other property."
Him: "We are going to send it to you in the data format property."
Me: "Isn't that field used for telling the UI the format of the data? not the type of field to render? Besides it doesnt make any sense for the UI to read 3 different properties to determine the field type. Also, I have to start to add extra conditionals in the code for these 'special' cases. A few more of these and the code is going to be a nightmare to maintain."
Him: Its only an if statement, we have to do all this extra stuff.
Me: I need the data in a logical, consistent manner.
Needless to say this gets escalated to management. Management listens to what I have to say and says ya that makes sense. Why dont we just have one place to read the data from. Management goes to talk to the other guy, comes back and says, they are not willing to change their design.
I've since asked for reassignment.... good thing my resume is up to date.
I'm working on a project that, long story short, is a simple data driven UI with some more complex validation in the back end. Basically, the requirement is to output various types on input boxes to take data values from the user that are dates and values in any combination.
For example, we might have one data point that needs just a date. We then may have another data point that is a date and a value. Further we could have a date and 2 values.
I recommended a data format that would be the most versatile, something on the order of a data point observation with a list of fields associated to that observation
Observation { Field Field Field ... Field }
Parsing is simple, life is good right?
Enter William Ted Franken, we prefer to refer to him by his initials. The data is being ordered in date value pairs.
I've been spending the past month trying to nudge the iceberg that is this guy, into a more sane data format citing reasons of simplicity and maintainability. Yesterday everything came to a head and our friend told me "sometimes simple isn't the best approach"
I nearly lost my shit...
@bstorer said:
- We have a black president now who wants to kill your grandmother.
- As part of a vast conspiracy to make themselves seem less worthless, Canada invented something called "Winter Olympics," supposedly held in something called a "Vancouver," wherein they were victorious in such imaginary sports as "hockey" and "curling" and, most ridiculously, "women's hockey."
- Domino's Pizza completely changed their recipe and proudly proclaim that they bested Papa John's in a taste test, which has to be the lowest the bar for success has ever been set.
I see then the terrorists have won then. I suppose you're going to tell me that Michael Jackson is dead and Rick Astley made a comeback?
At least I still have my internet porn.....
@bstorer said:
Your story is fine -- I mean, it's a decent WTF -- but I'm more interested in the thought processes that lead you to post this. Specifically, the thought processes that lead to you posting this now. You say you worked for this company a few years back, so it's not something that just happened. And you aren't a new member, so it's not as if you joined to post this. I like to think you've been holding this in for years due to an incredibly tight and recently expired NDA that had restricted your ability to speak about the project in even the vaguest of generalizations. I'm sure the truth is far less interesting, like you're waiting for a weekly build, or killing time while your Tom Petty stalker collection uploads.
Your investigation into my story is quite thorough. Thank you for that. You are correct, the truth is far less interesting. You see, I have been in a coma for the past year and a half after I hit my head on my desk one too many times. I recently awoke and decided to post this story.
I worked for a company in the social media sector a few years back. We would deploy new instances of a web site and then proceed to "customize" it for a particular client. Part of this customization involved changing settings which involved going into the Web.Config file and changing a setting value. Then you had to make sure that the particular setting wasn't being overridden in the App.Config and then finally check that the setting wasn't overridden in the registry.
Thats right, the settings for a WebApp here stored in 3 places, including the registry on the server. When asked why this WTF, among many others, where done this way, the answer was "Yea, we probably shouldn't have done it that way, but this is how it is."
Found this in my company's codebase.
public static void ThrowException (String strId, bool bLog, object[] args)
{
String strFormat = GetString (strId);
String strMsg = String.Format (strFormat, args);
if (bLog)
throw new ApplicationException (strMsg);
else
throw new UserException (strMsg);
}