Pretty much. One ideal might be for a flow chart to come alive and actually be the structure of your application itself, rather than just a reference or an aid.<p>I suppose that while visual programming excels at conveying topology and structure, it can be weak at a low level due to the tedium involved. Traditional code is arguably better suited for low-level grunt work, at least for most people.<p>A hybrid solution might be best. For example: a message travels from one high-level visual entity to another, and you&#x27;d easily be able to drill down into the code comprising those entities, locating the exact lines responsible for emission or receipt.