3 ms·
I am hijacking this slightly to talk about something only partially related. I am very sleep deprived right now and probably won't do the idea justice, but it's
by zero_shift 2y ago
I am hijacking this slightly to talk about something only partially related. I am very sleep deprived right now and probably won't do the idea justice, but it's bounced around my head for a while now.
It's that I find programming a fundamentally visual medium, even as text. It's an urge whenever I write a function, not simply to be "neat" and visually consistent but for the program text to embody a rhythm that provides a subtext.
Functions with lots of short branches have a bubbly fine grained texture. I see them performing lots of detailed operations and I know it's IO bound code. It's one reason Golang programs feel good to me when applied to this domain.
I see rigidity aligned segments and I sense this is programming as configuration. I know I'm supposed to... elide over the operational details as a reader and it's maybe even functional. I like authoring those sorts of functions in Haskell, I can line up my let / wheres and case matches to visually communicate "I am doing rules based programming here".
I wonder if other programmers interact with programs visually. It's one reason I kind of... dislike other contributions to my programs because they don't usually follow my visual subtext. I tolerate it, obviously but it makes me wonder how much of code readability really is common sense and what aspects are highly unique
- rbanffy 2y agoThere is certainly an aspect of programming that's very "spatial", connected to the aesthetic perceptions of neatness and beauty. I like your metaphors, the "bubbly" texture (that'll impact things like branch prediction, or imply a heavy use of predicates in very parallel SIMD code, driving down efficient hardware usage)