- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Perhaps the report writers just didn't want all their effort making a fantastic report to go to waste, having people simply look at nothing but the dot. Us coders can be too proud sometimes.
Admin
Because */images/mood/ green.JPG yellow.JPG red.JPG
Is SO complex and difficult? That explanation of why implementing it is such a bunch of nonsense.
Admin
There's about ten tons of stupid in this thread.
All the stuff about problems with displaying the moods was a LIE, you PHB-grade morons.
Admin
Admin
Admin
Admin
Re: UNCF
Admin
From the TODO comment I extrapolate that:
Some database re engineering needed done to integrate with the new release. When it came time to access the mood procedure, the developer decided to simply add a TODO for at the time, probably because the re engineering that had been done so far didn't include the mood functionality.
Because the TODO says to do the schema refactoring before the schema grows too large to do it easily, that means if the developer would have just done the refactoring right there it wouldn't have been too bad to implement.
Time goes by and the schema gets updated/modified/new tables/new rows, all without consideration for the mood feature.
So the real reason the mood feature didn't get added in is because they completely forgot about it during the new release development, and to add it in now would require going back through and redeveloping the release.
Then when the customer inquires about why one of their features are gone, rather than just saying, "Oh... we forgot about that," they make up some big long stupid story.
Admin
HTH
Admin
Admin
Admin
LOL...seriously, you ever notice on Star Trek that whenever they open a file or a program if they get attacked or something they are in jeprody of loosing it. Apparently when the computers of the future open a file they will not leave a copy on disk.
Admin
YES!!!!.... That's exactly what I am saying!!!
Admin
naaaah..
You also missed some critical steps:
Admin
I guess the more entrenched people were older ... and used to the "not in the mood" excuses. Doesn't take long for a grown man to learn these and apply them at work, y'know!
Wooo! I've got the entire alphabet in random order as a captcha!
Admin
Nice one ;-)
Admin
At least this page hasn't been redirect to Google ... or worse ... yet.
WTF is a suscipere?
Admin
I mean, it's obvious that was the only solution left, wasn't it?
(Unless you count adding a single "getReportStatus()" function to the various layers)
Admin
alt text?
OK!Admin
No-one seems to have picked up on the fact that this was a GUI update, hence it is not completely out of the question that database changes were in fact "out of scope" which could indeed make it impractical to implement the 'mood'
Perhaps the comment was left in the stored proc as a reminder so that when db changes did become in scope they could get around to doing it properly.
Admin
Admin
I bet it would have been simple if they asked for TEXT to change color instead of a graphic image.
Admin
But if a blind person reads the report, he sees neither shape nor color...
Admin
Admin
I give him an empty picture frame to use as a monitor, and make everybody promise not to tell!
Admin
Maybe I am missing something obvious? But why didn't they just code the icons into text and store in the DB?
For example: http://software.hixie.ch/utilities/cgi/data/data
Admin
generating images? wtf? so they are just too dumb to have three images on their webserver and write into their reports which one is being used?
Admin
Admin
Now the primary key will change when the mood of the report changes. Every routine/application that wants to retrieve the report by ID needs to be updated to handle this.
Anyone who suggests such a "solution" should better have a damn good reason why an additional column in the database table is not possible.
Admin
People, read this comment above :)
Here is what happened:
manager says: "We want the dot". dev thinks: "oh crap, the dot... forgot about that one" dev says: "unfortunately the dot is a lot of work because of the image processing (manager hears: white noise) scaling load balancing file system corrupt bad millions millions...(manager thinks: woosh), wouldn't you agree?" manager says: "Ah yes of course, that makes sense, good work" manager thinks: "face saved - score!"
Later on manager takes a look at the devs notes and realizes that he has been had. manager thinks: "wtf!?"
Admin
Ouija board!
Admin
Win! I Lol'ed.
Admin
Why? I've written a custom web browser.
Admin
TRWTF is the custom web browser
Admin
I have written systems like this (balanced scorecard/dashboard/etc...) and sometimes it's easy (e.g. fixed red/green/blue that you can set in a DB field) and sometimes it's more difficult(e.g. allowing the user to define variables representing data from various feeds, easily manipulate it, and define feed-specific criteria for dynamically determining if red/green/blue). Depending on how the business/software groups work together, I could see push back on getting this "in the door" if it was never formally agreed on and if project scope has a tendency to explode.
Just my $0.02 worth...
ALTL
Admin
To late by the time you posted this it was an Epic Fail.
Admin
IF they're too stupid to tell shapes apart, they're probably not working there. Say what you will about middle management, they can all at least dress themselves.
Admin
I know: Green cross, yellow star, pink triangle (inverted). That way, we can start some serious shit when the lawyers get involved.
Admin
My understanding is that the developers didn't want to implement the feature. I think the schema was the least of their worries... Implementing the frontend would have been much more troublesome then the backend, IMO. I'm not even really sure how you're supposed to know what "mood" a report is in... Maybe this is because of my hatred for paper though.
Nice. ;DAdmin
Admin
Well, that would explain why he cannot see or hear...
Admin
Except for the code comment posted at the end where they say "let's do this before the schema [backend] gets too hard to change".
Which, from what I can tell, was the funny part. Not that anybody got it. OK, three people got it.
Out of the rest:
I'd do a pie chart but I'm afraid someone would photograph it on a wooden table in an attempt at humor.
</cbg>Admin
OMFG dude, I love Windows 95. I still use Windows 95 to this day. Best OS ever released!
RD www.FireMe.to/udi
Admin
...so there are only three icons: #1: :-) [green] #2: :-| [yellow] #3: :-( [red]
So what's with all the dynamic image generation?!?!? Why can't they just put three image icons on the server and reference the right one?
Admin
This normal practise at IBQ The next version will not be a update but a upgrade; read $$$
This version will have moving avatars on every report.
Admin
Admin
Lol, I was thinking the color coded words as well, why mess with images at all?
Admin
Everyone wondering what's so hard about loading an image, please read below.
The stuff about loading images was a red herring that worked on the management. In reality, the database had progressed to a point where it would have taken more work to add a place to store the 'mood' than they were willing to do. The WTF in this case was that one of the coders realized this early on, and left a TODO for himself noting that they should add this to the database before it becomes unwieldy.
There is an extra bit of irony in the fact that many of you were raked in by the "dynamic image" like the company's management was.
I will admit that I had to re-read the last half of the story to get it. Now get the hell off my lawn.
Admin
Forgot to add: the real WTF may very well be that these guys are either unwilling or incapable of implementing a feature that the customer asked for. But we can take two morals from this:
Things that seem easy to an outsider are not always easy in fact. And everything seems easy to your boss.
They sufficiently bs'ed their way out of doing their job. Proving once again that if you have the right combination of smarts and laziness, the world is your oyster.
Admin
I kinda like the idea of bombing management with technobabble if you don't want to implement a feature. Makes things so easy...
Adding a 'print report' button? Are you nuts? We'd need to serialize the whole XML stream into design patterns for that. If we managed to extract the algoritm at all, we'd still have to establish a stable feedback loop to feed the entity code into before our data service overloads. And you don't even want to think about what happened if the interface hub calibration were misconfigured...