maths132-notes VS forth

I used to love programming in PostScript.

This post prompted me to put some of my old math notes up on GitHub [1]. The final chapter on coupled differential equations sends the DE's parameters to the PostScript printer, where my PS code would execute the different equations and draw the resulting phase portrait.

My PS code is in that repo's README. The final results are in the notes.pdf file [2]. The best examples are in the last few pages.

[1] https://github.com/stevesimmons/maths132-notes

[2] https://github.com/stevesimmons/maths132-notes/blob/main/not...

>You don't write README.md, ARCHITECTURE.md, JavaDocs, etc, at all?

Maybe? Not sure - haven't worked on enough big projects to declare answer

>A new developer is supposed to go through all the codebases and figure out for himself?

Yes to this bit - code should have very clear structure to it with appropriate comments attached, whether that's literate style as JonesForth<https://github.com/phf/forth/blob/master/x86/jonesforth.S> shows, small section header comment or whatever.

It should be very clear what section exploring does - tiny example but cat <http://9p.io/sources/plan9/sys/src/cmd/cat.c> from plan 9 very simple segmented code - deals with file opening in main loop and cat function just reads and prints text

JONESFORTH is good read if want source to explore

You're very welcome.

For later exploration, JonesForth <https://github.com/phf/forth/tree/master/x86> is excellent exploration of Forth's internals.