|visits||member for||3 years, 3 months|
|seen||Jun 28 at 19:20|
Programmer of stuff. Also something of a UNIX addict.
You can check out my 1337 haxx0r code projects at http://code.arp242.net
If you feel the need to contact me in private, you can email me at firstname.lastname@example.org, but please don't ask technical questions, those belong on Stack Overflow :-)
|bio||website||arp242.net||visits||member for||3 years, 3 months|
|location||Eindhoven, Netherlands||seen||Jun 28 at 19:20|
Should I always start with UML as a good practice when designing classes?
I don't think there is "one true answer" to this; I strongly dislike starting with an UML diagram, and would rather prototype first (and use UML afterwards to document), but I also know people who very much prefer to start with UML before starting to program... IMHO one of the biggest disadvantages of starting with UML is the tendency for everything to get too complicated than what it really needs to be... YMMV ...