[Oberon] a module a page (keeps the mind sane)?

[Frans-Pieter Vonck]

> Every time I search/read the book, it tends to become smaller;
I was trained to do my technical writing the Pyramid way.
https://medium.com/lessons-from-mckinsey/the-pyramid-principle-f0885dd3c5c7

And I just met a russian programmer who had learned the visual language 
Drakon.
Drakon is fun:
https://drakonhub.com/video-drakon-part-1

Programming in Modula (Oberon) one needs no flow charting, according to 
Niklaus.
However I feel comforable with drawing sketches with pencil and paper.

Greets,
Frans-Pieter


eas lab schreef op 2018-12-19 02:30:
> As always: better take a top-down-view.
> The screen/page contents is subservient to the Human Cognition.
> Eg. this current WebBased gmail is far inferior to our 90's 
> NativeOberon:
> - I can't see the email thread's Subject/Title. N.O. shows such vital
> info ALWAYS in the TopFrame.
> 
> - If you need to have simultaneous sight of multiple sections of a
> textFile, N.O. does it. Products of this F/B twitter age can't.
> 
> There's a problem of proliferation of fileNames and DirectoryTree
> structure, if every bit of info is to get its own file.
> 
> When re/searching a new topic: I create a single <BookFile> with the
> SectionTitles at the top. Which is another example of needing to view
> 2 sections of a file together:
>  see the top-ContentsDescription, while CopyPaste to autoSearch for
>  the required section.
> Every time I search/read the book, it tends to become smaller; by
> deletions of the terrible redundancy of web-publications.