> My idea is a bit like literate programming, but instead of just writing a document that mixes code and text to describe the program as it is, you write a document that describes how it started, and how it evolved at each step… And at any point, you can extract the complete working system. I call that “narrative” programming, because it has that time component.
J seems to me like a strange fit for this. Why not prefer a language where the syntax, operators and idioms tend to leave you with already self-describing code? J is elegant enough, but I feel like I'd rather try this in a Scheme dialect or something.
Yeah, the same idea works for any language, and the software I wrote for it is language-neutral. I just happen to have a history of making J videos. (I haven't actually used the software in a video yet... I was just saying the videos tend to follow that similar narrative structure.)
2 comments
[ 0.15 ms ] story [ 9.2 ms ] threadJ seems to me like a strange fit for this. Why not prefer a language where the syntax, operators and idioms tend to leave you with already self-describing code? J is elegant enough, but I feel like I'd rather try this in a Scheme dialect or something.