Visio Pride and its Zen

[Yacine]

Having lately been unfaithful to Visio and been playing around with Python I discovered a community so much proud of itself, that it built its own jokes and recognition signs.
Two I liked the most:
They have a name for their kinds: pythonista!
They have a credo of their own  - the Zen of Python (https://www.python.org/dev/peps/pep-0020/)

Code Select Expand

-Beautiful is better than ugly.
  -Explicit is better than implicit.
  -Simple is better than complex.
  -Complex is better than complicated.
  -Flat is better than nested.
  -Sparse is better than dense.
  -Readability counts.
  -Special cases aren't special enough to break the rules.
  -Although practicality beats purity.
  -Errors should never pass silently.
  -Unless explicitly silenced.
  -In the face of ambiguity, refuse the temptation to guess.
  -There should be one-- and preferably only one --obvious way to do it.
  -Although that way may not be obvious at first unless you're Dutch.
  -Now is better than never.
  -Although never is often better than *right* now.
  -If the implementation is hard to explain, it's a bad idea.
  -If the implementation is easy to explain, it may be a good idea.
  -Namespaces are one honking great idea -- let's do more of those!
I definitely envy them on these things.
Whilst Visio - being a proprietary system - will never belong to me as an open source "python" could, I still feel so much related to it as it is a very one kind of itself.
Therefore I plead for a similar pride as the pythonista have.From now on I am a Visioneer.

[Yacine]

If I were to just copy python's zen, I would probably start with:

Shapesheet formulas are better than macros.
Plugins are better than macros.
When it comes to open source, macros are better than plugins.

Locally referenced shapes are a bad idea.
Use document, page or search results to reference a shape.

Never ever build a system that relies on heavy manual maintenance.
Never store big amounts of data in masters, outsource them.

When ever possible think about maintainability and scalability.

[Paul Herber]

Is this language good at making triangles?
Pythonagoras.

[Yacine]

I'm not pleading for Python, but for Visio.

and yes, it (Python) does triangles very well.
Priangles, Tpiangles, Tryangles, red ones, but specially the blues ones.

And so does Visio.

I do relatively often interrogate the internet on alternatives to Visio. But regardless on how much I try, I cannot find anything that can:

- interactively draw
- and manage property dependencies

as Visio does. (I wish I had the capability to build an opensource version of Visio).