- 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
Admin
Admin
Na na na na na na na na na na katamari enterprise...
Admin
Admin
There, FTFY
Admin
Admin
Wow, messed that up, didn't I?
Admin
We don't have a class dependency diagram like that 'cause we don't need no stinking classes ;-)
Admin
I agree with you on no classes. As matter of fact, I missed every single class on OO, AI, DB Design while in college. When so many movies releasing, it is much more relaxing to spend time in talkies, than spend time in class.
Admin
Admin
It looks to me like a useful diagram for explaining that my employees are nincompoops who can't build a nice and simple system that just does what it needs to do, and that I need to replace the lot of them.
Admin
Captcha: laoreet - the noise Nagesh will make when I whip him with his mouse cord
Admin
I'm pretty sure that somewhere within that circle there is a pentagram...
Admin
Admin
Admin
Admin
This looks like a job for ....Graphviz!
Admin
Funny, that looks like our Workflow diagram...
Admin
Huh. And other MS developers get all pissy when I tell them WWF and BizTak are complete crap.
Captcha: veniam - A venereal disease contracted in Vietnam.
Admin
Madarchod, No student in India has goats. You have been found out.
Admin
Where's the EnterprisePojoBeanAbstractSessionFactoryManager? :) And of course, it HAS to be version 1.701, it IS Enterprisey after all!
Admin
Admin
A massive enterprise project has a lot of dependencies?
Oh the horror, quick captain hindsight, what should we have done?!
Admin
"Talkies"? Did this Naresh grow up during the roaring 20's?
Admin
Been there, debugged that.
You forgot to mention that the OS is past end of life, there's no source control of any kind, the versions of Perl, PHP, Java, and the Apache Webserver on the server are obsolete, there's only the production server, and the total mess is used to run more than one enterprise application.
Admin
Were approaching this problem all wrong, seeing how there are obviously a large number of people here named Nagesh, we should come up with a standard naming system. One that is, robust, portable, and efficient. (And fair)
So, for fairness, "First come first serve" Seems like a good way to handle such a thing. The first person to post on an article is Nagesh1 (We all have a number, that way nobody's name is too ugly.) the second Nagesh2 and so on.
Of course, this is a fair solution, but not a efficient one, we can hypothesise that there are far more then just three people named Nagesh here, and after nine we'll hit double digits, and after double digits we'll be in the hundreds, it'll be impossible to keep track of, so, to make the standard efficient, we'll use the alphabet instead, each time a new Nagesh object (Person) is created, we'll append a letter to the end.
Thus, the first Nagesh will be Nagesha and the second will be Nageshb, and so on respectively. Of course, this system is efficient and fair, but not robust, after all, how could an outside observer tell that there's a system at all if there's just random letters at the end of our names? They couldn't, plus, it'll be an eye sore once we go past z and start using more then one letter.
Because of this, we'll have to separate Nagesh from it's letter denomination, so now the first Nagesh to post will be Nagesh/a and the second to post will be Nagesh/b, and so on for the rest of the people who post that happen to be named Nagesh. Of course, this system is fair, robust, and efficient, but it's not portable yet, don't worry, not a problem.....
PS. I'm pretty sure I can code, Poe's law is in full effect here.
Admin
I suppose these guys are having kittens the deployment day.
Admin
Being pendantic, but here goes...
Is the small picture really the box shown on the big picture? The angle looks wrong...
Perhaps the zoomed-in version comes from slightly further anti-clockwise?
Admin
That looks like a petri dish with some kind of developer eating disease...
Admin
That way you'd get an evenly coloured shape. ..with maybe a couple of holes for eyes..
Admin
Finally someone notices. The zoomed area is not from where it is claimed to be from. My guess is that it is from the point a few minutes clockwise.
Admin
Well yeah, anything looks bad naively arranged in a circle. Run a genetic arrangement algorithm with the fitness function set to minimize total length of the connections, and it might turn into something a bit more recognisable.
Admin
Admin
No real WTFs today then, just like last week. Woo hoo, a dependency diagram. Don't you retards realise that any dependency diagram for any sufficiently complex system will look a lot like this? Stop fucking around with crappy "articles" that aren't even articles (I'm sorry but a single JPG does not an article make) and do some real fucking work you lazy cunts.
Admin
There's a very good reason the dependency graph looks like that. Hint: It's a bit of a dark art.
[image]
CAPTCHA: Deruspicy - reading code like entrails to predict possible execution outcome.
Admin
That anglerfish looks a lot worse because of the link to "system" or to "generics", can't really make it out. Either way it's in the .NET framework, and virtually every class is dependant on those.
Admin
Admin
If it make you both feel any better, I am in the same situation. Our database has no explicit foreign key constraints; just implicit ones.
You can delete data with impunity and never have to worry about pesky things like whether the logical parent record exists in another table.
Admin
Stupid Akismet, there's not even a link in my article, so why do you believe it is spam?
Admin
Looks like the design for Van Halen's guitar
Admin
Admin
Right, until you try to join on them, which is where I am now experiencing a bug that never showed up in testing... Without constraints, it's not a matter of IF your data will eventually be shit, it's just a matter of WHEN, and when the code that is used to manage these relationships is written like this:
... then it tends to happen much sooner than later.
Admin
Wait, what?
Admin
Admin
Maybe you were being sarcastic, but aren't there enough IPv6 addresses to give every atom in the universe its own IP address? I know there are enough GUIDs to do that, and I think IPv6 addresses are the same length. So, no, that wouldn't use up all of the IPv6 addresses. Still, it's a pretty complicated diagram...
Admin
We get some data that includes client transactions, client names, account information, etc. Sometimes the transactions come before the client and account information. Sometimes the transaction information is correct but the client or account info has the account number slightly wrong (it might have been hand-entered at some point in the chain).
We don't want to reject the transactions just because the client doesn't exist yet -- we usually get the correct client information eventually. And, in cases when it's important, we can figure out who the client was. It's not always important (the aggregate information is still valid even if we don't know what clients a few of the transactions should be linked to).
So, we can't enforce referential integrity, and our database is not COMPLETELY shit, just partly. :-)
Admin
Admin
Admin
Admin