2 ms·
Good, structured verbal and written communication tends to be breadth-first, not depth-first. This doesn't come easy to a lot of people, especially programmers
by ryandrake 4y ago
Good, structured verbal and written communication tends to be breadth-first, not depth-first. This doesn't come easy to a lot of people, especially programmers where solving programming problems often times involves discovering (and addressing) a tree of sub-problems.
I look for this kind of structure when I interview people, and it's amazing how many go breadth-first with their answers, and it turns into a hard-to-follow stream-of-consciousness.
Me: "Please describe system X"
What I want to hear: "System X is composed of major subsystems A, B, and C. I'll talk about them in order. Subsystem A is composed of attributes 1, 2, and 3, which I can describe later if needed. Subsystem B is composed of 4, 5, 6..."
What I often get is: "System X first has subsystem A. Subsystem A has a lot of attributes, like attribute 1, which itself is composed of detail alpha, the research behind detail alpha is this: ... ..., ok, now back to attribute 1, there's also detail beta, which is really cool because ... ..." and we're out of time without even getting to any of the other attributes, or to subsystems B, subsystems C, or even mentioning any of their attributes.
It's easier to go from stream-of-consciousness to depth-first, but you lose your audience. Better to take the time to structure what you're going to say, and present it breadth-first, top-down.
EDIT: Somehow switched depth and breadth :)