If you were coding and realized a function you just wrote wasn't accounting for an edge case, you'd probably rewrite the relevant areas to account for it. Instead, if you had planned ahead, or taken the time to redraw, you could've maintained the low distance between nodes. That's when this property starts eroding away. and your next move is to draw that "engine" connects to more things. But what if your diagram currently looks like this. If you just have two nodes connected to each other, obviously you draw them close to each other. This is simple to get right for small diagrams, but much harder to do as they grow larger. I don't mean beautiful in the designer sense of drop shadows and rounded corners, but rather, functional beauty that maximizes its effectiveness to communicate ideas. Some of those have staying power that clarify and spark collaboration for the entirety of a project, while others don't live past the end of the afternoon meeting.īelow are some properties of beautiful diagrams. But there are many ways to draw the same dozen entities and relationships. What defines a diagram like that? The content, of course, has to be correct: things have to exist at the right abstraction levels, it's up-to-date, there's no ambiguity, etc. Periodically throughout the day, chairs swivel around to face this centerpiece, their occupants folding their hands behind their heads. Questions are answered by pointing at it. Over the next month, discussions gravitate around this diagram. Have you ever been in a meeting where a diagram is drawn, and when it ends, no one wants to erase the whiteboard? Instead, someone takes a picture of it on their phone, or they'll roll the whiteboard out to your team area and draw a big "DO NOT ERASE" sign.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |