Post by @dahukanna@mastodon.social

2026-07-27 07:54 UTC

1/2-“ @gvwilson@mastodon.social has often asked why we can't draw diagrams on top of code & I think this view of programming is one of the answers. We see code as a solution to a problem, not as a source of learning. We see documentation as unnecessary, because "talk is cheap, show me the code", but certain forms of knowledge can never be in the code. Knowledge like alternatives considered & rejected, paths explored & then backtracked, features that’d be hard to add or trivial & why.” https://www.felienne.nl/csoc-s01-e01/

Replies (1)

@stylus@social.afront.org 2026-07-27 12:09

@dahukanna@mastodon.social @ehmatthes@fosstodon.org @gvwilson@mastodon.social I have seen more than a few painstakingly created ASCII art diagrams in comments but they're a dying breed. I recognize it's hard to distinguish between preferences and rationalizations for the status quo but when I imagine having a diagram editor in my editor, and dismiss all worries about file format compatibility, I imagine I would not like the necessity of changing from a text centric view of my activity to a visual one, and that I would bristle at the need to become good at this form of representation in addition to all I do already. But there is at least some rationalization there, as I'll happily use a schematic capture program when designing circuits...

Open ##4995225