addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartexportfacebookfolderfullheartglobegmailgoogleimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Re: [gctechspace] Door documentation

From: Steve D.
Sent on: Saturday, June 23, 2012 9:29 PM
 On Sat, Jun 23, 2012 at 8:58 PM, David Tangye <[address removed]> wrote:
On Sat, Jun 23, 2012 at 8:44 PM, Steve Dalton <[address removed]> wrote:
I used to do UML when I did Big-Design-Up-Front waterfall stuff 5-10 years ago - but these days you don't really see them much. They might still have a place in some projects.
Its interesting that you almost seem to imply that UML is mainly associated with waterfall.

I've just seen UML/Rational stuff used mainly in the big waterfall projects - just my experience, I haven't done a waterfall project since I worked at the government about 4 years ago..... and that went exactly how my might expect for the QLD gov one.
It's not that we don't do design in Agile - just not *that* kind of design..... fully automated tested working code is a far better use of time than creating diagrams that's all. Good specs and code that can be linked directly to these specs through tests are the best documentation you can have.
Yes but you do not have that here.
We should have - writing tests would be a much better way to understand the code in my humble opinion.
Just my opinion - there are probably others that could explain it much better than I can.
I do not see any problem with the clarity of your explanation of your understanding and perspective.

I also find it sad that so many good practices, badly used, have fallen out of favour, not because the concepts were bad, but simply because too few people did it well, and so the concept got bad press but the herd of useless or mediocre practitioners never do. Some things never change.

Completely agree - such is this industry I'm afraid. Agile itself is not immune from this  and it is almost an dirty word now with a lot of the people that have been doing it since the start. So many people have bent and warped it to suit their needs. I must try not to use the word actually - we usually replace it with the word "Racoon" as this is just as meaningful. There is a podcast on codingbynumbers with Craig Smith where we talked about this exact thing - worth a listen.... 

Anyway - back to the subjects - I'm not anti-UML.... I just think tests are a better way of understanding code and leaving a nice legacy of others. When I see some new code one of the first things I usually do is go through the tests - even step through them in the debugger if I have to.


Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by David Tangye ([address removed]) from Gold Coast Techspace.
To learn more about David Tangye, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages

Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]

Make a pledge on our shelving/storage project here:

Steve Dalton, President
Gold Coast Tech Space
3b/51 Johnston St, Southport, Q 4215
+61 [masked]

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy