I'm a 3rd-year Electrical Engineer and I've taken a intro to programming course pretty much for lulz. I've been thrown a couple of classes from a lab partner and I have to come up with a UML Sequence diagram using Enterprise Architect. I have been able to successfully gen a Class Diagram from source engineering but haven't been able to come around to a Sequence. Is there any way to work this out or am I going to have to read my lab partner's shitty code.
UML is so last decade. Get with the new OMG (literally!) Enterprise Business Scalable Process Management Pointy Haired Performance Collaborating Synergistic Paradigm!
I'm glad there's OMG. It unites all kinds of bullshit, so it gets easier to avoid. Anything coming from OMG is pure, utter bullshit. I don't know what kind of enterprise fucktards work there, or if it's all just a big prank or an inside joke. At times, OMG's shit really looks like a prank, the kind of joke paragraph about professional multi-tier mission-critical scalable enterprise-ready solutions for your business we write over here. I'd be somewhat surprised if they really took all this for serious; I mean, how could human beings working with something related to computers be this useless! My goodness, they are a waste of air and food.
>>6
We are intimately familiar with ENTERPRISE $KEYWORD and therefore qualified to assess its bullshittery.
Name:
Anonymous2007-09-11 0:48 ID:mdTyL85e
UML is one of those things that if you need it, you're going to hate every moment of it. It's like a warning signal: just like the yowls of some wild animal in the bush makes you walk the other direction, the coming of UML means it's time to start shopping your resume around.
Same with XML, component or aspect-oriented programming, Oracle, Java, C++, or a language provided by only one vendor.
PHP and MySQL are the other end of the faggotry spectrum, but at least you won't feel like committing suicide after wasting your life in a cubical farm surrounded by fat sweaty men banging out ENTERPRISE BUSINESS SCALABLE SOLUTIONS code.
Name:
Anonymous2007-09-11 1:43 ID:WZas2IPk
UML was designed to be abstract. However, ENTERPRISE BUSINESS asshattery has required it to be absolutely concrete down to the full classes and methods, templates, etc. That's NOT what UML was intended for; it's supposed to be a helpful representation to describe IN GENERAL how SOME things should work, then you can program your specifics later.
Doing concrete specifics is called PROGRAMMING, so you end up PROGRAMMING your whole ENTERPRISE BUSINESS SOLUTION in UML and then again in your ENTERPRISE SCALABLE LANGUAGE which is dumbfuckery at its greatest.
And people need to use the -ery suffix more.
Name:
Anonymous2007-09-11 1:45 ID:80S5dVe1
Too much suffixery going on
Name:
Anonymous2007-09-11 1:49 ID:WZas2IPk
ONE WORDERY, THE FORCERY INDENTATIONERY OF CODERY, THREAD OVARY.
>>17
They need to do way instain suffixery who ovary thier threads.
Name:
Anonymous2007-09-11 7:56 ID:8XarD/4+
Thread ovary is now meme, which I invented.
Name:
Anonymous2007-09-11 9:12 ID:klBpFLSF
>>12 the coming of UML means it's time to start shopping your resume around. Same with XML, component or aspect-oriented programming, Oracle, Java, C++, or a language provided by only one vendor.
I must quote this man's words of truth.
Name:
Mr. Likes To Age Threads2007-11-11 23:12
（￣へ￣） Hello. I am "Mr. Likes To Age Threads". I do believe this is a thread in need of Age, so I would like to Age it. That is why my name is "Mr. Likes To Age Threads".