Hello!

It's been a while since I last came here, but I've missed it!  Really nice to get the email mouser  :)  And it's great to see the forum so busy!

Different priorities took me away for a while.  After doing some python stuff (my NANY 2010 mug stills sits proudly on the desk!), I went on to work with a bit of Angular / KnockoutJS, just for fun.  After a job move, I now work with people doing Android and iOS development, so I've spent the last year trying to understand mobile architecture.  It's fun, but the difference in models between web and mobile is like learning to tie shoelaces in a completely different way   :wallbash:

Since I last visited, I've moved from being a Windows guy to being an OSX guy too  :mad:

I'll try not to leave it so long next time...especially as mouser's challenges are what got me back into coding in the first place  :Thmbsup:

It's not free, but I'm now using PyCharm as my IDE.  For an IDE for a dynamically-typed language, it works very well.

I've experience of Rational Rose (the UML part of Rhapsody) working in a large team

Pros:

• Allows a standardised documentation method.
• Means that information should all be in one place.

Cons:

• Once it's part of a corporate environment, the methodology guys add a huge layer of complexity to the tool (which they don't have to use).  I'm very much of the opinion that diagrams are there to communicate processes, rather than having to be a stickler for methodology-based rules and complexity.
• Like every documenting system, it quickly drifts out of sync with the development and becomes useless.  In a perfect world, the logical models and use-cases should be kept updated, but no-one ever has the time or inclination to do this.

Like mouser says, they are overkill for a small team.  I don't think that you can beat scribbling random flow diagrams and bullet points on paper or a whiteboard and then archiving them with your mobile phone's camera.