Ask HN: Do you still use UML?
UML can be a great communication tool in specific situations but when it becomes a religion your organization will suffer.  I'm older than most here, drank the cool-aid that predicted code generation and round tripping but spit it back up before the poison had a chance to set in.<p>A bonus comment for the youngin's ... When you hear that some new system will allow "the common man" to write his own software without developers, smile and agree with them because they'll come back when it doesn't go as planned and you can charge a higher rate for the resulting expedited project.<p>EDIT:<p>I should also admit that I liked (like?) the idea of writing code using diagrams.  In the '80s I wrote a program I called "Flo-Pro" in Turbo C that never quite became self-compiling.  It wasn't at all OOPsish or FP.  In the '90s I wrote several tools in Prograph [0] (now known as Marten) but was stymied by the fact that I was the only one in the company using the tool.  In the early aughts, I tried URL tools that promised to write my code from the diagrams - it worked for very simple code but I never saw round-tripping work.<p>I love drawings in general - my coworkers joke that it's not a meeting unless I have a dry-erase marker in my hand.  But those diagrams are invariably system-level, architectural drawings.  As others have noted, I also appreciate ERD as a way to visualize relationships in RDBMS.  So as much as I like the idea, development stays in the world of text - I'm not holding my breath for some magic bullet.<p>[0] <a href="http://www.andescotia.com/" rel="nofollow">http://www.andescotia.com/</a>