Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

I usually prefer a Google Doc shared among the team to work on a given problem or feature instead of the so popular Miro. Diagrams are nice, yes, I agree, but they are not a substitute for actual text. Engineers think that because they draw boxes and lines and add little notes here and there the design is Done. Product managers usually like this approach too because “we don’t have time to read a whole page of text”. Drives me nuts.


You know what drives me nuts? People spending two pages on a convoluted description of what could have been a simple diagram. It goes both ways.


"A picture is worth a thousand words" or some such.

That said, I've certainly heard that different people prefer different ways of learning/consuming knowledge. I myself will choose video for some things, illustrations/graphs/images for other things, and text/tables for yet others. I do have a fondness for well done images, though.

Even the style of text can have an impact. Bullet points for providing instructions, instead of a long paragraph of sprawling text.

Another thing I picked up some 15 years ago is borrowed from newspapers: the concept of "above the fold"; get the main points out there near the top, and keep it concise.


A picture is worth a thousand words, but most instances of "a thousand words" cannot be expressed by a picture.


Pictures/visuals just communicate differently.

A well-done graph can communicate data and the desired message quickly. At the opposite end of the spectrum, we have poorly done or deceptive graphs.

An illustrated magazine will communicate a story differently, compared to a text-only novel. There's nuance to each approach that the other can't quite capture.

A photograph or painting can elicit a different level (breadth, depth) of mood/emotion that words might merely hint at.

Of course, what's useful in one context could be pointless in another. An introduction to photography would do well to include some illustrations, whereas a book on meditation could probably do fine with few, if any, images. Another example is Gray's Anatomy, which would probably be more challenging to consume if there were no illustrations.

Some subjects such as learning a martial art can be helped by using pictures/illustrations, but realistically when used as the only source of knowledge fall short of adequately communicating proficiency in said martial art, where only in-person instruction would really suffice.


Agree, most people cannot write concisely, sequence diagrams are generally a safer bet.


The diagram is a thinking tool, or a supplement to written text, but not the whole thing.


Text is for details, diagrams are to quickly communicate the whole idea in a single place. IMHO every complex-enough project needs both.


The import from URL feature on Google docs is perfect for importing mermaid.live diagrams to accompany the text. A mermaid.live URL contains the complete diagram state, which allows anyone to follow the original URL, make modifications and update the Google doc.


That's a hard sell for those who work in companies that prohibit dependencies on free 3rd-party web services to discuss business confidential ideas in an unsecure way.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: