Re:We need visual programming. No, not like that
by arethuza on Monday July 15, 2024 @05:46AM
(#40966448)
I can remember about 20 years ago a colleague getting quite frustrated that a bug he had been looking at for quite a long time came down to someone doing something bizarre in an overloaded assignment operator in C++.
[ Parent
| on HN ]
Re:We need visual programming. No, not like that
by guappa on Monday July 15, 2024 @06:44AM
(#40966678)
I've seen methods with names like "get_value()" have extensive side effects.
No type system can fix bad programming.
Re:We need visual programming. No, not like that
by arethuza on Monday July 15, 2024 @06:55AM
(#40966724)
Of course I think we have all seen horrors like that - what I remember was his completely exasperated response not the technical details of the bug.
Re:We need visual programming. No, not like that
by pastage on Monday July 15, 2024 @07:31AM
(#40966884)
Complexity is mostly exponentiellt worse in the unknowns and you can not graph what you already know.
The point in the article is that when we read code we need another visualization to change or mental model. I can scan code and find most bugs fast, but when you are stuck a complexity by row/column sure would be handy to find overloaded assignments.