#DoneDecidingWithDiamonds

Someone once told me how much they appreciate that I use the correct flow chart shapes.

Now, at the risk of disappointing them, I am deciding to break convention.

I appreciate the jarring disruption a diamond creates to highlight where a workflow may diverge, but I am done with the aesthetic tradeoffs.

  1. I don't want to make a larger diamond.
  2. I can't always shorten my text.
  3. Sometimes I need more than 3 divergent paths.

Enter the hexagon.

  1. Easily matches the dimensions of the other shapes.
  2. Provides more space for text.
  3. Supports 7 paths!

Sure - it may get trigger someone to question your knowledeg of conventions, as they spit out their coffee and arrogantly belittle you as they proclaim that hexagons are meant for initializations. That's why I'm sharing this post. It's time to build a movement. It's time to disrupt the status quo. If someone gives you any guff, you just point them here and let them know we're #DoneDecidingWithDiamonds.

If hexagons are good enough for the bees, then they're good enough for me. 

Popular

Work Experience vs Professional Experience

Let's Clear Up The Ambiguity!

FAQs for a Software Engineering Hiring Manager

7 Steps to Writing an Amazing Resume

7 Steps to Building your Portfolio MVP