I hate UML.

[notfred]

Ohh, let's draw little diagrams! We could just write this crap down, but no, let's spend all day making graphs that tell us things we already know!

Fvcknig waste of time.

 

[EagleKeeper]

Originally posted by: notfred
Ohh, let's draw little diagrams! We could just write this crap down, but no, let's spend all day making graphs that tell us things we already know!

Fvcknig waste of time.

New buzz word. Also, when used "properly" it can help organize and then allow documention/validation down the road.

Personally I agree with you, but some want it to be a standard to justify spending big $$ on a tool.

 

[lozina]

Personally I find that using UML to design an application is the biggest waste of time.

Maybe once the app is done and the unforseen hitches in your design are ironed out, it's a nice little toy. Though when you got projects lined up like I do there's really no time to do this 'leisurly' chore

 

[DaveSimmons]

Right up there with Xtreeme Programming. Do the Dew!!!!

Like explaining to the n00b looking over my shoulder why I wrote something the way I did is really going to make me be more productive :roll:

 

[yllus]

UML is extremely useless.

 

[Kilrsat]

Originally posted by: DaveSimmons
Right up there with Xtreeme Programming. Do the Dew!!!!

Like explaining to the n00b looking over my shoulder why I wrote something the way I did is really going to make me be more productive :roll:

If it isn't a n00b over your shoulder, but someone more your equal, you two should be able to play off each other and build a solid application without too much wasted time. Especially if you two think alike, since once they see where you're going with the current little bit they can already be thinking of the implementation of the next segment.

But yes, if you have to constantly explain what you're doing because the other person can't follow along it is a waste.

 

[Nothinman]

UML rocks =)

 

[DaveSimmons]

Originally posted by: Kilrsat

Originally posted by: DaveSimmons
Right up there with Xtreeme Programming. Do the Dew!!!!

Like explaining to the n00b looking over my shoulder why I wrote something the way I did is really going to make me be more productive :roll:

If it isn't a n00b over your shoulder, but someone more your equal, you two should be able to play off each other and build a solid application without too much wasted time. Especially if you two think alike, since once they see where you're going with the current little bit they can already be thinking of the implementation of the next segment.

But yes, if you have to constantly explain what you're doing because the other person can't follow along it is a waste.

I can see it helping a pair of inexperienced people, or in a mentoring situation where the experienced person watches the junior developer, but I'm experienced enough that I'd never be stopping to discuss anything. My partner would be bored and/or confused watching me type silently for hours

Usually when I get stuck it's on something obscure like figuring out how to extract a bitmap from the IE web browser control, or in reverse-engineering the half-documented SWF file format. Then it's off to Google or just going through trial and error.

 

[ArmchairAthlete]

Couldn't it help others who are looking at your program see how it works? Before they delve into the code itself.

Ah I dunno. But I'll have to draw some UML stuff soon I am sure. We only talked about it a bit so far.

 

[royaldank]

UML has it's place. 2 or 3 programmers at a company probably don't need it, but larger places can put it to good use. If you can really get it down, it can simplify programming and do some of the work for you. Helps in really large projects with project managers that aren't coders. Helps with the specification of the development process.

 

[kamper]

Originally posted by: DaveSimmons
Right up there with Xtreeme Programming. Do the Dew!!!!

Like explaining to the n00b looking over my shoulder why I wrote something the way I did is really going to make me be more productive :roll:

Of course it doesn't make you more productive. But it gets the noob up to speed a hell of a lot faster, if you do it well, which makes the team more productive in the end.

As for the UML, just because it didn't serve your purposes doesn't mean you have to run around bashing it. If someone told you you have to use for every piece of software you write then you can bash them. There are situations where it's very useful as a descriptive tool when used in moderation.

The argument that it just gets in your way and slows you down could is just as easily (and often) applied to testing. I think we can all agree that testing is one of those painful but necessary things if you want decent code.

 

[Zugzwang152]

Agreed, I am taking my Design class this semester, and I hate UML soooo much. It's completely useless so far, we'll see if it actually comes in handy during larger projects later in the year...