Diagrams can be great. but i feel like there are two completely separate ways of using them. The first is from the overly formal world of software engineering (

Diagrams can be great. but i feel like there are two completely separate ways of using them. The first is from the overly formal world of software engineering (e.g UML diagrams) where they were meant to act as a formal specification for others to follow. Luckily this practice is a lot less common. The second way is to use diagrams as a digital 'back-of-beer-coaster' tool to help you break down the big picture into smaller chunks. They also help you see at a glance areas that need more attention and also if more info from other people/systems is required. and generally, screw the logic. What's the data? and where does it go?